bare-pack
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): Transition to GitHub Actions CI publisher with SLSA attestation is the expected holepunchto org automation pattern. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): kasperisager removed as direct publisher; replaced by GitHub Actions CI — consistent with org-level automation adoption. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI-automated publish with SLSA provenance; no malicious indicators in diff. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): CLI loads user-supplied builtins file via --builtins flag; intentional and documented pattern for this tool. | ai | |
| phantom-deps | phantom-dep:bare-fs | AI (phantom-deps): bare-fs is used via package.json imports map conditional ('bare' condition), not a direct import statement. | ai | |
| phantom-deps | phantom-dep:bare-path | AI (phantom-deps): bare-path is used via package.json imports map conditional ('bare' condition), not a direct import statement. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.1.2 | 7 / 4 | |
| 2.1.1 | 7 / 4 | |
| 2.1.0 | 7 / 4 | |
| 2.0.2 | 7 / 4 | |
| 2.0.1 | 8 / 4 | |
| 2.0.0 | 8 / 4 | |
| 1.5.1 | 8 / 4 | |
| 1.5.0 | 8 / 4 | |
| 1.4.10 | 8 / 4 | |
| 1.4.9 | 8 / 4 |
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-06-05. 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.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.