@oai-statsig/statsig-node-core-linux-x64-musl
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): Prebuilt native .node binary is the sole purpose of this platform-specific shard package; expected pattern for statsig-node-core. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Platform-specific binary shard packages routinely omit descriptions; stable pattern for this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): No-dep, no-keyword, no-description signals are all expected for a minimal native binary shard package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.23.1 | 0 / 0 | |
| 0.23.0 | 0 / 0 | |
| 0.22.0 | 0 / 0 | |
| 0.20.0 | 0 / 0 | |
| 0.19.5 | 0 / 0 | |
| 0.19.4 | 0 / 0 |
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (xinlili-oai) than the most recent previously approved version (statsigsdk) on 2026-06-01, but xinlili-oai is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.20.0
2 findingsPackage contains compiled binaries that could be backdoors: • statsig-node-core.linux-x64-musl.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.5
2 findingsPackage contains compiled binaries that could be backdoors: • statsig-node-core.linux-x64-musl.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.4
2 findingsPackage contains compiled binaries that could be backdoors: • statsig-node-core.linux-x64-musl.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.