@umijs/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): Manual publish by known maintainer; gitHead absence stable for this workflow. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Vendored compiled deps inflate size legitimately. | ai | |
| source-diff | large-new-source-files | AI (source-diff): compiled/ vendor bundles; expected for this package's build model. | ai | |
| source-diff | net-exec-file:compiled/lodash/index.js | AI (source-diff): lodash bundle; benign vendored dep. | ai | |
| source-diff | net-exec-file:compiled/prettier/index.js | AI (source-diff): prettier bundle; net+exec is inherent to the vendored tool, no hostile target. | ai | |
| source-diff | obfuscated-file:compiled/prettier/index.js | AI (source-diff): Bundled vendor dep under documented compiled/ dir; minified, not obfuscated. | ai | |
| phantom-deps | phantom-dep:@types/lodash | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| phantom-deps | phantom-dep:@types/mkdirp | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| phantom-deps | phantom-dep:@types/rimraf | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| phantom-deps | phantom-dep:@types/got | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| phantom-deps | phantom-dep:@types/glob | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| phantom-deps | phantom-dep:@types/color | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| phantom-deps | phantom-dep:@types/debug | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| phantom-deps | phantom-dep:@types/yargs | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| phantom-deps | phantom-dep:@types/semver | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| phantom-deps | phantom-dep:@types/cheerio | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| phantom-deps | phantom-dep:@types/resolve | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| phantom-deps | phantom-dep:@types/signale | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| phantom-deps | phantom-dep:@types/mustache | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| phantom-deps | phantom-dep:@types/cross-spawn | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| phantom-deps | phantom-dep:@types/yargs-parser | AI (phantom-deps): Type re-export package; @types/* deps loaded by convention not direct import. | ai | |
| 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 | |
| bogus-package | bogus-package | AI (bogus-package): Established umi framework package; low-value signals are false positives. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Bundled tsconfig-paths resolves paths dynamically; expected behavior. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Bundled import-lazy uses Reflect.get for lazy loading; documented pattern. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): Bundled execa uses spawn; core functionality of that dep. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Bundled debug library reads DEBUG env var; standard pattern. | ai |
Versions (showing 76 of 176)
| Version | Deps | Published |
|---|---|---|
| 3.4.8 | 1 / 0 | |
| 3.4.7 | 1 / 0 | |
| 3.4.6 | 1 / 0 | |
| 3.4.5 | 1 / 0 | |
| 3.4.4 | 1 / 0 | |
| 3.4.3 | 1 / 0 | |
| 3.4.2 | 1 / 0 | |
| 3.4.1 | 1 / 0 | |
| 3.4.0 | 1 / 0 | |
| 3.3.15 | 44 / 0 | |
| 3.3.14 | 43 / 0 | |
| 3.3.12 | 43 / 0 | |
| 3.3.10 | 43 / 0 | |
| 3.3.9 | 43 / 0 | |
| 3.3.8 | 43 / 0 | |
| 3.3.7 | 43 / 0 | |
| 3.3.6 | 43 / 0 | |
| 3.3.5 | 43 / 0 | |
| 3.3.4 | 43 / 0 | |
| 3.3.3 | 43 / 0 | |
| 3.3.2 | 43 / 0 | |
| 3.3.1 | 43 / 0 | |
| 3.3.0 | 43 / 0 | |
| 3.2.28 | 43 / 0 | |
| 3.2.27 | 43 / 0 | |
| 3.2.26 | 43 / 0 | |
| 3.2.25 | 43 / 0 | |
| 3.2.24 | 43 / 0 | |
| 3.2.23 | 43 / 0 | |
| 3.2.22 | 43 / 0 | |
| 3.2.21 | 43 / 0 | |
| 3.2.20 | 43 / 0 | |
| 3.2.19 | 43 / 0 | |
| 3.2.18 | 43 / 0 | |
| 3.2.17 | 43 / 0 | |
| 3.2.16 | 43 / 0 | |
| 3.2.15 | 43 / 0 | |
| 3.2.14 | 43 / 0 | |
| 3.2.13 | 43 / 0 | |
| 3.2.12 | 43 / 0 | |
| 3.2.11 | 43 / 0 | |
| 3.2.10 | 43 / 0 | |
| 3.2.9 | 43 / 0 | |
| 3.2.8 | 43 / 0 | |
| 3.2.7 | 43 / 0 | |
| 3.2.6 | 43 / 0 | |
| 3.2.5 | 43 / 0 | |
| 3.2.4 | 43 / 0 | |
| 3.2.3 | 43 / 0 | |
| 3.2.2 | 43 / 0 | |
| 3.2.1 | 43 / 0 | |
| 3.2.0 | 43 / 0 | |
| 3.1.4 | 43 / 0 | |
| 3.1.3 | 43 / 0 | |
| 3.1.2 | 43 / 0 | |
| 3.1.1 | 43 / 0 | |
| 3.1.0 | 43 / 0 | |
| 3.0.18 | 43 / 0 | |
| 3.0.17 | 43 / 0 | |
| 3.0.16 | 43 / 0 | |
| 3.0.15 | 43 / 0 | |
| 3.0.14 | 42 / 0 | |
| 3.0.13 | 42 / 0 | |
| 3.0.12 | 42 / 0 | |
| 3.0.11 | 42 / 0 | |
| 3.0.10 | 42 / 0 | |
| 3.0.9 | 42 / 0 | |
| 3.0.8 | 42 / 0 | |
| 3.0.7 | 42 / 0 | |
| 3.0.6 | 42 / 0 | |
| 3.0.5 | 42 / 0 | |
| 3.0.4 | 42 / 0 | |
| 3.0.3 | 42 / 0 | |
| 3.0.2 | 42 / 0 | |
| 3.0.1 | 44 / 0 | |
| 3.0.0 | 44 / 0 |
v3.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (peachscript) than the most recent previously approved version (sorrycc) on 2023-05-24, but peachscript 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.
v3.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.