@xylabs/react-json-viewer
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 intentionally converted to a tiny re-export shim per package.json description. | ai | |
| dependencies | unvetted-dep:@ariestools/sdk-react | AI (dependencies): Sibling package from the same org that this shim now re-exports. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 11.0.1 | 1 / 12 | |
| 11.0.0 | 1 / 27 | |
| 10.0.5 | 1 / 27 | |
| 10.0.3 | 1 / 26 | |
| 10.0.2 | 1 / 26 | |
| 10.0.1 | 0 / 16 | |
| 10.0.0 | 0 / 16 | |
| 9.1.2 | 0 / 16 | |
| 9.1.1 | 0 / 16 | |
| 9.1.0 | 0 / 16 | |
| 9.0.4 | 0 / 16 | |
| 9.0.3 | 0 / 16 | |
| 9.0.2 | 0 / 16 | |
| 9.0.1 | 0 / 16 | |
| 9.0.0 | 0 / 13 | |
| 8.0.4 | 0 / 13 | |
| 8.0.3 | 0 / 13 | |
| 8.0.2 | 0 / 13 | |
| 8.0.1 | 0 / 13 |
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
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-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.