@nuggetslife/vc-darwin-arm64
This is the **aarch64-apple-darwin** binary for `@nuggetslife/vc`
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): Package is a prebuilt native Node.js addon; the .node file is the intended deliverable, not a backdoor. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific binary distribution packages routinely lack README, repo links, keywords, and deps — these signals are false positives for this package type. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.4.3 | 0 / 0 | |
| 0.4.2 | 0 / 0 | |
| 0.4.1 | 0 / 0 | |
| 0.4.0 | 0 / 0 | |
| 0.3.2 | 0 / 0 | |
| 0.3.1 | 0 / 0 | |
| 0.3.0 | 0 / 0 | |
| 0.2.0 | 0 / 0 | |
| 0.1.0 | 0 / 0 | |
| 0.0.30 | 0 / 0 | |
| 0.0.29 | 0 / 0 | |
| 0.0.28 | 0 / 0 | |
| 0.0.27 | 0 / 0 |
v0.4.3
2 findingsPackage contains compiled binaries that could be backdoors: • vc.darwin-arm64.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
2 findingsPackage contains compiled binaries that could be backdoors: • vc.darwin-arm64.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
2 findingsPackage contains compiled binaries that could be backdoors: • vc.darwin-arm64.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
2 findingsPackage contains compiled binaries that could be backdoors: • vc.darwin-arm64.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
2 findingsPackage contains compiled binaries that could be backdoors: • vc.darwin-arm64.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
2 findingsPackage contains compiled binaries that could be backdoors: • vc.darwin-arm64.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
2 findingsPackage contains compiled binaries that could be backdoors: • vc.darwin-arm64.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
2 findingsPackage contains compiled binaries that could be backdoors: • vc.darwin-arm64.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsPackage contains compiled binaries that could be backdoors: • vc.darwin-arm64.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
2 findingsPackage contains compiled binaries that could be backdoors: • vc.darwin-arm64.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
2 findingsPackage contains compiled binaries that could be backdoors: • vc.darwin-arm64.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
2 findingsPackage contains compiled binaries that could be backdoors: • vc.darwin-arm64.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.