← Home

writr

npm Repository Homepage

Markdown Rendering Simplified

3
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jaredwray

Keywords

markdownhtmlrenderermarkdown-to-htmltoctable-of-contentsemojisyntax-highlightingmarkdown-processorgithub-flavored-markdowngfmremark-pluginrehype-pluginmarkdown-editorcontent-managementdocumentation-toolbloggingmarkdown-extensionseo-friendlymarkdown-anchorsremarkrehypereactreact-componentreact-markdownmarkdown-to-react

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:remark-toc AI (dependencies): remark-toc is a well-known remark ecosystem plugin; stable false positive for this markdown renderer. ai
dependencies unvetted-dep:remark-github-blockquote-alert AI (dependencies): Legitimate remark plugin for GH-style blockquote alerts; appropriate dependency for this package. ai

Versions (showing 3 of 3)

Version Deps Published
6.1.2 22 / 20
5.0.2 19 / 13
5.0.1 19 / 10

v6.1.2

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.

v5.0.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v5.0.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.