agent-passport-system

Every workflow declares explicit permissions scoped to its activity: read-only defaults, with elevated grants only where the job needs them (id-token:write for release provenance, issues:write for the PR commenter). The repository default token permission is read-only.

Dispatch inputs are consumed only as typed action parameters, never interpolated into shell steps; the one boolean-like input is a constrained choice compared for equality, and the username input flows to a JavaScript action as data.

package.json version is bumped for every release, and npm's registry rejects republishing an already-used version number, so every published version is guaranteed unique. [version_unique]

SECURITY.md's Secrets policy section defines storage, access, and rotation; the operating posture is zero long-lived secrets: OIDC publishing, ephemeral least-privilege CI tokens, push protection. https://github.com/aeoess/agent-passport-system/blob/main/SECURITY.md

Releases are published through npm Trusted Publishing (OIDC) with a SLSA build-provenance attestation signed via Sigstore; no long-lived signing key exists on any distribution site. SECURITY.md documents verification with npm audit signatures. https://www.npmjs.com/package/agent-passport-system [signed_releases]

Releases are published through npm Trusted Publishing (OIDC) with a SLSA build-provenance attestation signed via Sigstore; no long-lived signing key exists on any distribution site. SECURITY.md documents verification with npm audit signatures. https://www.npmjs.com/package/agent-passport-system [signed_releases]

SECURITY.md's Supported Versions section states the scope of support per release line: which package lines receive fixes and from which versions. https://github.com/aeoess/agent-passport-system/blob/main/SECURITY.md

The same Supported Versions table explicitly marks older versions as no longer receiving security updates. https://github.com/aeoess/agent-passport-system/blob/main/SECURITY.md

GOVERNANCE_SURFACES.md documents that held surfaces and escalated access require explicit founder approval, and the contribution ladder (Commons, Candidate, Core) is the review path before any elevated trust is granted. https://github.com/aeoess/agent-passport-system/blob/main/GOVERNANCE_SURFACES.md

The current release (v3.3.0) delivers an SPDX SBOM (sbom-v3.3.0.spdx.json), generated from the locked dependency graph, as a GitHub release asset alongside the provenance-attested npm tarball. https://github.com/aeoess/agent-passport-system/releases/tag/v3.3.0

All six codebases enforce a shared baseline (secret scanning, push protection, private vulnerability reporting), but the released-package siblings (Python SDK, MCP server) do not yet match the primary's full control set: no required status checks, CodeQL, or fuzzing there yet. Parity for the released siblings is tracked work.

npm test runs an extensive automated FLOSS test suite (tsx --test across hundreds of test files), documented in package.json and CONTRIBUTING.md.
https://github.com/aeoess/agent-passport-system/blob/main/CONTRIBUTING.md [test]

The written policy is in CONTRIBUTING.md: fixes require a failing test first, and new functionality requires tests before merge.
https://github.com/aeoess/agent-passport-system/blob/main/CONTRIBUTING.md [test_policy_mandated]

THREAT_MODEL.md carries the assurance case: the threat model (actors, assets, attacker capabilities), explicit numbered trust boundaries, what the system prevents and does not prevent, and an assurance argument mapping the design to secure-design principles and to countermeasures for common implementation weaknesses.
https://github.com/aeoess/agent-passport-system/blob/main/THREAT_MODEL.md [assurance_case]

There are no known vulnerabilities in the project's two runtime dependencies (npm audit gates every release), so no non-affecting findings exist to document in a VEX statement; if one arises, it will be recorded with non-exploitability detail.

Dependabot monitors the npm and GitHub Actions manifests (.github/dependabot.yml); OpenSSF Scorecard runs on schedule; the release gate runs npm audit before publish; cargo dependencies are pinned via the committed Cargo.lock. [dependency_monitoring]

Dependabot monitors the npm and GitHub Actions manifests (.github/dependabot.yml); OpenSSF Scorecard runs on schedule; the release gate runs npm audit before publish; cargo dependencies are pinned via the committed Cargo.lock. [dependency_monitoring]

Dependabot monitors the npm and GitHub Actions manifests (.github/dependabot.yml); OpenSSF Scorecard runs on schedule; the release gate runs npm audit before publish; cargo dependencies are pinned via the committed Cargo.lock. [dependency_monitoring]

All 14 open alerts resolved: 5 fixed with verified code changes (prototype pollution, command injection, SSRF, one test tightened), 9 dismissed as confirmed false positives, each with traced evidence. Combined with the 6 fixed and 4 dismissed earlier this session, 0 alerts remain open, confirmed by re-running the tool after every change.
https://github.com/aeoess/agent-passport-system/security/code-scanning [static_analysis_fixed]

CodeQL (security-extended) has been run against the codebase. https://github.com/aeoess/agent-passport-system/actions/runs/28966837754 [static_analysis]