The README is brief, and the project has no tests or security policy, limiting confidence in integration and ongoing care. Its small dependency set and MIT license reduce adoption friction, but they do not offset the maintenance gap.
38%
Total Score
33
100
75
83
The package has only one release, published on May 24, 2017, with no releases in the last 12 months. This is strong evidence that development and maintenance have stopped.
The repository had zero commits and zero active maintainers in the last three months, consistent with the last push being nearly nine years ago. This materially raises abandonment risk.
Only one registry account has publish access, and the project is not shown as organization-backed. A single maintainer increases continuity risk if that person stops maintaining the package.
The repository owner is an individual user rather than an organization. That provides less visible institutional backing and modestly increases continuity risk.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap for a package with no other recent activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/view Version >=5.3 | — | — |
illuminate/support Version >=5.3 | — | — |
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.