The package has had no release for nearly eight years, and the repository has had no recent commit activity. A clear MIT license, tests, matching source repository, and no install scripts reduce adoption risk, but the missing security policy and very small project footprint leave maintenance concerns.
55%
Total Score
25
100
78
83
The latest release was published in October 2018, with no releases in the previous 12 months; this is a substantial maintenance concern for a dependency assessed now.
There were no commits and no active maintainers in the last three months; combined with the old release history, this strongly raises abandonment risk.
The repository is owned by an individual rather than an organization, so there is no provided evidence of organizational maintenance capacity to offset the stale activity.
The repository has one star, no forks, and one watcher, indicating very limited external adoption and little independent evidence of ongoing use.
Composer is used for the build, but no security-scanning tooling is present; for an older, inactive project this leaves fewer safeguards against dependency or build problems.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/container Version 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.