@xyo-network/react-chain-model
XYO Layer One React SDK Stake
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@xyo-network/react-chain | AI (dependencies): First-party sibling package from same org/monorepo, not third-party. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Added dep is first-party @xyo-network package, low risk. | ai | |
| provenance | publisher-changed | AI (provenance): atrouw has a large approved track record (1625 packages); likely org-level account transition for xylabs/xyo-network ecosystem. | ai | |
| dependencies | unvetted-dep:@xylabs/typeof | AI (dependencies): Same org (@xylabs) as the publisher; consistent namespace across all deps in this package. | ai | |
| provenance | no-provenance | AI (provenance): Established xylabs org package; lack of Sigstore provenance is consistent across their entire catalog. | ai |
Versions (showing 51 of 285)
| Version | Deps | Published |
|---|---|---|
| 4.0.5 | 1 / 70 | |
| 4.0.4 | 0 / 49 | |
| 4.0.3 | 0 / 49 | |
| 4.0.2 | 0 / 47 | |
| 4.0.1 | 0 / 47 | |
| 4.0.0 | 0 / 47 | |
| 3.0.2 | 0 / 49 | |
| 3.0.1 | 0 / 49 | |
| 3.0.0 | 0 / 47 | |
| 2.0.18 | 0 / 34 | |
| 2.0.17 | 0 / 34 | |
| 2.0.16 | 0 / 34 | |
| 2.0.15 | 0 / 34 | |
| 2.0.14 | 0 / 34 | |
| 2.0.13 | 0 / 34 | |
| 2.0.12 | 0 / 37 | |
| 2.0.11 | 0 / 37 | |
| 2.0.10 | 0 / 37 | |
| 2.0.9 | 0 / 37 | |
| 2.0.7 | 0 / 37 | |
| 2.0.6 | 0 / 37 | |
| 2.0.5 | 0 / 37 | |
| 2.0.4 | 0 / 36 | |
| 2.0.3 | 0 / 39 | |
| 2.0.1 | 0 / 57 | |
| 2.0.0 | 0 / 57 | |
| 1.23.2 | 0 / 57 | |
| 1.23.0 | 0 / 57 | |
| 1.22.0 | 0 / 62 | |
| 1.21.3 | 0 / 57 | |
| 1.21.2 | 0 / 57 | |
| 1.21.0 | 0 / 57 | |
| 1.20.29 | 0 / 58 | |
| 1.20.28 | 0 / 58 | |
| 1.20.27 | 0 / 58 | |
| 1.20.26 | 2 / 61 | |
| 1.20.23 | 2 / 61 | |
| 1.20.18 | 2 / 61 | |
| 1.20.16 | 2 / 62 | |
| 1.20.15 | 2 / 10 | |
| 1.20.14 | 2 / 10 | |
| 1.20.13 | 2 / 10 | |
| 1.20.12 | 2 / 10 | |
| 1.20.11 | 2 / 10 | |
| 1.20.10 | 2 / 9 | |
| 1.20.9 | 2 / 9 | |
| 1.20.8 | 2 / 9 | |
| 1.20.5 | 2 / 10 | |
| 1.20.4 | 2 / 10 | |
| 1.20.3 | 2 / 10 | |
| 1.20.2 | 2 / 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.