Skip to content

docs(security): add a private reporting channel for outside reporters - #418

Merged
dinndev2 merged 1 commit into
mainfrom
docs/security-policy
Nov 14, 2026
Merged

dinndev2 merged 1 commit into
mainfrom
docs/security-policy

Conversation

@dinndev2

Copy link
Copy Markdown
Contributor

What

Adds SECURITY.md: a private reporting channel written for an outside reporter. It covers supported versions (the latest published version only), how to report and what to include, response times, and scope. The scope says what aitm actually is: a CLI that runs a model's tool calls in a worktree with your credentials and can merge pull requests.

  • In scope: credentials reaching anything aitm publishes; a file tool escaping its worktree; outside content making aitm itself merge or push; --admin doing more than documented; the same classes in ai-claude-compat.
  • Out of scope: what --admin is documented to do; prompt injection that stays inside the boundaries aitm enforces; a model writing bad code; upstream providers and tools.

There are no internal runbooks and no internal escalation vocabulary. The response times match the sibling router repository's policy.

The other half of #396 needs a repository admin

The policy's "Report a vulnerability" link works only once private vulnerability reporting is enabled, and it is off. GET /repos/developerz-ai/ai-task-master/private-vulnerability-reporting returns {"enabled": false}. An admin can turn it on in Settings → Code security → Private vulnerability reporting → Enable, or with:

gh api -X PUT repos/developerz-ai/ai-task-master/private-vulnerability-reporting

Until then, merging this publishes a channel that does not open. So this PR refers to #396 rather than closing it. Close #396 once the setting reads true.

Refs #396

🤖 Generated with Claude Code

SECURITY.md names the supported version, how to report privately through a
GitHub security advisory and what to include, the response times, and what
is and is not in scope for a CLI that runs tool calls with the user's
credentials and can merge pull requests.

Refs #396

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@developerz-ai

developerz-ai Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

✅ Reviewed — nothing survived verification

0 actionable comment(s) · 1 refuted by verification · grounded on your code

⚠️ 1 config note(s): test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against

🤖 developerz.ai — automated review, running on your model and your box.

@developerz-ai developerz-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Review summary — 1 file(s), 0 finding(s).

  • test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against

🤖 developerz.ai review — automated, running on your model and your box. What is this?

@dinndev2
dinndev2 merged commit 355a423 into main Nov 14, 2026
5 checks passed
@dinndev2
dinndev2 deleted the docs/security-policy branch November 14, 2026 04:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Before listing: a published CLI that can merge pull requests has no security reporting channel

1 participant