The package is licensed, documented, and has a matching source repository. Unpinned workflow actions and no security policy add maintenance hygiene concerns.
68%
Total Score
50
100
88
75
The registry namespace and repository are owned by the same individual account, so the package has direct ownership alignment but no organizational backing shown by this signal.
The package has nine releases over about six years, with one release in the last 12 months and a median interval of about nine months. This indicates a small, infrequent but not abandoned release pattern.
There were zero commits and zero active maintainers in the last three months. The recent release provides some compensating evidence, but the current lack of activity raises abandonment concern.
The repository uses Composer for builds but reports no security-scanning tools. For a small package this is a hygiene gap, not evidence of unsafe code by itself.
The repository has no security policy. This weakens vulnerability-reporting transparency, although the package's small scope and other documentation partly reduce the concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version ^5.4 || ^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || ^13 | — | — |
illuminate/container Version ^5.4 || ^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || ^13 | — | — |
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.