The repository has had no commits for nearly three years, and the project has no security policy or automated security scanning. Its organization backing, matching repository, MIT declaration, and small documented artifact provide some transparency, but do not offset the package-wide withdrawal.
20%
Total Score
50
64
50
Packagist marks the entire package as abandoned, with no replacement specified. Package-wide deprecation is a severe dependency risk even though the repository is not archived.
The latest release was published nearly three years ago, with no releases in the last 12 months and only five releases overall. This indicates a likely abandoned release line.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided activity signal compensates for this inactivity.
Composer build tooling is present, which supports reproducible package structure, but no security scanning tools are configured. The tooling is therefore only partial reassurance.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency and maintenance gap for a package used in applications.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mpdf/mpdf Version ^7.0|^8.0 | — | — |
laravel/framework Version * | — | — |
phpoffice/phpspreadsheet Version ^1.2.0 | — | — |
propaganistas/laravel-phone Version ^4.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.