@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 58 of 158)
| Version | Deps | Published |
|---|---|---|
| 1.16.14 | 9 / 10 | |
| 1.16.13 | 9 / 10 | |
| 1.16.12 | 9 / 10 | |
| 1.16.11 | 9 / 10 | |
| 1.16.10 | 11 / 10 | |
| 1.16.9 | 11 / 10 | |
| 1.16.8 | 11 / 10 | |
| 1.16.7 | 11 / 10 | |
| 1.16.6 | 11 / 10 | |
| 1.16.5 | 11 / 10 | |
| 1.16.4 | 11 / 10 | |
| 1.16.3 | 11 / 10 | |
| 1.16.2 | 11 / 10 | |
| 1.16.1 | 11 / 10 | |
| 1.16.0 | 11 / 10 | |
| 1.15.28 | 11 / 10 | |
| 1.15.27 | 11 / 10 | |
| 1.15.26 | 11 / 10 | |
| 1.15.25 | 11 / 10 | |
| 1.15.24 | 11 / 10 | |
| 1.15.23 | 11 / 10 | |
| 1.15.22 | 11 / 10 | |
| 1.15.21 | 11 / 10 | |
| 1.15.20 | 11 / 10 | |
| 1.15.19 | 11 / 10 | |
| 1.15.18 | 11 / 10 | |
| 1.15.17 | 11 / 10 | |
| 1.15.16 | 11 / 10 | |
| 1.15.15 | 11 / 10 | |
| 1.15.14 | 11 / 10 | |
| 1.15.13 | 11 / 10 | |
| 1.15.12 | 11 / 10 | |
| 1.15.11 | 11 / 10 | |
| 1.15.10 | 11 / 10 | |
| 1.15.9 | 11 / 10 | |
| 1.15.8 | 11 / 10 | |
| 1.15.7 | 11 / 10 | |
| 1.15.6 | 11 / 10 | |
| 1.15.5 | 11 / 10 | |
| 1.15.4 | 11 / 10 | |
| 1.15.3 | 11 / 10 | |
| 1.15.2 | 12 / 10 | |
| 1.15.1 | 12 / 10 | |
| 1.15.0 | 12 / 10 | |
| 1.14.4 | 12 / 10 | |
| 1.14.3 | 12 / 10 | |
| 1.14.2 | 12 / 10 | |
| 1.14.1 | 12 / 10 | |
| 1.14.0 | 12 / 10 | |
| 1.13.0 | 12 / 10 | |
| 1.12.14 | 12 / 10 | |
| 1.12.13 | 12 / 10 | |
| 1.12.12 | 12 / 10 | |
| 1.12.11 | 12 / 10 | |
| 1.12.10 | 12 / 10 | |
| 1.12.9 | 12 / 10 | |
| 1.12.8 | 12 / 10 | |
| 1.12.7 | 3 / 19 |
v1.16.14
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.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.16.11
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.10
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.9
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.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.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.16.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.16.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.16.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.
v1.16.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.16.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.16.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.15.28
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.15.27
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.15.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.15.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.15.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.15.23
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.15.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.15.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.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.15.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.15.18
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.15.17
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.15.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.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.15.14
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.15.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.15.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.10
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.15.8
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.15.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.15.6
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-10-15, 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.15.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.15.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.
v1.15.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.15.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.15.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.15.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.14.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.14.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.14.1
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-08-28, 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.14.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-08-28, 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.13.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.12.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.12.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.12.11
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.12.10
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.12.9
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.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.