@nx/key-linux-x64-musl
This package contains a native binary for @nx/key.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Platform-specific prebuilt .node binary is the sole purpose of this package; expected for @nx/key native binding. | ai | |
| bogus-package | bogus-package | AI (bogus-package): No-repo/no-deps/no-keywords are expected for a minimal platform-specific binary sub-package in the @nx/ ecosystem. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.0.6 | 0 / 0 | |
| 5.0.4 | 0 / 0 | |
| 5.0.3 | 0 / 0 | |
| 5.0.1 | 0 / 0 | |
| 5.0.0 | 0 / 0 |
v5.0.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
2 findingsPackage contains compiled binaries that could be backdoors: • nx_key.linux-x64-musl.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
2 findingsPackage contains compiled binaries that could be backdoors: • nx_key.linux-x64-musl.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.