@xyo-network/schema-payload-plugin
2
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 | publisher-changed | AI (provenance): Publisher changed to org account 'xyo' with 872 approved packages; consistent with org-level account consolidation. | ai | |
| provenance | missing-githead | AI (provenance): Established XYO Network org with 530 approved packages; no material changes vs prior version; likely CI environment change rather than compromise. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by org account migration; xyo publisher has strong track record across 434 packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of large established XYO Network monorepo; sparse README is typical for internal plugin packages. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; provenance absence is consistent across all versions of this package family. | ai |
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.