@napi-rs/snappy-linux-arm64-musl
Fastest Snappy compression library in Node.js
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): Publisher changed to GitHub Actions with SLSA provenance attestation — this reflects legitimate CI/CD automation adoption by the known maintainer (broooooklyn/snappy). Stable for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by GitHub Actions publish with SLSA attestation indicates migration to automated publishing, not account takeover. SLSA provenance corroborates legitimate origin. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): This package's sole purpose is distributing the precompiled .node binary for Linux ARM64 musl. Bundled binary is expected and intentional for napi-rs platform packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific napi-rs binary sub-packages legitimately have no deps and minimal READMEs; these signals are structural false positives for this package type. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 7.3.3 | 0 / 0 | |
| 7.3.2 | 0 / 0 | |
| 7.3.1 | 0 / 0 | |
| 7.3.0 | 0 / 0 | |
| 7.2.2 | 0 / 0 | |
| 7.2.1 | 0 / 0 | |
| 7.2.0 | 0 / 0 | |
| 7.1.2 | 0 / 0 | |
| 7.1.1 | 0 / 0 | |
| 7.1.0 | 0 / 0 | |
| 7.0.5 | 0 / 0 | |
| 7.0.4 | 0 / 0 | |
| 7.0.3 | 0 / 0 | |
| 7.0.2 | 0 / 0 | |
| 7.0.1 | 0 / 0 | |
| 7.0.0 | 0 / 0 |
v7.3.3
2 findingsPackage contains compiled binaries that could be backdoors: • snappy.linux-arm64-musl.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.2
2 findingsThis version was published by a different npm account than previous versions on 2025-08-16. 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.3.1
2 findingsThis version was published by a different npm account than previous versions on 2025-08-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.
v7.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
2 findingsPackage contains compiled binaries that could be backdoors: • snappy.linux-arm64-musl.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.