@formio/vpat
VPAT module for form.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
Keywords
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.8.0 | 0 / 22 | |
| 2.7.6 | 0 / 22 | |
| 2.7.5 | 0 / 22 | |
| 2.7.4 | 0 / 22 | |
| 2.7.3 | 0 / 22 | |
| 2.7.2 | 0 / 22 | |
| 2.7.1 | 0 / 22 | |
| 2.7.0 | 0 / 22 | |
| 2.6.4 | 0 / 22 | |
| 2.6.3 | 0 / 22 | |
| 2.6.2 | 0 / 22 | |
| 2.6.1 | 0 / 22 |
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.