@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is an in-house sibling package, part of monorepo restructure into a shim. | ai | |
| provenance | missing-githead | AI (provenance): Known maintainer manual publish pattern for this org; not a tampering signal. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Org-level maintainer rotation in a large, established XYO Network package; not indicative of takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org-level rotation; xyo account replaced by atrouw within the same organization. | 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 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 10.0.6 | 1 / 61 | |
| 10.0.5 | 2 / 50 | |
| 10.0.4 | 2 / 48 | |
| 10.0.3 | 2 / 59 | |
| 10.0.2 | 2 / 61 | |
| 10.0.0 | 2 / 61 | |
| 9.1.1 | 2 / 61 | |
| 9.1.0 | 2 / 61 | |
| 9.0.6 | 2 / 67 | |
| 9.0.5 | 2 / 67 | |
| 9.0.4 | 2 / 66 | |
| 9.0.2 | 2 / 76 | |
| 9.0.1 | 2 / 79 | |
| 9.0.0 | 2 / 83 | |
| 8.0.1 | 2 / 83 | |
| 8.0.0 | 2 / 81 | |
| 7.6.3 | 2 / 81 | |
| 7.6.2 | 2 / 82 | |
| 7.6.1 | 2 / 82 | |
| 7.5.12 | 2 / 80 | |
| 7.5.11 | 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 |
v10.0.6
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: atrouw.
[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 (atrouw) than the most recent previously approved version (jonesmac) on 2026-07-07, but atrouw 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.
v10.0.5
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: atrouw.
[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 (atrouw) than the most recent previously approved version (jonesmac) on 2026-07-07, but atrouw 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.
v10.0.4
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: atrouw.
[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 (atrouw) than the most recent previously approved version (jonesmac) on 2026-07-04, but atrouw 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.
v10.0.3
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: atrouw.
[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 (atrouw) than the most recent previously approved version (jonesmac) on 2026-06-30, but atrouw 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.
v8.0.0
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jonesmac.
This version was published by a different npm account (jonesmac) than the most recent previously approved version (atrouw) on 2026-05-08, 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.6.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
v7.6.2
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
This version was published by a different npm account (atrouw) than the most recent previously approved version (xyo) on 2026-05-06, but atrouw is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.6.1
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
This version was published by a different npm account (atrouw) than the most recent previously approved version (xyo) on 2026-05-05, but atrouw is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.5.11
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
This version was published by a different npm account (xyo) than the most recent previously approved version (jonesmac) on 2026-04-23, but xyo 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.