@rollup/plugin-json
Convert .json files to ES6 modules
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established rollup official plugin published by long-standing maintainer; lack of Sigstore provenance is a process gap, not a security risk for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 6.1.0 | 1 / 4 | |
| 6.0.1 | 1 / 4 | |
| 6.0.0 | 1 / 4 | |
| 5.0.2 | 1 / 4 | |
| 5.0.1 | 1 / 4 | |
| 5.0.0 | 1 / 4 | |
| 4.1.0 | 1 / 3 | |
| 4.0.3 | 1 / 3 | |
| 4.0.2 | 1 / 3 | |
| 4.0.1 | 1 / 3 | |
| 4.0.0 | 1 / 3 |
v6.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shellscape.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.