@umijs/plugin-docs
@umijs/plugin-docs
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 |
|---|---|---|---|---|
| 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 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 4.6.61 | 6 / 9 | |
| 4.6.59 | 6 / 9 | |
| 4.6.58 | 6 / 9 | |
| 4.6.57 | 6 / 9 | |
| 4.6.56 | 6 / 9 | |
| 4.6.55 | 6 / 9 | |
| 4.6.54 | 6 / 9 | |
| 4.6.53 | 6 / 9 | |
| 4.6.52 | 6 / 9 | |
| 4.6.51 | 6 / 9 | |
| 4.6.50 | 6 / 9 | |
| 4.6.49 | 6 / 9 | |
| 4.6.48 | 6 / 9 | |
| 4.6.47 | 6 / 9 | |
| 4.6.46 | 6 / 9 | |
| 4.6.45 | 6 / 9 | |
| 4.6.44 | 6 / 9 | |
| 4.6.43 | 6 / 9 | |
| 4.6.42 | 6 / 9 | |
| 4.6.41 | 6 / 9 | |
| 4.6.40 | 6 / 9 | |
| 4.6.39 | 6 / 9 | |
| 4.6.38 | 6 / 9 | |
| 4.6.37 | 6 / 9 | |
| 4.5.3 | 6 / 9 | |
| 4.5.2 | 6 / 9 | |
| 4.5.1 | 6 / 9 | |
| 4.5.0 | 6 / 9 | |
| 4.4.12 | 6 / 9 | |
| 4.4.11 | 6 / 9 |
v4.6.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.56
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.50
1 finding[Accepted risk] Package 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.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.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.5.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.5.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.5.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.4.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.4.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.