@umijs/lint
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): ESLint plugin loaded by config convention, not directly imported. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): Lint config package; postcss loaded by convention via stylelint, not directly imported. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Framework-scoped; loaded by babel-eslint-parser convention, not directly imported. | ai | |
| phantom-deps | phantom-dep:postcss-syntax | AI (phantom-deps): Referenced in config files by convention, not directly imported. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-jest | AI (phantom-deps): ESLint plugin loaded by config convention, not directly imported. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react | AI (phantom-deps): ESLint plugin loaded by config convention, not directly imported. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react-hooks | AI (phantom-deps): ESLint plugin loaded by config convention, not directly imported. | ai | |
| typosquat | typosquat.levenshtein:eslint | AI (typosquat): Scoped @umijs/ package; not a typosquat of eslint. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped @umijs/ package; not a typosquat of pino. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires in compiled/@rushstack/eslint-patch bundle; legitimate eslint config resolution pattern. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Fires in compiled/postcss-less minified bundle; no malicious payload. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires in compiled/postcss-less minified bundle; standard parser pattern. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Fires in compiled stylelint plugin bundle; config library pattern. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Fires in compiled stylelint plugin bundle; not obfuscation. | ai |
Versions (showing 51 of 57)
| Version | Deps | Published |
|---|---|---|
| 4.6.57 | 12 / 5 | |
| 4.6.56 | 12 / 5 | |
| 4.6.55 | 12 / 5 | |
| 4.6.54 | 12 / 5 | |
| 4.6.53 | 12 / 5 | |
| 4.6.52 | 12 / 5 | |
| 4.6.51 | 12 / 5 | |
| 4.6.50 | 12 / 5 | |
| 4.6.49 | 12 / 5 | |
| 4.6.48 | 12 / 5 | |
| 4.6.45 | 12 / 5 | |
| 4.6.42 | 12 / 5 | |
| 4.6.41 | 12 / 5 | |
| 4.6.39 | 12 / 5 | |
| 4.6.36 | 12 / 5 | |
| 4.6.35 | 12 / 5 | |
| 4.6.34 | 12 / 5 | |
| 4.6.33 | 12 / 5 | |
| 4.6.32 | 12 / 5 | |
| 4.6.31 | 12 / 5 | |
| 4.6.30 | 12 / 5 | |
| 4.6.29 | 12 / 5 | |
| 4.6.28 | 12 / 5 | |
| 4.6.27 | 12 / 5 | |
| 4.6.26 | 12 / 5 | |
| 4.6.25 | 12 / 5 | |
| 4.6.24 | 12 / 5 | |
| 4.6.23 | 12 / 5 | |
| 4.6.22 | 12 / 5 | |
| 4.6.21 | 12 / 5 | |
| 4.6.20 | 12 / 5 | |
| 4.6.19 | 12 / 5 | |
| 4.6.18 | 12 / 5 | |
| 4.6.17 | 12 / 5 | |
| 4.6.16 | 12 / 5 | |
| 4.6.15 | 12 / 5 | |
| 4.6.14 | 12 / 5 | |
| 4.6.13 | 12 / 5 | |
| 4.6.12 | 12 / 5 | |
| 4.6.11 | 12 / 5 | |
| 4.6.10 | 12 / 5 | |
| 4.6.9 | 12 / 5 | |
| 4.6.8 | 12 / 5 | |
| 4.6.7 | 12 / 5 | |
| 4.6.6 | 12 / 5 | |
| 4.6.5 | 12 / 5 | |
| 4.6.4 | 12 / 5 | |
| 4.6.3 | 12 / 5 | |
| 4.6.2 | 12 / 5 | |
| 4.6.1 | 12 / 5 | |
| 4.6.0 | 12 / 5 |
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.