22806bf364
Some checks failed
CodeFlash / Optimize new Python code (pull_request) Failing after 1s
E2E - Bubble Sort Benchmark / benchmark-bubble-sort-optimization (pull_request) Failing after 2s
E2E - Bubble Sort Pytest (No Git) / bubble-sort-optimization-pytest-no-git (pull_request) Failing after 2s
E2E - Bubble Sort Unittest / bubble-sort-optimization-unittest (pull_request) Failing after 1s
Coverage E2E / end-to-end-test-coverage (pull_request) Failing after 2s
E2E - Futurehouse Structure / futurehouse-structure (pull_request) Failing after 2s
E2E - Init Optimization / init-optimization (pull_request) Failing after 1s
E2E - Topological Sort / topological-sort-optimization (pull_request) Failing after 2s
E2E - Tracer Replay / tracer-replay (pull_request) Failing after 2s
PR Labeler / label-workflow-changes (pull_request) Failing after 1s
Mypy Type Checking for CLI / type-check-cli (pull_request) Failing after 1s
/ Run pr agent on every pull request, respond to user comments (pull_request) Failing after 1s
Lint / Run pre-commit hooks (pull_request) Failing after 6s
unit-tests / unit-tests (3.10) (pull_request) Failing after 2s
unit-tests / unit-tests (3.11) (pull_request) Failing after 1s
unit-tests / unit-tests (3.12) (pull_request) Failing after 2s
unit-tests / unit-tests (3.13) (pull_request) Failing after 2s
unit-tests / unit-tests (3.9) (pull_request) Failing after 2s
19 lines
1.2 KiB
Markdown
19 lines
1.2 KiB
Markdown
# Security Policy
|
|
|
|
This document outlines Codeflash's vulnerability disclosure policy. For more information about Codeflash's approach to security, please visit [codeflash.ai/security](https://www.codeflash.ai/security).
|
|
|
|
## Supported Versions
|
|
|
|
Since Codeflash is moving quickly, we can only commit to fixing security issues for the latest version of codeflash client.
|
|
If a vulnerability is discovered in our backend, we will release the fix for all the users.
|
|
|
|
## Reporting a Vulnerability
|
|
|
|
|
|
Please do not report security vulnerabilities through public GitHub issues.
|
|
|
|
Instead, please report them to our [GitHub Security page](https://github.com/codeflash-ai/codeflash/security). If you prefer to submit one without using GitHub, you can also email us at security@codeflash.ai.
|
|
|
|
We commit to acknowledging vulnerability reports immediately, and will work to fix active vulnerabilities as soon as we can. We will publish resolved vulnerabilities in the form of security advisories on our GitHub security page. Critical incidents will be communicated both on the GitHub security page and via email to all affected users.
|
|
|
|
We appreciate your help in making Codeflash more secure for everyone. Thank you for your support and responsible disclosure.
|