@xyo-network/diviner-abstract
3
Versions
—
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
atrouwjoelbcarterrphansen91jordantrouwjonesmac
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Likely a CI/CD environment change accompanying the publisher transition; no code changes detected. | ai | |
| provenance | publisher-changed | AI (provenance): jonesmac is an established publisher with 3701 approvals; consistent with org-level maintainer transition for xyo-network packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Large established XYO SDK monorepo package; sparse README/keywords is a consistent pattern across the org, not spam. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; provenance absence is consistent across all versions and not a security signal here. | ai |
v5.0.2
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.