dumi
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/hast | AI (phantom-deps): Type-only package loaded by framework convention. | ai | |
| phantom-deps | phantom-dep:@types/mdast | AI (phantom-deps): Type-only package loaded by framework convention. | ai | |
| phantom-deps | phantom-dep:heti | AI (phantom-deps): heti is a declared runtime dep used as optional peer/plugin, referenced in config files by convention. | ai | |
| phantom-deps | phantom-dep:sass | AI (phantom-deps): sass is a declared dep used as optional CSS preprocessor, loaded by convention in umi/dumi builds. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval in compiled/loader-runner is the standard webpack loader-runner ESM dynamic import pattern, not malicious. | ai | |
| phantom-deps | phantom-dep:rc-motion | AI (phantom-deps): rc-motion is a UI dep loaded by convention in the theme layer. | ai | |
| phantom-deps | phantom-dep:react-simple-code-editor | AI (phantom-deps): Loaded by convention in dumi's live editor feature. | ai | |
| phantom-deps | phantom-dep:prismjs | AI (phantom-deps): prismjs loaded by convention in dumi's syntax highlighting pipeline. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in loader-runner is standard webpack loader loading pattern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.4.27 | 68 / 34 | |
| 2.4.26 | 68 / 34 | |
| 2.4.23 | 68 / 34 | |
| 2.4.22 | 68 / 34 | |
| 2.4.21 | 68 / 34 |
v2.4.27
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.