The small user base and absent security scanning reduce confidence in long-term support. Clear licensing, tests, documentation, and a matching repository provide useful transparency, but the project has not been updated for about seven years.
43%
Total Score
50
69
88
The latest release was on August 26, 2019, and there were no releases in the last 12 months. About seven years without a release is strong evidence of abandonment risk.
There were 0 commits and 0 active maintainers in the last three months, consistent with the release history and indicating no current maintenance capacity.
The repository has only 2 stars, 0 forks, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these numbers provide little evidence of sustained adoption.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning lowers repository hygiene and visibility into dependency risks.
The repository has no security policy. This is a transparency gap for reporting and handling vulnerabilities, especially in a package with no recent maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ramsey/uuid Version ^3.8.0 | — | — |
setasign/fpdi-fpdf Version ^2.0 | — | — |
setasign/fpdi-tcpdf 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.