Thank you for helping keep the Agent Volumes project and its community safe. As an independent non-profit organization focused on open specifications and documentation, we take security seriously and follow a coordinated disclosure process.

This policy applies to all public repositories under the Agent Volumes organization, including:

• Specification documents
• Documentation assets
• Conformance and validation assets

We do not maintain private repositories, backend code, or internal infrastructure.

The following are out of scope for this policy:

• Cosmetic or content issues without security impact
• Vulnerabilities in upstream projects or tools that we use but do not maintain
• Denial of Service (DoS) testing against organization assets
• Reports based only on missing best-practice headers without a demonstrable exploit

Please report vulnerabilities privately:

• Preferred: GitHub Security Advisories — Use the Security > Advisories tab in the relevant repository to submit a private report.
• Alternate: Send a report to security@agentvolumes.org.

1. The affected repository and specific version or commit
2. A description of the vulnerability and its potential impact
3. Detailed reproduction steps or a proof of concept
4. Suggested mitigation or fix (if available)

These timelines are best-effort commitments. We will keep you informed of progress at least every 7 business days until the issue is closed.

We follow coordinated disclosure:

1. The reporter submits a private vulnerability report.
2. We acknowledge, triage, and work on a fix privately.
3. Once a fix is applied, we publish a GitHub Security Advisory with full details.
4. The reporter is credited in the advisory unless they request anonymity.
5. If no fix is released within 90 days, the reporter may disclose publicly.

We will not take legal action against researchers who report vulnerabilities in good faith and follow this policy.

We support good-faith security research. We ask that you:

• Access data only to the extent required to prove impact
• Avoid degrading service availability for others
• Refrain from social engineering or destructive testing

Agent Volumes follows the SLSA (Supply-chain Levels for Software Artifacts) framework as aspirational guidance to ensure the integrity of our specifications and documentation.

• Build L1/L2 required; Build L3 target
• Source L1/L2 required; Source L3 target
• Source L4 not achievable in a 1-person organization
• SHA-pinned workflows, hardened runners, least-privilege permissions
• Lockfiles committed, dependency review, OSV scanning
• Signed commits & protected branches required

All commits to protected branches must be cryptographically signed. We support:

• GPG signing
• SSH signing
• Sigstore gitsign

All repositories must enforce:

• Require signed commits
• Require pull request reviews (minimum 1 reviewer)
• Require status checks to pass before merging
• Require linear history (no merge commits)
• Restrict force pushes

While we currently focus on documentation and specifications, we aim to provide signed attestations and SLSA provenance for any future software artifacts or conformance tools released by the organization.

• All workflow runs are logged via GitHub's audit log
• Access to secrets is logged
• Deployment activity is tracked

• Dependabot alerts are enabled on all repositories
• Code scanning with CodeQL and/or Semgrep runs on all PRs
• OSV Scanner runs on PRs and scheduled full scans
• Secret scanning prevents credential leakage

This organization uses OpenSSF Scorecard to continuously monitor security posture:

• Binary artifacts
• Branch protection
• Code review
• Dependency update tool
• Fuzzing
• License
• Maintained
• Pinned dependencies
• SAST
• Security policy
• Signed releases
• Token permissions
• Vulnerabilities

Detailed reference lists for each topic are available in the companion documents:

• SLSA Framework references
• GitHub Security and Step Security references
• OSV Scanner and Additional Resources