@json-render/react
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package transferred to Vercel Labs; vercel-release-bot is Vercel's standard CI/CD publisher. Repo URL confirms vercel-labs ownership. Transition is legitimate and stable going forward. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (matt.straka, vercel-release-bot) reflect legitimate transfer to Vercel Labs org, consistent with the repository URL pointing to github.com/vercel-labs. | ai | |
| provenance | missing-githead | AI (provenance): Package is from a known vercel-labs monorepo with a clean publisher history and no other risk signals; missing gitHead is likely a CI/CD environment change, not a supply chain concern. | ai | |
| provenance | no-provenance | AI (provenance): Published by vercel-release-bot, a trusted automated publisher with a long track record. Lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.19.0 | 1 / 6 | |
| 0.18.0 | 1 / 5 | |
| 0.17.0 | 1 / 5 | |
| 0.16.0 | 1 / 5 | |
| 0.15.0 | 1 / 5 | |
| 0.14.1 | 1 / 5 | |
| 0.14.0 | 1 / 5 | |
| 0.13.0 | 1 / 5 | |
| 0.12.1 | 1 / 5 | |
| 0.12.0 | 1 / 5 | |
| 0.11.0 | 1 / 5 | |
| 0.10.0 | 1 / 5 | |
| 0.9.1 | 1 / 5 | |
| 0.8.0 | 1 / 4 | |
| 0.7.0 | 1 / 4 | |
| 0.6.1 | 1 / 4 | |
| 0.6.0 | 1 / 4 | |
| 0.5.2 | 1 / 4 | |
| 0.5.1 | 1 / 4 | |
| 0.5.0 | 1 / 4 | |
| 0.4.4 | 1 / 4 | |
| 0.4.3 | 1 / 4 | |
| 0.4.2 | 1 / 4 | |
| 0.4.0 | 1 / 4 | |
| 0.2.0 | 1 / 4 | |
| 0.1.0 | 1 / 4 | |
| 0.0.1 | 1 / 4 |
v0.19.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-07. This could indicate a legitimate maintainer transition or an account compromise.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.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.
v0.16.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.
v0.14.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vercel-release-bot.
This version was published by a different npm account than previous versions on 2026-03-13. 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.