@unovis/vue
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 package @unovis/vue is a legitimate F5 data viz library; Levenshtein match to 'vite' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @unovis/vue is a legitimate F5 data viz library; Levenshtein match to 'yup' is coincidental. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.6.5 | 0 / 19 | |
| 1.6.4 | 0 / 18 | |
| 1.6.2 | 0 / 16 | |
| 1.6.1 | 0 / 16 | |
| 1.6.0 | 0 / 16 | |
| 1.5.2 | 0 / 16 |
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.