@floating-ui/vue
Supply chain provenance
Status for the latest visible version.
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): @floating-ui/vue is the official Vue adapter for Floating UI; the Levenshtein similarity to 'vite' is purely coincidental and not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @floating-ui/vue is the official Vue adapter for Floating UI; the Levenshtein similarity to 'yup' is purely coincidental and not a typosquat. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.1.11 | 3 / 6 | |
| 1.1.10 | 3 / 6 | |
| 1.1.9 | 3 / 6 | |
| 1.1.8 | 3 / 6 | |
| 1.1.7 | 3 / 6 |
v1.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.