@umijs/babel-plugin-import-to-await-require
@umijs/babel-plugin-import-to-await-require
1
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
xusd320yifankakaxixierenyuanstormslowlyxiefengniansorryccchenshuai2144kuitospeachscriptxiaohuoni
Keywords
umi
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Part of the umijs monorepo; sparse README/description is a known pattern for internal scoped packages. | ai | |
| dependencies | unvetted-dep:@umijs/utils | AI (dependencies): Sibling package from the same umijs monorepo; version-locked to the same release. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 3.5.43 | 1 / 1 |
v3.5.43
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.