← Home

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

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): Move to GitHub Actions CI publisher, not a manual account takeover pattern. ai
maintainer-change maintainer-added AI (maintainer-change): Org-internal maintainer additions (kev-oai, katg-oai) consistent with OpenAI statsig team. ai
npm-metadata no-description AI (npm-metadata): Auto-generated per-platform binary package; description omission is stable/expected. ai
npm-metadata bundled-binaries AI (npm-metadata): Platform-specific native binding package; the .node binary is the sole deliverable by design. ai
bogus-package bogus-package AI (bogus-package): Minimal metadata is expected for a platform-shard binary package with no deps or description needed. 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.