Healthy and suitable to use, with modest maintenance caveats. It has a long release history, a current stable release, clear documentation, tests in the repository, and no deprecation or risky workflow findings; recent activity is sparse and concentrated in one contributor, with limited security-process documentation.
78%
Total Score
63
100
88
67
The package and repository are owned by the same individual account, so the matching ownership supports authenticity but does not provide organizational maintenance redundancy.
The project has existed for about 12 years with 88 releases and a typical historical interval of about 24 days, but only one release was published in the last 12 months. The recent release still shows that the project is not abandoned, though its current cadence is slow.
All recent commits came from a single contributor, creating a meaningful continuity risk for this user-owned project with no organizational backing shown.
Only one commit was made in the last three months by one active maintainer, so current maintenance capacity appears limited despite the recent release and repository push.
The repository uses Composer build tooling, but no security scanning tools are configured. This is a process gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
illuminate/contracts Version ^11.0|^12.0|^13.0 | — | — |
illuminate/validation Version ^11.0|^12.0|^13.0 | — | — |
giggsey/libphonenumber-for-php-lite Version ^9.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.