@umijs/bundler-esbuild
@umijs/bundler-esbuild
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
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): Monorepo package with minimal README; stable pattern for @umijs/* scoped packages. | ai | |
| dependencies | unvetted-dep:enhanced-resolve | AI (dependencies): enhanced-resolve is a well-known webpack resolver utility; not a risk for this package. | ai | |
| dependencies | unvetted-dep:postcss-preset-env | AI (dependencies): postcss-preset-env is a standard PostCSS plugin; not a risk for this package. | ai | |
| dependencies | unvetted-dep:postcss | AI (dependencies): postcss is a widely-used, well-established CSS tooling package; not a risk for this package. | ai | |
| dependencies | unvetted-dep:@umijs/bundler-utils | AI (dependencies): Sibling package in the UmiJS monorepo; legitimate dependency. | ai | |
| dependencies | unvetted-dep:@umijs/utils | AI (dependencies): Internal monorepo dependency at matching version; stable pattern for umi packages. | ai | |
| dependencies | unvetted-dep:postcss-flexbugs-fixes | AI (dependencies): postcss-flexbugs-fixes is a standard PostCSS plugin; not a risk for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.6.61 | 6 / 1 | |
| 4.6.59 | 6 / 1 | |
| 4.6.58 | 6 / 1 | |
| 4.6.57 | 6 / 1 | |
| 4.6.56 | 6 / 1 | |
| 4.6.1 | 6 / 1 |
v4.6.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.