← Home

@oai-statsig/statsig-node-core-linux-arm64-musl

npm Repository Homepage
6
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

xinlili-oaistatsigsdkaraf-oailoomb-oai

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): Platform-specific native Node.js binding; bundled .node binary is the sole purpose of this package. ai
bogus-package bogus-package AI (bogus-package): No-dep, no-keyword pattern is expected for a platform-specific binary distribution 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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.23.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.22.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: statsigsdk → xinlili-oai (on 2026-06-01, known maintainer) provenance

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 findings
HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • statsig-node-core.linux-arm64-musl.node

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.

v0.19.5

2 findings
HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • statsig-node-core.linux-arm64-musl.node

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.

v0.19.4

2 findings
HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • statsig-node-core.linux-arm64-musl.node

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.