@simplewebauthn/browser
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Migrated to GitHub Actions CI/CD publishing with SLSA provenance; legitimate transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy ended with CI/CD-attested publish; consistent with maintainer resuming work. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 13.3.0 | 0 / 1 | |
| 13.2.2 | 0 / 1 | |
| 13.2.0 | 0 / 1 | |
| 13.1.2 | 0 / 1 |
v13.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.2.2
2 findingsThis version was published by a different npm account than previous versions on 2025-10-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.