@xylabs/react-error
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
Keywords
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 explicitly declared as re-export shim; drop matches stated purpose. | ai | |
| dependencies | unvetted-dep:@ariestools/sdk-react | AI (dependencies): Sibling package from same publisher, intended re-export target. | ai | |
| provenance | missing-githead | AI (provenance): High-volume XY Labs publisher with clean track record; likely CI environment change, not a supply-chain indicator. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All three new deps are established, widely-used packages appropriate for a React error UI library. | ai | |
| provenance | publisher-changed | AI (provenance): jonesmac is an established XY Labs publisher with 896 approved packages; transition from xyo appears to be a legitimate org-level handoff. | ai | |
| provenance | no-provenance | AI (provenance): XY Labs packages consistently lack provenance; stable false positive for this org. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 11.0.1 | 1 / 14 | |
| 11.0.0 | 1 / 29 | |
| 10.0.5 | 1 / 29 | |
| 10.0.3 | 1 / 28 | |
| 10.0.2 | 1 / 28 | |
| 10.0.1 | 3 / 23 | |
| 10.0.0 | 3 / 23 | |
| 9.1.2 | 3 / 23 | |
| 9.1.1 | 3 / 23 | |
| 9.1.0 | 3 / 23 | |
| 9.0.4 | 3 / 29 | |
| 9.0.3 | 3 / 29 | |
| 9.0.2 | 3 / 30 | |
| 9.0.1 | 3 / 30 | |
| 9.0.0 | 3 / 33 | |
| 8.0.4 | 3 / 33 | |
| 8.0.3 | 3 / 33 | |
| 8.0.2 | 3 / 33 | |
| 8.0.1 | 3 / 33 | |
| 8.0.0 | 3 / 33 | |
| 7.2.5 | 3 / 33 | |
| 7.2.4 | 3 / 33 | |
| 7.2.3 | 3 / 33 | |
| 7.2.2 | 3 / 33 | |
| 7.2.1 | 3 / 35 | |
| 7.2.0 | 3 / 35 | |
| 7.1.20 | 6 / 24 | |
| 7.1.17 | 4 / 18 | |
| 7.1.16 | 4 / 18 | |
| 7.1.15 | 4 / 18 | |
| 7.1.14 | 4 / 18 | |
| 7.1.13 | 4 / 18 | |
| 7.1.12 | 4 / 18 | |
| 7.1.11 | 4 / 17 | |
| 7.1.10 | 4 / 17 | |
| 7.1.9 | 4 / 17 |
v11.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.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 (jonesmac) on 2026-06-30, 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.