micromark extension to support GFM (GitHub Flavored Markdown)
68%
Total Score
75
89
67
A prepack lifecycle script adds build-time complexity and a publishing step to inspect, but it is not by itself evidence of unsafe runtime installation behavior.
The package has 12 releases over about six years, but none in the last three years, which raises maintenance and abandonment concerns for a library dependency.
The repository recorded no commits and no active maintainers in the last three months, reinforcing the concern raised by the long gap since the latest registry release.
The project uses TypeScript and npm build tooling, but no security scanning tools were detected; this is a modest transparency and hygiene gap rather than a severe risk.
Both workflows were analyzed without reported audit findings, and the pull_request_target workflow has no untrusted checkout or script-injection sink. However, all four action references are unpinned, weakening build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
micromark-util-types Version ^2.0.0 | — | — |
micromark-extension-gfm-table Version ^2.0.0 | — | — |
micromark-extension-gfm-footnote Version ^2.0.0 | — | — |
micromark-extension-gfm-tagfilter Version ^2.0.0 | — | — |
micromark-util-combine-extensions Version ^2.0.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.