@xyo-network/react-schema
Common React library for all XYO projects that use React
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@xylabs/react-select | AI (dependencies): First-party xylabs ecosystem dep; stable pattern across all XYO package versions. | ai | |
| dependencies | unvetted-dep:@xyo-network/node-core-types | AI (dependencies): First-party xyo-network ecosystem dep; stable pattern across all XYO package versions. | ai | |
| dependencies | unvetted-dep:@xyo-network/diviner-schema-list-model | AI (dependencies): First-party xyo-network ecosystem dep; stable pattern across all XYO package versions. | ai | |
| dependencies | unvetted-dep:@xyo-network/diviner-schema-stats-model | AI (dependencies): First-party xyo-network ecosystem dep; stable pattern across all XYO package versions. | ai | |
| provenance | no-provenance | AI (provenance): XYO monorepo packages consistently lack provenance; stable false positive for this package family. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 9.0.5 | 3 / 77 | |
| 9.0.4 | 3 / 76 | |
| 9.0.2 | 3 / 89 | |
| 9.0.1 | 3 / 92 | |
| 8.0.1 | 3 / 95 | |
| 8.0.0 | 3 / 95 | |
| 7.6.3 | 3 / 95 | |
| 7.6.2 | 3 / 96 | |
| 7.6.1 | 3 / 96 | |
| 7.6.0 | 3 / 96 | |
| 7.5.12 | 3 / 92 | |
| 7.5.11 | 3 / 92 | |
| 7.5.7 | 18 / 27 | |
| 7.5.6 | 18 / 26 | |
| 7.5.4 | 18 / 26 |
v9.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.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 (atrouw) than the most recent previously approved version (jonesmac) on 2026-06-02, 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.
v9.0.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 (jonesmac) than the most recent previously approved version (atrouw) on 2026-06-01, 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.
v8.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.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.
v7.6.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.
v7.6.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.
v7.5.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.
v7.5.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.
v7.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.