@formio/vue
A vue.js renderer for form.io forms.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped @formio/vue is a legitimate formio org package; Levenshtein match to 'vite' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @formio/vue is a legitimate formio org package; Levenshtein match to 'yup' is coincidental. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 1 / 14 | |
| 6.1.6 | 1 / 14 | |
| 6.1.5 | 1 / 14 | |
| 6.1.4 | 1 / 14 | |
| 6.1.3 | 1 / 14 | |
| 6.1.2 | 1 / 14 | |
| 6.1.1 | 1 / 14 | |
| 6.1.0 | 1 / 14 | |
| 6.0.4 | 1 / 14 | |
| 6.0.3 | 1 / 14 | |
| 6.0.2 | 1 / 14 | |
| 6.0.1 | 1 / 14 |
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.