← Home

@umijs/utils

See our website [umijs](https://umijs.org) for more information.

3
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

sorryccchenshuai2144kuitospeachscriptxiaohuoniyifankakaxixierenyuanxusd320zoomdong07

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Bundled execa dependency; env-spread is standard for process spawning utilities. ai
semgrep semgrep:child-process-import AI (semgrep): Bundled deps (address, execa, cross-spawn) legitimately use child_process. ai
semgrep semgrep:env-bulk-read AI (semgrep): Bundled debug library reads DEBUG env var; standard pattern. ai
semgrep semgrep:child-process-spawn AI (semgrep): Bundled execa uses spawn; core functionality of that dep. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Bundled import-lazy uses Reflect.get for lazy loading; documented pattern. ai
semgrep semgrep:dynamic-require AI (semgrep): Bundled tsconfig-paths resolves paths dynamically; expected behavior. ai
bogus-package bogus-package AI (bogus-package): Established umi framework package; low-value signals are false positives. ai

Versions (showing 3 of 3)

Version Deps Published
4.6.57 2 / 46
4.6.56 2 / 46
4.5.3 2 / 46

v4.6.57

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.6.56

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: peachscript → zoomdong07 (on 2026-05-25, known maintainer) provenance

This version was published by a different npm account (zoomdong07) than the most recent previously approved version (peachscript) on 2026-05-25, but zoomdong07 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.5.3

2 findings
HIGH env-spread: compiled/execa/index.js:1 semgrep

Spreading entire process.env into an object — may capture all secrets > 1 | (function(){var e={782:function(e,t,n){"use strict";const{PassThrough:r}=n(781);e.exports=e=>{e={...e};const{array:t}=e;

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.