@formio/grid
The core Form.io grid.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @formio/grid is not a typosquat of uuid; Levenshtein match is a false positive for scoped names. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 2 / 20 | |
| 2.2.6 | 2 / 20 | |
| 2.2.5 | 2 / 20 | |
| 2.2.4 | 2 / 20 | |
| 2.2.3 | 2 / 20 | |
| 2.2.2 | 2 / 20 | |
| 2.2.1 | 2 / 20 | |
| 2.2.0 | 2 / 20 | |
| 2.1.6 | 2 / 20 | |
| 2.1.5 | 2 / 20 | |
| 2.1.4 | 2 / 20 |
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.