json-edit-react
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:object-property-assigner | AI (dependencies): Same-author utility package; purpose-fit for this JSON editor component, stable pattern across versions. | ai | |
| dependencies | unvetted-dep:object-property-extractor | AI (dependencies): Same-author utility package; purpose-fit for this JSON editor component, stable pattern across versions. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.30.1 | 0 / 28 | |
| 1.30.0 | 0 / 28 | |
| 1.29.1 | 2 / 28 | |
| 1.29.0 | 2 / 28 | |
| 1.28.2 | 2 / 28 | |
| 1.28.1 | 2 / 28 | |
| 1.28.0 | 2 / 28 | |
| 1.27.2 | 2 / 28 | |
| 1.27.1 | 2 / 28 | |
| 1.27.0 | 2 / 28 | |
| 1.26.2 | 2 / 28 |
v1.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.