docsify-cli
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
trusktrqingwei.lijhildenbiddleanixsahajamesgeorge007sy-recordskoooooo-7
Keywords
docsifydocdocsdocumentationcreatorgeneratorcli
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Config-file loader pattern; user supplies path via CLI arg, not attacker-controlled remote input. | ai | |
| phantom-deps | phantom-dep:docsify | AI (phantom-deps): docsify is a runtime dep served to users, not directly imported in JS — stable false positive for this CLI tool. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 4.4.4 | 17 / 12 |
v4.4.4
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.