@ai-sdk/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): @ai-sdk/vue is a legitimate scoped package in the Vercel AI SDK; Levenshtein match to 'vite' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @ai-sdk/vue is a legitimate scoped package in the Vercel AI SDK; Levenshtein match to 'yup' is a false positive. | ai |
Versions (showing 14 of 325)
| Version | Deps | Published |
|---|---|---|
| 2.0.96 | 3 / 14 | |
| 2.0.95 | 3 / 14 | |
| 2.0.94 | 3 / 14 | |
| 2.0.93 | 3 / 14 | |
| 2.0.92 | 3 / 14 | |
| 2.0.91 | 3 / 14 | |
| 2.0.90 | 3 / 14 | |
| 2.0.89 | 3 / 14 | |
| 2.0.88 | 3 / 14 | |
| 2.0.87 | 3 / 14 | |
| 2.0.86 | 3 / 13 | |
| 2.0.85 | 3 / 13 | |
| 2.0.84 | 3 / 13 | |
| 2.0.83 | 3 / 13 |
v2.0.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.