bare-module-traverse
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Holepunch org migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI-published release with SLSA provenance; consistent with org-level tooling migration. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): kasperisager removal consistent with Holepunch org moving to automated CI publishing. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.1.2 | 3 / 6 | |
| 2.1.1 | 3 / 6 | |
| 2.1.0 | 3 / 6 | |
| 2.0.2 | 3 / 6 | |
| 2.0.1 | 3 / 5 | |
| 2.0.0 | 3 / 5 | |
| 1.8.3 | 3 / 5 | |
| 1.8.2 | 3 / 5 | |
| 1.8.1 | 3 / 5 | |
| 1.8.0 | 3 / 5 | |
| 1.7.4 | 3 / 5 | |
| 1.7.3 | 3 / 5 |
v2.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-07. 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.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.