@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 51 of 211)
| Version | Deps | Published |
|---|---|---|
| 4.6.81 | 6 / 9 | |
| 4.6.80 | 6 / 9 | |
| 4.6.79 | 6 / 9 | |
| 4.6.78 | 6 / 9 | |
| 4.6.77 | 6 / 9 | |
| 4.6.76 | 6 / 9 | |
| 4.6.75 | 6 / 9 | |
| 4.6.69 | 6 / 9 | |
| 4.6.68 | 6 / 9 | |
| 4.6.67 | 6 / 9 | |
| 4.6.66 | 6 / 9 | |
| 4.6.65 | 6 / 9 | |
| 4.6.64 | 6 / 9 | |
| 4.6.63 | 6 / 9 | |
| 4.6.62 | 6 / 9 | |
| 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 | |
| 4.4.10 | 6 / 9 | |
| 4.4.9 | 6 / 9 | |
| 4.4.8 | 6 / 9 | |
| 4.4.7 | 6 / 9 | |
| 4.4.6 | 6 / 9 | |
| 4.4.5 | 6 / 9 |
v4.6.81
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.80
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.79
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.78
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.77
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.76
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.75
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (zoomdong07) on 2026-07-10, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v4.6.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.10
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sorrycc) than the most recent previously approved version (xusd320) on 2025-04-25, but sorrycc 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.
v4.4.9
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (xusd320) than the most recent previously approved version (sorrycc) on 2025-04-22, but xusd320 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.
v4.4.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (xusd320) than the most recent previously approved version (sorrycc) on 2025-04-21, but xusd320 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.
v4.4.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sorrycc) than the most recent previously approved version (xusd320) on 2025-04-18, but sorrycc 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.
v4.4.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sorrycc) than the most recent previously approved version (xusd320) on 2025-02-28, but sorrycc 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.
v4.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.