snyk
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/cli/320.index.js | AI (source-diff): Snyk CLI bundles brotli-compressed webpack assets; this pattern is stable and expected across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Established Snyk package; lack of Sigstore provenance is low risk given publisher track record. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Env spreading is intentional to pass environment to child CLI process; stable pattern for this package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Snyk's documented bootstrap pattern; runs platform binary setup on install across all versions. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used to exec the Snyk CLI binary; core to the wrapper's documented functionality. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads platform binary deployment config; expected pattern for cross-platform CLI bootstrap. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Snyk bundles platform-specific .node binaries as part of its CLI distribution; stable pattern across versions. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.1304.3 | 2 / 4 | |
| 1.1304.2 | 2 / 4 | |
| 1.1304.1 | 2 / 4 | |
| 1.1304.0 | 2 / 4 |
v1.1304.3
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1304.2
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1304.1
5 findingsScript: node wrapper_dist/bootstrap.js exec
Package contains compiled binaries that could be backdoors: • dist/cli/436e8fd533bf10006b55a55732649189.node • dist/cli/8e59fcb098dc20398bb2cf58a44b048e.node
Spreading entire process.env into an object — may capture all secrets 188 | shell: false, 189 | stdio: 'inherit', > 190 | env: { 191 | ...process.env, 192 | SNYK_INTEGRATION_NAME: integrationName,
Spreading entire process.env into an object — may capture all secrets 149 | shell: false, 150 | stdio: 'inherit', > 151 | env: { 152 | ...process.env, 153 | SNYK_INTEGRATION_NAME: exports.integrationName,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1304.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.