A single maintainer and no security policy or automated security scanning leave limited resilience and transparency. Clear documentation, tests, release notes, and an active repository offset some of that risk.
58%
Total Score
50
83
50
One registry maintainer limits publishing resilience, although the linked repository is owned by the same individual, so this is a capacity concern rather than an ownership mismatch.
The package has had four releases since December 2024, but none in the last 12 months and its latest release was in June 2025, indicating a meaningful maintenance pause.
The repository recorded zero commits and zero active maintainers in the last three months, which weakens evidence of ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest repository-hygiene gap.
The repository has no security policy, reducing transparency about vulnerability reporting and response expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
setasign/fpdf Version ^1.8 | — | — |
illuminate/support Version ^8.0|^9.0|^10.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.