@mearie/native-linux-arm64-gnu
Type-safe, zero-overhead GraphQL client
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is used for platform-specific native binding shims; stable pattern for this package family. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Platform-specific native binding package; .node binary is the intended artifact, published with SLSA provenance. | ai | |
| bogus-package | bogus-package | AI (bogus-package): No-dep, sparse README is expected for a platform-specific native binary sub-package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.4.1 | 0 / 0 | |
| 0.4.0 | 0 / 0 | |
| 0.3.0 | 0 / 0 | |
| 0.2.2 | 0 / 0 | |
| 0.2.1 | 0 / 0 | |
| 0.1.0 | 0 / 0 | |
| 0.0.0 | 0 / 0 |
v0.4.1
2 findingsPackage contains compiled binaries that could be backdoors: • mearie-native.linux-arm64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
2 findingsPackage contains compiled binaries that could be backdoors: • mearie-native.linux-arm64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
2 findingsPackage contains compiled binaries that could be backdoors: • mearie-native.linux-arm64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.2
2 findingsPackage contains compiled binaries that could be backdoors: • mearie-native.linux-arm64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.1
2 findingsPackage contains compiled binaries that could be backdoors: • mearie-native.linux-arm64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
2 findingsPackage contains compiled binaries that could be backdoors: • mearie-native.linux-arm64-gnu.node
Published 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.