@napi-rs/snappy-linux-arm-gnueabihf
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): napi-rs/snappy uses GitHub Actions CI/CD for automated publishing; transition from human account to GitHub Actions is the expected and documented release pattern for this ecosystem. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Platform-specific binary packages in the napi-rs ecosystem can have long gaps between releases; SLSA provenance attestation confirms legitimate CI/CD origin. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): This is a napi-rs platform-specific package; the .node binary is its sole purpose. SLSA provenance attestation confirms CI/CD build integrity. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific binary sub-packages in napi-rs ecosystem intentionally have no deps and minimal README — this is the standard pattern for all @napi-rs/* platform packages. | 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-arm-gnueabihf.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-arm-gnueabihf.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.