corestore
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:bare-events | AI (phantom-deps): bare-events is used via package.json imports map conditional, not a direct import; stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Holepunch org uses GitHub Actions for publishing with SLSA attestation; CI publisher is expected going forward. | ai | |
| dependencies | unvetted-dep:b4a | AI (dependencies): b4a is a standard Holepunch buffer utility used across the ecosystem; stable false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 7.10.1 | 10 / 5 | |
| 7.10.0 | 10 / 5 | |
| 7.9.2 | 8 / 6 | |
| 7.9.1 | 8 / 6 | |
| 7.9.0 | 8 / 6 | |
| 7.8.0 | 8 / 6 | |
| 7.7.0 | 8 / 5 | |
| 7.6.1 | 8 / 5 | |
| 7.6.0 | 8 / 5 | |
| 7.5.0 | 8 / 5 | |
| 7.4.8 | 8 / 4 | |
| 7.4.7 | 8 / 4 | |
| 7.4.6 | 8 / 4 | |
| 7.4.5 | 8 / 4 | |
| 7.4.4 | 8 / 4 | |
| 7.4.3 | 8 / 4 | |
| 7.4.2 | 7 / 4 |
v7.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.10.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-27. 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.
v7.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.