@umijs/bundler-utils
See our website [umijs](https://umijs.org) for more information.
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires inside vendored express bundle; normal for a bundler-utils package that compiles its deps. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established UmiJS ecosystem package; sparse README/keywords are consistent across all versions. | ai | |
| dependencies | unvetted-dep:esbuild | AI (dependencies): esbuild is a well-known, widely-used bundler; pinned at 0.21.4 as a compiled dependency in this UmiJS monorepo package. No security concern. | ai | |
| dependencies | unvetted-dep:@umijs/utils | AI (dependencies): @umijs/utils is a sibling package in the same UmiJS monorepo, pinned at the same version. Expected and legitimate dependency. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in compiled/bundled es-module-lexer is expected minified output, not a payload obfuscation risk. | ai | |
| phantom-deps | phantom-dep:regenerate-unicode-properties | AI (phantom-deps): Same as regenerate — used indirectly via compiledConfig externals pattern in UmiJS monorepo packages. | ai | |
| phantom-deps | phantom-dep:regenerate | AI (phantom-deps): regenerate is declared as a dependency and mapped as an external in compiledConfig; it's intentionally passed through rather than bundled, not a phantom dep in the malicious sense. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() in bundled tapable is standard minified code pattern; not dynamic code execution from untrusted input. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.6.61 | 5 / 39 | |
| 4.6.59 | 5 / 39 | |
| 4.6.58 | 5 / 39 | |
| 4.6.57 | 5 / 39 | |
| 4.6.56 | 5 / 39 | |
| 4.6.1 | 5 / 39 |
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.