@umijs/plugin-docs
@umijs/plugin-docs
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 | no-provenance | AI (provenance): Established package; provenance absence is a general ecosystem signal, not a package-specific risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal UmiJS monorepo package; sparse metadata is expected and consistent across all versions. | ai | |
| dependencies | unvetted-dep:keymaster | AI (dependencies): keymaster is a well-known keyboard shortcut library; stable dependency for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Sample shows isBuffer constructor check, not dynamic code execution; stable false positive for this compiled bundle. | ai | |
| phantom-deps | phantom-dep:shiki | AI (phantom-deps): shiki is a declared runtime dep used via config/compiled output; phantom-dep heuristic misfires here. | ai |
Versions (showing 11 of 211)
| Version | Deps | Published |
|---|---|---|
| 4.0.10 | 5 / 10 | |
| 4.0.9 | 5 / 10 | |
| 4.0.8 | 5 / 10 | |
| 4.0.7 | 4 / 9 | |
| 4.0.6 | 4 / 9 | |
| 4.0.5 | 4 / 8 | |
| 4.0.4 | 4 / 8 | |
| 4.0.3 | 4 / 8 | |
| 4.0.2 | 4 / 8 | |
| 4.0.1 | 4 / 8 | |
| 4.0.0 | 4 / 8 |
v4.0.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.0.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.0.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.0.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.0.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.0.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.0.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.0.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.0.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.0.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.0.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.