@balena/node-crc-utils
2
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
balena.iopage
Keywords
crc32crc32_combinecrcgzip
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Balena migrated publishing to GitHub Actions CI/CD with SLSA attestation; this is the expected new publisher for this org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal consistent with org-level CI/CD takeover of publishing; no malicious indicators. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Automated CI/CD pipelines routinely publish successive versions rapidly; no malicious content found. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Fires on Emscripten-compiled crc32.js WASM output; stable false positive for this package. | ai |
v3.1.0
2 findings
HIGH
Publisher changed: balena.io → GitHub Actions (on 2026-06-03)
provenance
This version was published by a different npm account than previous versions on 2026-06-03. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.