@umijs/bundler-utils
See our website [umijs](https://umijs.org) for more information.
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established umijs package; publish-env metadata change, no behavioral risk. | ai | |
| source-diff | net-exec-file:compiled/babel/index.js | AI (source-diff): vendored babel bundle; net+eval are legitimate parser internals | ai | |
| source-diff | obfuscated-file:compiled/babel/index.js | AI (source-diff): webpack-bundled vendored babel; noMinify/compiled build output, stable across versions | ai | |
| source-diff | obfuscated-file:compiled/express/index.js | AI (source-diff): bundled express vendor output | ai | |
| source-diff | net-exec-file:compiled/express/index.js | AI (source-diff): bundled express vendor output | ai | |
| source-diff | obfuscated-file:compiled/less/index.js | AI (source-diff): bundled less vendor output | ai | |
| source-diff | net-exec-file:compiled/less/index.js | AI (source-diff): bundled less vendor output | ai | |
| source-diff | obfuscated-file:compiled/cjs-module-lexer/index.js | AI (source-diff): bundled cjs-module-lexer vendor output | ai | |
| source-diff | obfuscated-file:compiled/es-module-lexer/index.js | AI (source-diff): bundled es-module-lexer wasm vendor output | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval in vendored express/depd internals, not injected | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established UmiJS ecosystem package; sparse README/keywords are consistent across all versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires inside vendored express bundle; normal for a bundler-utils package that compiles its deps. | 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:new-function-constructor | AI (semgrep): new Function() in bundled tapable is standard minified code pattern; not dynamic code execution from untrusted input. | 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 |
Versions (showing 51 of 219)
| Version | Deps | Published |
|---|---|---|
| 4.6.82 | 5 / 39 | |
| 4.6.81 | 5 / 39 | |
| 4.6.80 | 5 / 39 | |
| 4.6.79 | 5 / 39 | |
| 4.6.78 | 5 / 39 | |
| 4.6.77 | 5 / 39 | |
| 4.6.76 | 5 / 39 | |
| 4.6.75 | 5 / 39 | |
| 4.6.74 | 5 / 39 | |
| 4.6.73 | 5 / 39 | |
| 4.6.72 | 5 / 39 | |
| 4.6.71 | 5 / 39 | |
| 4.6.70 | 5 / 39 | |
| 4.6.69 | 5 / 39 | |
| 4.6.68 | 5 / 39 | |
| 4.6.67 | 5 / 39 | |
| 4.6.66 | 5 / 39 | |
| 4.6.65 | 5 / 39 | |
| 4.6.64 | 5 / 39 | |
| 4.6.63 | 5 / 39 | |
| 4.6.62 | 5 / 39 | |
| 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.55 | 5 / 39 | |
| 4.6.54 | 5 / 39 | |
| 4.6.53 | 5 / 39 | |
| 4.6.52 | 5 / 39 | |
| 4.6.51 | 5 / 39 | |
| 4.6.50 | 5 / 39 | |
| 4.6.49 | 5 / 39 | |
| 4.6.48 | 5 / 39 | |
| 4.6.47 | 5 / 39 | |
| 4.6.46 | 5 / 39 | |
| 4.6.45 | 5 / 39 | |
| 4.6.44 | 5 / 39 | |
| 4.6.43 | 5 / 39 | |
| 4.6.42 | 5 / 39 | |
| 4.6.41 | 5 / 39 | |
| 4.6.40 | 5 / 39 | |
| 4.6.39 | 5 / 39 | |
| 4.6.38 | 5 / 39 | |
| 4.6.37 | 5 / 39 | |
| 4.6.36 | 5 / 39 | |
| 4.6.35 | 5 / 39 | |
| 4.6.34 | 5 / 39 | |
| 4.6.33 | 5 / 39 | |
| 4.6.32 | 5 / 39 | |
| 4.6.31 | 5 / 39 |
v4.6.82
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.81
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.80
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.79
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.78
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.77
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.76
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.75
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.74
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.73
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.72
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.71
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.70
2 findingsThis version was published by a different npm account than previous versions on 2026-07-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.47
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.46
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.45
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.44
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.43
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.42
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.41
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.40
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.39
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.38
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.37
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.36
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.35
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.34
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.33
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.32
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.31
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.