@xyo-network/react-chain-transfer-plugin
XYO Layer One API
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@xyo-network/xl1-sdk | AI (phantom-deps): Same-org scope, re-exported by shim. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Package intentionally became a deprecated compat shim per package.json. | ai | |
| dependencies | unvetted-dep:@xyo-network/react-chain | AI (dependencies): Same-org XYO package, the shim's replacement target. | ai | |
| provenance | missing-githead | AI (provenance): High-volume monorepo publisher; missing gitHead is a CI environment change, not a supply-chain indicator for this package. | ai | |
| dependencies | unvetted-dep:@xyo-network/react-event | AI (dependencies): Same xyo-network publisher with strong approval track record; stable sibling dep pattern. | ai | |
| dependencies | unvetted-dep:@xyo-network/react-payload-plugin | AI (dependencies): Same xyo-network publisher with strong approval track record; stable sibling dep pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): XYO monorepo packages consistently have link-heavy READMEs and no keywords; not a spam indicator for this org. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is an in-ecosystem sibling package at matching version; low risk for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Consistent with all other xyo-network packages in this ecosystem; no provenance is org-wide norm. | ai |
Versions (showing 100 of 158)
| Version | Deps | Published |
|---|---|---|
| 4.0.5 | 2 / 70 | |
| 4.0.4 | 1 / 65 | |
| 4.0.3 | 1 / 65 | |
| 4.0.2 | 1 / 76 | |
| 4.0.1 | 1 / 76 | |
| 4.0.0 | 1 / 75 | |
| 3.0.2 | 1 / 76 | |
| 3.0.1 | 1 / 76 | |
| 3.0.0 | 1 / 77 | |
| 2.0.18 | 1 / 82 | |
| 2.0.17 | 1 / 82 | |
| 2.0.16 | 2 / 82 | |
| 2.0.15 | 2 / 82 | |
| 2.0.14 | 2 / 82 | |
| 2.0.13 | 2 / 82 | |
| 2.0.12 | 1 / 87 | |
| 2.0.11 | 1 / 98 | |
| 2.0.10 | 1 / 98 | |
| 2.0.9 | 1 / 98 | |
| 2.0.7 | 1 / 98 | |
| 2.0.6 | 1 / 98 | |
| 2.0.5 | 1 / 98 | |
| 2.0.4 | 1 / 100 | |
| 2.0.3 | 1 / 113 | |
| 1.23.2 | 1 / 118 | |
| 1.23.0 | 1 / 118 | |
| 1.22.0 | 2 / 125 | |
| 1.21.3 | 2 / 116 | |
| 1.21.2 | 2 / 117 | |
| 1.21.0 | 2 / 117 | |
| 1.20.29 | 2 / 114 | |
| 1.20.28 | 2 / 114 | |
| 1.20.27 | 2 / 114 | |
| 1.20.26 | 5 / 93 | |
| 1.20.25 | 5 / 93 | |
| 1.20.24 | 5 / 93 | |
| 1.20.23 | 5 / 93 | |
| 1.20.22 | 5 / 93 | |
| 1.20.21 | 5 / 93 | |
| 1.20.20 | 5 / 92 | |
| 1.20.19 | 5 / 92 | |
| 1.20.18 | 5 / 92 | |
| 1.20.17 | 5 / 93 | |
| 1.20.16 | 5 / 93 | |
| 1.20.15 | 5 / 24 | |
| 1.20.14 | 5 / 24 | |
| 1.20.13 | 5 / 24 | |
| 1.20.12 | 5 / 24 | |
| 1.20.11 | 5 / 24 | |
| 1.20.10 | 5 / 23 | |
| 1.20.9 | 5 / 23 | |
| 1.20.8 | 5 / 23 | |
| 1.20.5 | 5 / 21 | |
| 1.20.4 | 5 / 21 | |
| 1.20.3 | 5 / 21 | |
| 1.20.2 | 5 / 21 | |
| 1.20.1 | 5 / 21 | |
| 1.20.0 | 5 / 21 | |
| 1.19.18 | 5 / 21 | |
| 1.19.17 | 5 / 21 | |
| 1.19.16 | 5 / 21 | |
| 1.19.15 | 5 / 22 | |
| 1.19.14 | 8 / 10 | |
| 1.19.13 | 8 / 10 | |
| 1.19.12 | 8 / 10 | |
| 1.19.11 | 8 / 10 | |
| 1.19.10 | 8 / 10 | |
| 1.19.9 | 8 / 10 | |
| 1.19.8 | 8 / 10 | |
| 1.19.7 | 8 / 10 | |
| 1.19.6 | 8 / 10 | |
| 1.19.5 | 8 / 10 | |
| 1.19.4 | 8 / 10 | |
| 1.19.3 | 8 / 10 | |
| 1.19.2 | 8 / 10 | |
| 1.19.1 | 8 / 10 | |
| 1.19.0 | 8 / 10 | |
| 1.18.5 | 8 / 10 | |
| 1.18.4 | 8 / 10 | |
| 1.18.2 | 8 / 10 | |
| 1.18.1 | 9 / 10 | |
| 1.18.0 | 9 / 10 | |
| 1.17.7 | 9 / 10 | |
| 1.17.6 | 9 / 10 | |
| 1.17.3 | 9 / 10 | |
| 1.17.2 | 9 / 10 | |
| 1.17.1 | 9 / 10 | |
| 1.17.0 | 9 / 10 | |
| 1.16.26 | 9 / 10 | |
| 1.16.25 | 9 / 10 | |
| 1.16.24 | 9 / 10 | |
| 1.16.23 | 9 / 10 | |
| 1.16.22 | 9 / 10 | |
| 1.16.21 | 9 / 10 | |
| 1.16.20 | 9 / 10 | |
| 1.16.19 | 9 / 10 | |
| 1.16.18 | 9 / 10 | |
| 1.16.17 | 9 / 10 | |
| 1.16.16 | 9 / 10 | |
| 1.16.15 | 9 / 10 |
v4.0.5
2 findings[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-08, 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.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
2 findings[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 (atrouw) on 2026-07-02, 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.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.3
2 findings[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 (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.
v1.21.2
2 findings[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 (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.
v1.21.0
2 findings[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 (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.
v1.20.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.28
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-24, 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.
v1.20.27
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.
v1.20.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.21
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-17, 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.
v1.20.20
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 (xyo) on 2026-04-17, 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.
v1.20.19
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-16, 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.
v1.20.18
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-16, 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.
v1.20.17
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: jonesmac.
v1.20.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.10
2 findings[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-03-26, 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.
v1.20.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.8
2 findings[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 (xyo) than the most recent previously approved version (jonesmac) on 2026-03-24, 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.
v1.20.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.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.
v1.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.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.
v1.20.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.
v1.19.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.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.
v1.19.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.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.
v1.19.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
2 findings[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-01-29, 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.
v1.19.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.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.4
2 findings[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 (xyo) than the most recent previously approved version (joelbcarter) on 2026-01-26, 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.
v1.18.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.
v1.18.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.
v1.17.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.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.
v1.17.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.
v1.17.0
2 findings[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 (xyo) than the most recent previously approved version (jonesmac) on 2025-11-25, 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.
v1.16.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.