MIT licensing, a matching repository, and clear usage documentation reduce adoption friction. However, the project has seen no commits or releases for nearly three years, so fixes and compatibility updates are unlikely.
45%
Total Score
75
83
50
The latest release was about three years ago, with no releases in the last 12 months. This is a substantial maintenance concern for a package developers may need to keep compatible with its ecosystem.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating little current maintenance capacity.
The repository has no security policy, which makes vulnerability reporting less transparent. This is a documentation gap rather than evidence of unsafe behavior.
Version v0.1.5 is not yet at a stable major version, adding compatibility uncertainty; the absence of prerelease labeling is a small compensating signal but does not offset the age of the release.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but all 6 of 6 action references are unpinned, leaving avoidable build-supply-chain hygiene risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mpdf/mpdf Version ^8.1 | — | — |
symfony/console Version ^4.2|^5.0|^6.0 | — | — |
illuminate/support Version ^7.0|^8.0|^9.0|^10.0 | — | — |
illuminate/filesystem Version ^7.0|^8.0|^9.0|^10.0 | — | — |
spatie/commonmark-highlighter Version ^2.1|^3.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.