Commit activity has stopped for about five months, and the project has one registry maintainer with no security scanning or policy. The repository has tests, a clear README, regular early releases, and no deprecation or archive status.
58%
Total Score
50
100
88
50
Only one registry account has publish access, creating a thin publishing base; the repository is user-owned rather than organization-backed, so there is no shown capacity buffer.
The repository is owned by an individual account, matching the package namespace, with no organizational backing shown to compensate for the single-maintainer structure.
There were no commits and no active maintainers in the last three months, indicating maintenance has stalled beyond the latest release.
The repository has zero stars, forks, and watchers, providing no community validation or backup maintenance capacity. This is supporting evidence rather than a verdict on its own.
Composer build tooling is present, but no security scanning tool is configured, leaving automated security coverage unshown.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^12.0 | — | — |
illuminate/database Version ^12.0 | — | — |
carone/laravel-common Version ^1.0 | — | — |
intervention/image-laravel Version ^1.5 | — | — |
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.