@umijs/preset-vue
@umijs/preset-vue
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-bulk-read | AI (semgrep): Fires inside vendored @vitejs/plugin-vue bundle; expected config-library behavior, stable across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package with minimal README/description; not indicative of spam or malice. | ai |
Versions (showing 11 of 211)
| Version | Deps | Published |
|---|---|---|
| 4.0.47 | 4 / 2 | |
| 4.0.46 | 4 / 2 | |
| 4.0.45 | 4 / 2 | |
| 4.0.44 | 4 / 2 | |
| 4.0.43 | 4 / 2 | |
| 4.0.42 | 4 / 2 | |
| 4.0.41 | 4 / 2 | |
| 4.0.40 | 4 / 2 | |
| 4.0.39 | 4 / 2 | |
| 4.0.38 | 4 / 2 | |
| 4.0.37 | 4 / 2 |
v4.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.