← Home

@xyo-network/react-payload-details

33
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

atrouwjoelbcarterrphansen91jordantrouwjonesmac

Keywords

xyoutilitytypescriptreact

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Manual publish by known maintainer explains missing gitHead; no behavior change. ai
maintainer-change maintainer-removed AI (maintainer-change): Org account rotation within same known team, corroborated by provenance INFO finding. ai
maintainer-change maintainer-added AI (maintainer-change): atrouw matched as known maintainer by email; manual publish, not compromise. ai
source-diff source-size-dropped AI (source-diff): Package became a deprecated shim re-exporting react-sdk; shrink is expected. ai
publish-pattern new-deps-added AI (publish-pattern): Added dep is the first-party sibling package it now shims to. ai
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
dependencies unvetted-dep:@xyo-network/react-payload-raw-info 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-schema AI (dependencies): Same-org sibling dependency; stable pattern across XYO monorepo releases. ai
provenance no-provenance AI (provenance): Large established XYO monorepo package; provenance absence is consistent across all versions. ai

Versions (showing 33 of 33)

Version Deps Published
10.0.6 1 / 61
10.0.5 4 / 54
10.0.4 4 / 52
10.0.3 4 / 63
10.0.2 4 / 65
10.0.0 4 / 65
9.1.1 4 / 65
9.1.0 4 / 65
9.0.6 4 / 71
9.0.5 4 / 71
9.0.4 4 / 70
9.0.2 4 / 80
9.0.1 4 / 83
9.0.0 4 / 87
8.0.1 4 / 87
8.0.0 4 / 85
7.6.3 4 / 85
7.6.2 4 / 86
7.6.1 4 / 86
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

v10.0.6

2 findings
HIGH Missing gitHead — previous versions had it provenance

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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.5

2 findings
HIGH Missing gitHead — previous versions had it provenance

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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.4

2 findings
HIGH Missing gitHead — previous versions had it provenance

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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.3

2 findings
HIGH Missing gitHead — previous versions had it provenance

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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.6.3

3 findings
HIGH Missing gitHead — previous versions had it provenance

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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: xyo → atrouw (on 2026-05-07, known maintainer) provenance

This version was published by a different npm account (atrouw) than the most recent previously approved version (xyo) on 2026-05-07, 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.2

3 findings
HIGH Missing gitHead — previous versions had it provenance

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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: xyo → atrouw (on 2026-05-06, known maintainer) provenance

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
HIGH Missing gitHead — previous versions had it provenance

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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: xyo → atrouw (on 2026-05-05, known maintainer) provenance

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.