Skip to content

docs: add private vulnerability reporting policy #258

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
byapparov merged 1 commit into from
Oct 21, 2026
Merged

docs: add private vulnerability reporting policy #258

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# Security policy

## Report a vulnerability

@aictrl-dev aictrl-dev Bot Oct 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚪ SECURITY.md lacks a supported-versions/scope section.

🤖 Fix with your agent 
Fix this code review finding (aictrl-dev/cli PR #258, SECURITY.md:3):

Problem: SECURITY.md lacks a supported-versions/scope section
Detail: The policy tells reporters what to include but not which CLI versions are currently supported, so reporters cannot tell whether an unsupported release is in scope. GitHub's standard SECURITY.md template pairs the reporting channel with a Supported Versions table. Everything security-relevant in the file (private-channel URL, org/repo links, sanitization guidance) is correct.
Suggested fix: Add a short "## Supported versions" section (e.g. a | Version | Supported | table listing the latest release as supported and older releases as best-effort, or the actual support window) so reporters know which versions are in scope.

Implement the fix on the PR head branch and add a regression test that fails before the fix and passes after.
Why this matters

The policy tells reporters what to include but not which CLI versions are currently supported, so reporters cannot tell whether an unsupported release is in scope. GitHub's standard SECURITY.md template pairs the reporting channel with a Supported Versions table. Everything security-relevant in the file (private-channel URL, org/repo links, sanitization guidance) is correct.

# Security policy

## Report a vulnerability

Report suspected vulnerabilities in aictrl CLI through [GitHub private vulnerability reporting](https://github.com/aictrl-dev/cli/security/advisories/new). You can also open this repository's Security and quality tab and choose **Report a vulnerability**.

Please include:


Report suspected vulnerabilities in aictrl CLI through [GitHub private vulnerability reporting](https://github.com/aictrl-dev/cli/security/advisories/new). You can also open this repository's Security and quality tab and choose **Report a vulnerability**.

Please include:

- The affected CLI version and relevant operating system or runtime details.
- A minimal reproduction and the observed behavior.
- The potential security impact.
- Sanitized logs or examples that help reproduce the problem.

Do not post exploit details, credentials, tokens, or private data in public issues. Remove secrets and personal data from any logs or examples you share.

For ordinary bugs without a suspected security impact, use the [public issue tracker](https://github.com/aictrl-dev/cli/issues).
Loading