@cc-kit/node-screenshots-win32-arm64-msvc
This is the **aarch64-pc-windows-msvc** binary for `cc-node-screenshots`
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Platform-specific binary shard packages legitimately lack README, keywords, repo URLs, and dependencies by design — they exist solely to ship a pre-compiled native addon for a specific OS/CPU target. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): The .node file is the expected deliverable for a platform-specific native addon package. No install scripts are present, reducing risk of malicious use. | ai |
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
2 findingsPackage contains compiled binaries that could be backdoors: • cc-node-screenshots.win32-arm64-msvc.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.