@umijs/test
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@umijs/utils | AI (dependencies): Internal monorepo sibling dep; always published in lockstep with @umijs/test. | ai | |
| dependencies | unvetted-dep:@umijs/bundler-utils | AI (dependencies): Internal monorepo sibling dep; always published in lockstep with @umijs/test. | ai | |
| provenance | no-provenance | AI (provenance): Long-established UmiJS monorepo package; provenance absence is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-modules-commonjs | AI (phantom-deps): Babel plugin loaded by convention via babel-jest config; not directly imported but legitimately used. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Legitimate @umijs scoped test utility in the UmiJS monorepo; not a typosquat of jest. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established monorepo package; sparse metadata is a style choice, not a spam indicator. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Legitimate @umijs scoped package; no relation to next.js. | ai | |
| typosquat | typosquat.levenshtein:vitest | AI (typosquat): Legitimate @umijs scoped package; no relation to vitest. | ai |
Versions (showing 40 of 140)
| Version | Deps | Published |
|---|---|---|
| 4.3.23 | 8 / 3 | |
| 4.3.22 | 8 / 3 | |
| 4.3.21 | 8 / 3 | |
| 4.3.20 | 8 / 3 | |
| 4.3.19 | 8 / 3 | |
| 4.3.18 | 8 / 3 | |
| 4.3.17 | 8 / 3 | |
| 4.3.16 | 8 / 3 | |
| 4.3.15 | 8 / 3 | |
| 4.3.14 | 8 / 3 | |
| 4.3.13 | 8 / 3 | |
| 4.3.12 | 8 / 3 | |
| 4.3.11 | 8 / 3 | |
| 4.3.10 | 8 / 3 | |
| 4.3.9 | 8 / 3 | |
| 4.3.8 | 8 / 3 | |
| 4.3.7 | 8 / 3 | |
| 4.3.6 | 8 / 3 | |
| 4.3.5 | 8 / 3 | |
| 4.3.4 | 8 / 3 | |
| 4.3.3 | 8 / 3 | |
| 4.3.2 | 8 / 3 | |
| 4.3.1 | 8 / 3 | |
| 4.3.0 | 8 / 3 | |
| 4.2.15 | 8 / 3 | |
| 4.2.14 | 8 / 3 | |
| 4.2.13 | 8 / 3 | |
| 4.2.12 | 8 / 3 | |
| 4.2.11 | 8 / 3 | |
| 4.2.10 | 8 / 3 | |
| 4.2.9 | 8 / 3 | |
| 4.2.8 | 8 / 3 | |
| 4.2.7 | 8 / 3 | |
| 4.2.6 | 8 / 3 | |
| 4.2.5 | 8 / 3 | |
| 4.2.4 | 8 / 3 | |
| 4.2.3 | 8 / 3 | |
| 4.2.2 | 8 / 3 | |
| 4.2.1 | 8 / 3 | |
| 4.2.0 | 8 / 3 |
v4.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.