Workflow actions are all unpinned, and the repository has no security policy or scanning. The README, repository tests, changelog, and MIT license provide useful baseline transparency.
56%
Total Score
50
80
50
Only six releases were published, with the latest over two years ago and none in the last 12 months. The short initial release run followed by prolonged inactivity lowers confidence in ongoing maintenance.
The repository had zero commits and zero active maintainers in the last three months, consistent with more than two years since the last push. This is the strongest evidence of current maintenance risk.
No security policy is present in the repository. This is a transparency and vulnerability-reporting gap, though it does not by itself show that the package is unsafe.
Version 0.2.4 is not a stable major release, and the README explicitly describes the package as early development with possible breaking changes. This makes upgrades less predictable.
All six analyzed action references are unpinned, reducing build reproducibility and increasing exposure to upstream action changes. There were no untrusted checkouts, script injections, or high-severity audit findings, which limits the impact to a hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.8 | — | — |
symfony/dom-crawler Version ^7.0 | — | — |
illuminate/contracts Version ^11.0 | — | — |
league/html-to-markdown Version ^5.1 | — | — |
spatie/laravel-package-tools Version ^1.14.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.