You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Before listing: a published CLI that can merge pull requests has no security reporting channel #396
This repository has no SECURITY.md, no issue templates, and private vulnerability reporting is
off — the repository's own security settings return no reporting configuration.
The package is published on npm and installs with one command. It is a CLI that opens pull
requests, watches CI and merges, and it ships a flag that merges a pull request past the
repository's own review requirement. A researcher who finds a problem in it has no documented
channel to report it in: the Security tab shows nothing, and the only escalation list in the
repository is an internal agent's, not a public one.
Acceptance criteria
SECURITY.md exists and gives an outside reporter a real channel, with what to include and
what response to expect.
Private vulnerability reporting is enabled on the repository, so the "report a vulnerability"
link works — the sibling router repository's does, and the check is one setting.
The channel is written for a stranger, not for the platform: no internal runbooks, no internal
escalation vocabulary.
Notes
The same repository's published README points at its own documentation; the sibling repositories in
this audit each have a working reporting channel, so this is an omission rather than a policy.
A package that can merge pull requests is worth a channel more than most.
changed the title [-]docs: the install documentation's four gaps[/-][+]Before listing: a published CLI that can merge pull requests has no security reporting channel[/+]on Nov 11, 2026
Private vulnerability reporting is still off: GET /repos/developerz-ai/ai-task-master/private-vulnerability-reporting returns {"enabled": false}, so the policy's "Report a vulnerability" link does not open yet. A repository admin needs to enable it under Settings → Code security → Private vulnerability reporting, or run gh api -X PUT repos/developerz-ai/ai-task-master/private-vulnerability-reporting.
The policy is written for a stranger: no internal runbooks or escalation vocabulary.
Reopened: the merge of #418 closed this by accident, because its description said "close this once the setting reads true" and GitHub reads that phrase as a closing keyword. Private vulnerability reporting is still off, so the second criterion is not met (see the status comment above).
The platform read this issue and is not planning work from it.
Triage judged that it does not ask for a change the platform can make: a tracking or discussion issue, for example. It stays open, and nothing here will be changed or closed by the platform.
A new issue asking for one concrete change is judged on its own.
Activity
[-]docs: the install documentation's four gaps[/-][+]Before listing: a published CLI that can merge pull requests has no security reporting channel[/+]developerz-ai commentedon Nov 14, 2026
🤖 developerz.ai, an automated agent, not a human — developerz-ai[bot]
Tracking pull request #418 for this issue.
dinndev2 commentedon Nov 14, 2026
Status:
SECURITY.mdexists and gives an outside reporter a private channel, what to include, response times and scope (docs(security): add a private reporting channel for outside reporters #418, merged).GET /repos/developerz-ai/ai-task-master/private-vulnerability-reportingreturns{"enabled": false}, so the policy's "Report a vulnerability" link does not open yet. A repository admin needs to enable it under Settings → Code security → Private vulnerability reporting, or rungh api -X PUT repos/developerz-ai/ai-task-master/private-vulnerability-reporting.Leaving this open until the setting reads
true.dinndev2 commentedon Nov 14, 2026
Reopened: the merge of #418 closed this by accident, because its description said "close this once the setting reads true" and GitHub reads that phrase as a closing keyword. Private vulnerability reporting is still off, so the second criterion is not met (see the status comment above).
developerz-ai commentedon Nov 15, 2026
Attempt 1 of 3 ended: the run finished with no change merged.
It has been filed again as attempt 2 of 3, carrying what the last one hit.
What stopped it:
run_timeout: The run hit a wall-clock, no-progress, or per-step deadline on the box and was aborted. The run timeline names which one.developerz-ai commentedon Nov 19, 2026
The platform read this issue and is not planning work from it.
Triage judged that it does not ask for a change the platform can make: a tracking or discussion issue, for example. It stays open, and nothing here will be changed or closed by the platform.
A new issue asking for one concrete change is judged on its own.