remark-gfm
remark plugin to support GFM (autolink literals, footnotes, strikethrough, tables, tasklists)
2
Versions
MIT
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
johnowooormremcohaszing
Keywords
autolinkfootnotegfmgithubmarkdownmdastpluginremarkremark-pluginstrikethroughtabletasklistunified
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:remark-parse | AI (phantom-deps): remark-parse is a peer/ecosystem dependency referenced in config/docs but not directly imported; this is expected for a remark plugin and stable across versions. | ai | |
| phantom-deps | phantom-dep:remark-stringify | AI (phantom-deps): remark-stringify is a peer/ecosystem dependency referenced in config/docs but not directly imported; this is expected for a remark plugin and stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): wooorm/remark ecosystem packages consistently lack Sigstore provenance; publisher is well-established and trusted. Not a meaningful risk signal for this package. | ai | |
| phantom-deps | phantom-dep:@types/mdast | AI (phantom-deps): @types/mdast is intentionally declared as a runtime dep in the unified ecosystem to expose TypeScript types to consumers; not a real phantom dependency issue. | ai |
v4.0.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.