@xyo-network/xl1-react-transaction
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 |
|---|---|---|---|---|
| source-diff | source-size-dropped | AI (source-diff): Package.json declares this is now a deprecated shim redirecting to react-chain, explaining the stub size. | ai | |
| dependencies | unvetted-dep:@xyo-network/react-chain | AI (dependencies): Same-org sibling package, the shim's replacement target. | ai | |
| phantom-deps | phantom-dep:@mui/icons-material | AI (phantom-deps): Used via config/build, consistent with UI shim package. | ai | |
| phantom-deps | phantom-dep:@xyo-network/xl1-sdk | AI (phantom-deps): Same org scope, expected transitive re-export in shim. | ai | |
| bogus-package | bogus-package | AI (bogus-package): XYO Network org package with legitimate repo and author; README template pattern is stable across their packages. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to org account 'xyo' with 155 approved packages; consistent with org-level publishing consolidation for @xyo-network namespace. | ai |
Versions (showing 51 of 94)
| Version | Deps | Published |
|---|---|---|
| 4.0.5 | 3 / 69 | |
| 4.0.4 | 0 / 42 | |
| 4.0.3 | 0 / 42 | |
| 4.0.2 | 0 / 41 | |
| 4.0.1 | 0 / 41 | |
| 4.0.0 | 0 / 40 | |
| 3.0.2 | 0 / 42 | |
| 3.0.1 | 0 / 42 | |
| 3.0.0 | 0 / 42 | |
| 2.0.18 | 0 / 44 | |
| 2.0.17 | 0 / 44 | |
| 2.0.16 | 0 / 44 | |
| 2.0.15 | 0 / 44 | |
| 2.0.14 | 0 / 44 | |
| 2.0.13 | 0 / 44 | |
| 2.0.12 | 0 / 47 | |
| 2.0.11 | 0 / 47 | |
| 2.0.10 | 0 / 47 | |
| 2.0.9 | 0 / 47 | |
| 2.0.7 | 0 / 47 | |
| 2.0.6 | 0 / 47 | |
| 2.0.5 | 0 / 47 | |
| 2.0.4 | 0 / 46 | |
| 2.0.3 | 0 / 49 | |
| 2.0.1 | 0 / 67 | |
| 2.0.0 | 0 / 67 | |
| 1.23.2 | 0 / 67 | |
| 1.23.0 | 0 / 67 | |
| 1.22.0 | 0 / 73 | |
| 1.21.3 | 0 / 67 | |
| 1.21.2 | 0 / 67 | |
| 1.21.0 | 0 / 67 | |
| 1.20.29 | 0 / 72 | |
| 1.20.28 | 0 / 72 | |
| 1.20.27 | 0 / 72 | |
| 1.20.26 | 2 / 75 | |
| 1.20.25 | 2 / 75 | |
| 1.20.24 | 2 / 75 | |
| 1.20.23 | 2 / 75 | |
| 1.20.22 | 2 / 75 | |
| 1.20.21 | 2 / 75 | |
| 1.20.20 | 2 / 75 | |
| 1.20.19 | 2 / 75 | |
| 1.20.18 | 2 / 75 | |
| 1.20.17 | 2 / 76 | |
| 1.20.16 | 2 / 76 | |
| 1.20.15 | 0 / 24 | |
| 1.20.14 | 0 / 24 | |
| 1.20.13 | 0 / 24 | |
| 1.20.12 | 0 / 24 | |
| 1.20.11 | 0 / 24 |
v4.0.5
2 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
2 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.