@xyo-network/react-payload-details
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from individual (jonesmac) to org account (xyo) with 1109 approved packages; consistent with org-level CI migration. | ai | |
| phantom-deps | phantom-dep:@xylabs/sdk-js | AI (phantom-deps): @xylabs/sdk-js is a declared runtime dep used via config/re-exports in this monorepo package; stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): Large established XYO monorepo package; provenance absence is consistent across all versions. | ai | |
| dependencies | unvetted-dep:@xyo-network/react-schema | AI (dependencies): Same-org sibling dependency; stable pattern across XYO monorepo releases. | ai | |
| dependencies | unvetted-dep:@xyo-network/react-property | AI (dependencies): Same-org sibling dependency; stable pattern across XYO monorepo releases. | ai | |
| dependencies | unvetted-dep:@xyo-network/react-payload-raw-info | AI (dependencies): Same-org sibling dependency; stable pattern across XYO monorepo releases. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 8.0.1 | 4 / 87 | |
| 8.0.0 | 4 / 85 | |
| 7.5.12 | 4 / 84 | |
| 7.5.11 | 4 / 84 | |
| 7.5.8 | 12 / 23 | |
| 7.5.7 | 12 / 23 | |
| 7.5.6 | 12 / 18 | |
| 7.5.5 | 12 / 18 | |
| 7.5.4 | 12 / 18 | |
| 7.5.3 | 12 / 18 | |
| 7.5.2 | 12 / 18 | |
| 7.5.1 | 12 / 18 | |
| 7.5.0 | 12 / 17 | |
| 7.4.2 | 12 / 17 | |
| 7.4.1 | 12 / 17 | |
| 7.4.0 | 12 / 17 |
v8.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: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-16. This could indicate a legitimate maintainer transition or an account compromise.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.12
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.5.11
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: xyo.
This version was published by a different npm account than previous versions on 2026-04-23. 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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.4
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.5.3
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.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.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.5.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.
v7.4.2
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.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.