@json-render/core
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): Publisher change from ctate to vercel-release-bot reflects legitimate transfer to Vercel Labs automation; repo URL confirms vercel-labs org ownership. Stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (matt.straka, vercel-release-bot) are consistent with Vercel Labs org adoption of this package. No malicious indicators. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead reflects a CI pipeline change by vercel-release-bot; consistent with automated release tooling. No other indicators of compromise. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @json-render/core is unrelated to the cors middleware; the name match is coincidental and this is a stable false positive for this package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 0.19.0 | 1 / 3 | |
| 0.18.0 | 1 / 3 | |
| 0.17.0 | 1 / 3 | |
| 0.16.0 | 1 / 3 | |
| 0.15.0 | 1 / 3 | |
| 0.14.1 | 1 / 3 | |
| 0.14.0 | 1 / 3 | |
| 0.13.0 | 1 / 3 | |
| 0.12.1 | 1 / 3 | |
| 0.12.0 | 1 / 3 | |
| 0.11.0 | 1 / 3 | |
| 0.10.0 | 1 / 3 | |
| 0.9.1 | 1 / 3 | |
| 0.9.0 | 1 / 3 | |
| 0.8.0 | 1 / 3 | |
| 0.7.0 | 1 / 3 | |
| 0.6.1 | 1 / 3 | |
| 0.6.0 | 1 / 3 | |
| 0.5.2 | 1 / 3 | |
| 0.5.1 | 1 / 3 | |
| 0.5.0 | 1 / 3 | |
| 0.4.4 | 1 / 3 | |
| 0.4.3 | 1 / 3 | |
| 0.4.2 | 1 / 3 | |
| 0.4.0 | 1 / 3 | |
| 0.3.0 | 1 / 3 | |
| 0.2.0 | 1 / 3 | |
| 0.1.0 | 1 / 3 | |
| 0.0.1 | 1 / 3 |
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
2 findingsPackage name '@json-render/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.