turndown
A library that converts HTML to Markdown
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@mixmark-io/domino | AI (dependencies): @mixmark-io/domino is the expected server-side DOM dependency for turndown; it is explicitly excluded in browser builds and is part of the same mixmark-io organization. | ai | |
| provenance | no-provenance | AI (provenance): Lack of provenance attestation is common (~88% of npm packages) and not a security concern for this well-known library. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 7.2.4 | 1 / 11 | |
| 7.2.3 | 1 / 11 | |
| 7.2.2 | 1 / 8 | |
| 7.2.1 | 1 / 8 | |
| 7.2.0 | 1 / 8 |
v7.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.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.