docs: add SECURITY.md vulnerability reporting policy#565
Conversation
Deletes deprecated tooling artifacts: .airlock, .bazelignore, .bazelrc, .codex skills, .devcontainer, .editorconfig, .env.example, .github templates and scripts, .gitignore, .golangci.yml, and CI workflow files. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
CodeAnt AI is reviewing your PR. Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is ON, but it could not run because on-demand usage is turned off. To enable Bugbot Autofix, turn on on-demand usage and set a spend limit in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 7b514b9. Configure here.
|
|
||
| ## Reporting a Vulnerability | ||
|
|
||
| If you discover a security vulnerability, please report it by [opening an issue](https://github.com/KooshaPari/helios-cli/issues/new?labels=security). |
There was a problem hiding this comment.
Security policy directs vulnerability reports to public issues
High Severity
The new .github/SECURITY.md instructs users to report security vulnerabilities by opening a public GitHub issue. This directly contradicts the existing root-level SECURITY.md, which explicitly states "Do NOT open public GitHub issue security vulnerabilities" and directs reporters to use email or GitHub Security Advisories instead. Public disclosure of vulnerabilities before a fix is available exposes the project and its users to exploitation.
Reviewed by Cursor Bugbot for commit 7b514b9. Configure here.
| * @KooshaPari | ||
|
|
||
| # Infrastructure as code | ||
| /iac/ @KooshaPari |
There was a problem hiding this comment.
Docs-only PR deletes critical CI and infrastructure files
High Severity
This PR is described as "docs: add SECURITY.md vulnerability reporting policy" but it also deletes dozens of critical files — CI workflows (CodeQL, cargo-audit, cargo-deny, codespell, CLA), code signing actions, build scripts, .bazelrc, .editorconfig, .codespellrc, issue templates, devcontainer configs, pre-commit hooks, dependabot configs, and more. These deletions are far outside the stated scope and appear to be accidentally included. The repository is left without CI, linting, security scanning, or automated dependency management after this change.
Reviewed by Cursor Bugbot for commit 7b514b9. Configure here.
Code Review SummaryStatus: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Other Observations (not in diff)Issues found in unchanged code that cannot receive inline comments:
Files Reviewed (2 files)
Reviewed by nemotron-3-super-120b-a12b-20230311:free · 444,116 tokens |


Summary
Test plan
🤖 Generated with Claude Code
Note
High Risk
High risk because it deletes a large amount of CI/workflow, Bazel, signing, and automation/config files, which can silently remove build/test/security gates and release tooling.
Overview
This PR performs a major repository cleanup by removing a large set of upstream automation and tooling configs (Airlock workflow, Bazel configuration, devcontainer setup, pre-commit hooks/scripts, custom GitHub Actions for code signing/policy gates, and many GitHub workflows).
It also simplifies
.github/CODEOWNERSand adds a new.github/SECURITY.mdsecurity policy document (in addition to the existing rootSECURITY.md).Reviewed by Cursor Bugbot for commit 7b514b9. Bugbot is set up for automated code reviews on this repo. Configure here.