abort-error
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Publisher achingbrain uses 0.0.0 as a starting version with semantic-release for versioning — a documented pattern in the IPFS ecosystem. Not indicative of malicious intent. | ai | |
| provenance | publisher-changed | AI (provenance): Package uses provenance:true and publishes via GitHub Actions CI/CD; publisher showing as 'GitHub Actions' instead of the human maintainer is the expected, documented behavior for this repo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Low-activity utility library; dormant periods followed by CI-triggered releases are normal for this package given its automated release setup. | ai |
v1.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-04-10. 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.
v1.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.