socketcluster
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): This is a CLI scaffolding tool; child_process.spawn is expected for running npm/git commands during project creation. Stable false positive for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode in k8s.js is decoding Docker registry auth credentials (standard Docker config format). Legitimate Kubernetes tooling pattern, not obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 4595-day history and 424 versions; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 20.0.2 | 3 / 0 | |
| 20.0.1 | 3 / 0 | |
| 20.0.0 | 3 / 0 | |
| 19.2.0 | 3 / 0 | |
| 19.1.8 | 3 / 0 | |
| 19.1.7 | 3 / 0 | |
| 19.1.6 | 3 / 0 | |
| 19.1.5 | 3 / 0 | |
| 19.1.4 | 3 / 0 | |
| 19.1.3 | 3 / 0 | |
| 19.1.2 | 3 / 0 | |
| 19.1.1 | 3 / 0 | |
| 19.1.0 | 3 / 0 | |
| 19.0.2 | 3 / 0 | |
| 19.0.1 | 3 / 0 | |
| 19.0.0 | 3 / 0 |
v20.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.