@react-form-builder/json-schema-generator
OptimaJet Form Builder Components - JSON schema generator
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:json-schema-typed | AI (phantom-deps): json-schema-typed is a declared runtime dependency used for type definitions; phantom-dep heuristic misfires here. | ai | |
| provenance | no-provenance | AI (provenance): Commercial vendor package; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 9.0.0 | 2 / 0 | |
| 8.1.0 | 2 / 0 | |
| 8.0.0 | 2 / 0 | |
| 7.15.0 | 2 / 0 | |
| 7.14.0 | 2 / 0 | |
| 7.13.0 | 2 / 0 | |
| 7.12.0 | 2 / 0 | |
| 7.11.0 | 2 / 0 | |
| 7.10.0 | 2 / 0 | |
| 7.9.0 | 2 / 0 |
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.