@xyo-network/react-payload-plugin
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org-level rotation; xyo account replaced by atrouw within the same organization. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Org-level maintainer rotation in a large, established XYO Network package; not indicative of takeover. | ai | |
| license | weak-copyleft-license:LGPL-3.0-only | AI (license): Standard weak copyleft license; stable across versions of this package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to org account 'xyo' with 1105 approved packages; consistent with org-level publisher consolidation. | ai | |
| dependencies | unvetted-dep:@xylabs/react-identicon | AI (dependencies): Internal xylabs ecosystem dependency; consistent pattern across XYO Network packages. | ai | |
| dependencies | unvetted-dep:@xyo-network/react-payload-details | AI (dependencies): Same-org dependency from XYO Network monorepo; stable pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): XYO Network monorepo; consistent pattern across all their packages, not a risk indicator. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 9.0.1 | 2 / 79 | |
| 7.5.12 | 2 / 80 | |
| 7.5.8 | 5 / 11 | |
| 7.5.7 | 5 / 11 | |
| 7.5.6 | 5 / 10 | |
| 7.5.5 | 5 / 10 | |
| 7.5.4 | 5 / 10 | |
| 7.5.3 | 5 / 10 | |
| 7.5.2 | 5 / 10 | |
| 7.5.1 | 5 / 10 | |
| 7.5.0 | 5 / 9 | |
| 7.4.2 | 5 / 9 | |
| 7.4.1 | 5 / 9 | |
| 7.4.0 | 5 / 9 |
v9.0.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jonesmac.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jonesmac) than the most recent previously approved version (xyo) on 2026-06-01, but jonesmac 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.
v7.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.