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, 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:json-loose | AI (dependencies): Same-author utility lib (carlosnz), low risk, used across his packages. | ai | |
| 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 100 of 100)
| Version | Deps | Published |
|---|---|---|
| 1.30.2 | 0 / 28 | |
| 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 | |
| 1.26.1 | 2 / 28 | |
| 1.26.0 | 2 / 28 | |
| 1.25.6 | 2 / 28 | |
| 1.25.5 | 2 / 29 | |
| 1.25.4 | 2 / 29 | |
| 1.25.3 | 2 / 29 | |
| 1.25.2 | 2 / 29 | |
| 1.25.1 | 2 / 29 | |
| 1.25.0 | 2 / 29 | |
| 1.24.0 | 2 / 29 | |
| 1.23.1 | 2 / 29 | |
| 1.23.0 | 2 / 29 | |
| 1.22.6 | 2 / 29 | |
| 1.22.5 | 2 / 29 | |
| 1.22.4 | 2 / 29 | |
| 1.22.3 | 2 / 29 | |
| 1.22.2 | 2 / 29 | |
| 1.22.1 | 2 / 29 | |
| 1.22.0 | 2 / 29 | |
| 1.21.2 | 2 / 29 | |
| 1.21.1 | 2 / 29 | |
| 1.20.0 | 2 / 26 | |
| 1.19.2 | 2 / 26 | |
| 1.19.1 | 2 / 26 | |
| 1.19.0 | 2 / 26 | |
| 1.18.0 | 2 / 25 | |
| 1.17.3 | 2 / 25 | |
| 1.17.2 | 2 / 25 | |
| 1.17.1 | 2 / 25 | |
| 1.17.0 | 2 / 25 | |
| 1.16.3 | 2 / 25 | |
| 1.16.2 | 2 / 25 | |
| 1.16.1 | 2 / 25 | |
| 1.16.0 | 2 / 25 | |
| 1.15.12 | 2 / 25 | |
| 1.15.11 | 2 / 25 | |
| 1.15.10 | 2 / 25 | |
| 1.15.9 | 2 / 25 | |
| 1.15.8 | 2 / 25 | |
| 1.15.7 | 2 / 25 | |
| 1.15.6 | 2 / 25 | |
| 1.15.5 | 2 / 25 | |
| 1.15.4 | 2 / 25 | |
| 1.15.3 | 2 / 25 | |
| 1.15.2 | 2 / 25 | |
| 1.15.1 | 2 / 25 | |
| 1.15.0 | 2 / 25 | |
| 1.14.1 | 3 / 25 | |
| 1.14.0 | 3 / 25 | |
| 1.13.3 | 3 / 25 | |
| 1.13.2 | 3 / 25 | |
| 1.13.1 | 3 / 25 | |
| 1.13.0 | 3 / 25 | |
| 1.12.0 | 4 / 24 | |
| 1.11.9 | 4 / 24 | |
| 1.11.8 | 4 / 24 | |
| 1.11.7 | 4 / 24 | |
| 1.11.6 | 4 / 24 | |
| 1.11.3 | 4 / 24 | |
| 1.11.0 | 4 / 24 | |
| 1.10.2 | 4 / 24 | |
| 1.9.3 | 4 / 24 | |
| 1.9.2 | 4 / 24 | |
| 1.9.1 | 4 / 23 | |
| 1.9.0 | 4 / 23 | |
| 1.8.4 | 4 / 23 | |
| 1.8.2 | 4 / 23 | |
| 1.8.1 | 4 / 23 | |
| 1.8.0 | 4 / 23 | |
| 1.7.2 | 4 / 23 | |
| 1.7.0 | 4 / 23 | |
| 1.6.1 | 4 / 23 | |
| 1.6.0 | 4 / 23 | |
| 1.5.3 | 4 / 23 | |
| 1.5.1 | 4 / 23 | |
| 1.5.0 | 4 / 23 | |
| 1.4.2 | 4 / 23 | |
| 1.4.0 | 4 / 23 | |
| 1.3.2 | 4 / 23 | |
| 1.3.0 | 4 / 15 | |
| 1.2.5 | 4 / 14 | |
| 1.2.4 | 4 / 14 | |
| 1.2.2 | 4 / 13 | |
| 1.2.0 | 4 / 13 | |
| 1.1.3 | 4 / 13 | |
| 1.1.1 | 4 / 13 | |
| 1.1.0 | 4 / 13 | |
| 1.0.0 | 4 / 13 |
v1.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.