The package includes tests, a README, and no install-time scripts, but its last release was over 12 years ago and the repository has had no commits or active maintainers in the last three months. The missing security scanning and security policy add transparency concerns.
35%
Total Score
38
100
69
75
Only two releases were published, with the latest over 12 years ago and none in the last 12 months. This is strong evidence of abandonment for a Laravel integration package.
There were no commits and no active maintainers in the last three months. Combined with the old last release, this indicates the project is not being maintained.
One registry account has publish access, leaving a thin publishing base. Because the repository is owned by the same individual, this also indicates limited visible continuity if that maintainer stops work.
The repository is owned by an individual rather than an organization, and no separate organizational backing is shown. This provides little redundancy against maintainer abandonment.
There is one open issue and no issue or pull-request activity in the last month. This is supporting evidence of inactivity, though the low issue volume alone is not severe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/dbal Version ~2.3 | — | — |
laravel/framework Version ~4.1 | — | — |
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.