Skip to content

docs: add a security policy - #590

Open
thereisnotime wants to merge 1 commit into
openagents-org:developfrom
thereisnotime:docs/security-policy
Open

docs: add a security policy#590
thereisnotime wants to merge 1 commit into
openagents-org:developfrom
thereisnotime:docs/security-policy

Conversation

@thereisnotime

Copy link
Copy Markdown

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.yml already says:

🔒 Report a Security Vulnerability, security/advisories/new. Please report security issues privately, NOT in public issues.

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:

POST /repos/openagents-org/openagents/security-advisories/reports
403: Repository does not have private vulnerability reporting enabled

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 (from packages/launcher/package.json) as a fallback. Happy to swap that for a different address.

Contents

  • where to report and what to include
  • acknowledgement within 5 working days, 90 day disclosure window
  • scope, including that vulnerabilities in agent runtimes the launcher shells out to belong to their own maintainers, and that holding a workspace token you were given is not a finding
  • two notes for self-hosters: a workspace token is a single shared credential with no per-agent identity, and FIREBASE_PROJECT_ID / APPLE_CLIENT_IDS decide which identity tenant a deployment trusts

All of it is a description of current behaviour. Adjust the timelines and the contact address to whatever you actually want to commit to.

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.
@vercel

vercel Bot commented Aug 3, 2026

Copy link
Copy Markdown

@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.

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.

1 participant