Repository navigation
docs: add a security policy - #590
Conversation
The issue template already routes security reports to security/advisories/new, but there is no SECURITY.md, so GitHub shows the repo as having no policy and the reporting route is undocumented everywhere else. Covers where to report, what to include, response and disclosure timelines, and what is in and out of scope. Adds two notes for self-hosters: a workspace token is one shared credential with no per-agent identity, and the identity provider settings decide which tenant a deployment trusts. Note the private reporting form linked from the issue template is currently disabled, so external reports get HTTP 403 'Repository does not have private vulnerability reporting enabled'. Enabling it in Settings > Code security would make that route work; the policy lists email as a fallback in the meantime.
|
@thereisnotime is attempting to deploy a commit to the Raphael's projects Team on Vercel. A member of the Team first needs to authorize it. |
Name no third-party products: the out-of-scope agent runtimes and the transport protocols are described generically, and the identity-provider note no longer lists specific vendor variables. Drop the container image from scope (it and its publish workflow were removed this month) and the self-declared agent_name detail, which is an implementation note rather than policy.
zomux
left a comment
zomux
left a comment
There was a problem hiding this comment.
Approve, thanks for writing this down and for spotting that private vulnerability reporting was off — it is now enabled on the repo, so the linked form works for outside reporters. I pushed one commit on top to keep the policy to this project: the out-of-scope agent runtimes and the transports are described generically rather than by product name, the identity-provider note no longer lists vendor-specific variables, the container image is out of scope (it and its publish workflow were removed this month), and the self-declared agent_name detail is dropped as an implementation note rather than policy.
3 participants
GitHub reports this project has no
SECURITY.md, so the repo shows no policy and the reporting route is undocumented outside the issue template..github/ISSUE_TEMPLATE/config.ymlalready says:This writes that down properly and fills in the parts the template cannot: what to include, response and disclosure timelines, and scope.
One thing worth checking
The private reporting form linked from that template is currently disabled. An external report returns:
So the policy asks people to report privately through a door that is not open, and the only remaining routes are public. Enabling it under Settings > Code security would fix that. Until then the policy lists
team@openagents.org(frompackages/launcher/package.json) as a fallback. Happy to swap that for a different address.Contents
FIREBASE_PROJECT_ID/APPLE_CLIENT_IDSdecide which identity tenant a deployment trustsAll of it is a description of current behaviour. Adjust the timelines and the contact address to whatever you actually want to commit to.