The license, README, and repository test structure provide basic transparency, but there is no security policy and virtually no community activity. Treat this as legacy code and expect to maintain it yourself.
38%
Total Score
0
100
72
75
The package has nine releases, but its latest release was more than seven years ago and there were no releases in the last 12 months. That is strong evidence of abandonment risk.
There were no commits and no active maintainers in the last three months, consistent with the repository's last push being more than seven years ago. This materially raises maintenance and abandonment risk.
The repository name does not match the package name and its README does not mention the package. That makes the package-to-source relationship less transparent and warrants caution.
The repository has zero stars and forks and only one watcher. Popularity is not decisive, but this provides no supporting evidence of active use or community review.
The repository uses Composer build tooling, but it has no security scanning tools. That is a modest transparency and maintenance gap, especially for an inactive package.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/cache Version ~5.6.0 | — | — |
jenssegers/mongodb Version ^3.0 | — | — |
illuminate/database Version ~5.6.0 | — | — |
illuminate/contracts Version ~5.6.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.