← Home

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

npm Repository Homepage
11
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

kev-oaikatg-oaixinlili-oaistatsigsdkaraf-oailoomb-oai

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Shift to GitHub Actions CI publisher is an improvement, not compromise indicator. ai
maintainer-change maintainer-added AI (maintainer-change): Org-consistent maintainer additions alongside CI-based publish. ai
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 11 of 11)

Version Deps Published
0.27.0 0 / 0
0.26.0 0 / 0
0.25.0 0 / 0
0.24.1 0 / 0
0.24.0 0 / 0
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.27.0

1 finding
LOW No provenance attestation provenance

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

v0.26.0

1 finding
LOW No provenance attestation provenance

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

v0.25.0

2 findings
HIGH Publisher changed: xinlili-oai → GitHub Actions (on 2026-07-06) provenance

This version was published by a different npm account than previous versions on 2026-07-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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