The linked repository includes tests and the package is MIT-licensed, but it does not identify this package in its README or repository name. Its tiny, user-owned project footprint adds little confidence for long-term maintenance.
38%
Total Score
25
79
75
There were no commits and no active maintainers in the last three months, consistent with a repository that has been inactive since 2016. This materially increases maintenance and abandonment risk.
The registry namespace and repository owner are the same user account, with no organization backing shown. This is not inherently unsafe, but it indicates a thin project backing context.
The latest release was published in April 2016, with no releases in the last 12 months and a package age of about 10 years. This is a substantial abandonment concern.
The repository name does not match the package name and its README does not mention the package. That weakens confidence that the linked source repository is actually the package's authoritative project.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but this provides little external evidence of ongoing adoption or review.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version 5.2.* | — | — |
illuminate/view Version 5.2.* | — | — |
illuminate/routing Version 5.2.* | — | — |
illuminate/session Version 5.2.* | — | — |
illuminate/support Version 5.2.* | — | — |
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.