The package has a small dependency surface and clear documentation for users. Workflow pinning and the absence of a security policy or scanning leave some maintenance and build-hygiene gaps.
78%
Total Score
88
100
94
75
There are two open issues and two open pull requests, with no new or closed items in the last month. This suggests limited current discussion, but it is not enough to outweigh the recent release and commits.
Composer build tooling is present, but no security scanning tools were detected. That is a process gap for supply-chain transparency, though it is not evidence of unsafe code.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a library used in WordPress projects.
All three workflow action references are unpinned, which weakens build reproducibility. The two cache-poisoning findings are low-confidence hygiene warnings, and the audit found no untrusted checkout, injection sink, or broad write token.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
erusev/parsedown Version ^1.7 | — | — |
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.