showdown
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
tiviesyntaxrules
Keywords
markdownconverter
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Showdown is a well-established package; lack of Sigstore provenance is common and not a meaningful risk signal here. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): The dynamic-require findings in bin/showdown.js are false positives — the requires are for static, known modules (fs, path, commander) in a minified CLI entry point. No user-controlled dynamic loading. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 1 / 20 |
v2.1.0
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.