@crystaldesign/forms
A wrapper to the generic forms library Jsonforms.io.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Commercial private library; missing repo/README metadata is expected for internal packages across all versions. | ai | |
| dependencies | unvetted-dep:@jsonforms/vanilla-renderers | AI (dependencies): Legitimate JSON Forms ecosystem dependency; stable pattern across this package's versions. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @crystaldesign/forms is not a typosquat of cors; edit-distance match is coincidental. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 26.5.3 | 5 / 4 | |
| 26.5.2 | 5 / 4 | |
| 26.5.1 | 5 / 4 | |
| 26.5.0 | 5 / 4 | |
| 26.4.8 | 5 / 4 | |
| 26.4.7 | 5 / 4 | |
| 26.4.6 | 5 / 4 | |
| 26.4.5 | 5 / 4 | |
| 26.4.4 | 5 / 4 | |
| 26.4.3 | 5 / 4 | |
| 26.4.2 | 5 / 4 | |
| 26.4.1 | 5 / 4 | |
| 26.4.0 | 5 / 4 | |
| 26.3.2 | 5 / 4 | |
| 26.3.1 | 5 / 4 | |
| 26.3.0 | 5 / 4 | |
| 26.2.4 | 5 / 4 | |
| 26.2.3 | 5 / 4 | |
| 26.2.2 | 5 / 4 | |
| 26.2.1 | 5 / 4 | |
| 26.2.0 | 5 / 4 | |
| 26.1.2 | 5 / 4 | |
| 26.1.1 | 5 / 4 | |
| 26.1.0 | 5 / 4 | |
| 25.16.2 | 5 / 4 | |
| 25.16.1 | 5 / 4 | |
| 25.16.0 | 5 / 4 | |
| 25.14.4 | 5 / 4 | |
| 25.14.3 | 5 / 4 | |
| 25.14.2 | 5 / 4 | |
| 25.14.1 | 5 / 4 | |
| 25.14.0 | 5 / 4 | |
| 25.13.7 | 5 / 4 | |
| 25.13.6 | 5 / 4 | |
| 25.13.5 | 5 / 4 | |
| 25.13.4 | 5 / 4 | |
| 25.13.3 | 5 / 4 | |
| 25.13.2 | 5 / 4 |
v26.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.