Tests, a clear README, and release notes improve confidence. The organization-backed repository is current, but maintenance remains concentrated and security practices are undocumented.
68%
Total Score
67
88
50
The package has only two releases across about 15 months, with an interval of about 380 days. The latest release was published about two months ago, so this suggests a small and infrequent maintenance history rather than abandonment.
One contributor made all two commits in the last three months, concentrating recent maintenance in a single person. Organization ownership provides some handoff capacity, but no second active contributor is shown.
The repository had two commits in the last three months, indicating some recent maintenance, but activity is limited. Combined with the sparse release history, this warrants caution rather than a severe abandonment assessment.
The project uses Composer for builds, but no security scanning tool was detected. The missing scanner is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no security policy. For a package that processes application-generated PDFs, this leaves vulnerability-reporting expectations undocumented.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
mpdf/mpdf Version ^8.3 | — | — |
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.