Clear documentation, tests, release notes, and a small dependency surface make integration straightforward. Workflow references are unpinned and the project lacks a security policy, leaving maintenance and build hygiene less reassuring.
62%
Total Score
50
100
94
83
The repository is owned by an individual user rather than an organization, so the project has limited visible institutional backing.
Only two releases exist, with the latest published in August 2021 and none in the last 12 months; this is a meaningful staleness concern for a dependency.
There were no commits and no active maintainers in the three months measured, which weakens evidence of ongoing maintenance; the later repository push partly offsets but does not remove this concern.
The repository has no security policy, leaving disclosure and handling expectations undocumented.
Both workflows were fully analyzed with no dangerous triggers, sinks, or audit findings, but all four action references are unpinned, creating avoidable build reproducibility and action-update risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
league/commonmark Version ^2.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.