The package is new, with one release and one commit from one active contributor, so long-term maintenance is not yet proven. MIT licensing, repository-backed tests, release notes, and organization ownership provide useful support, but no security policy or scanning is documented.
68%
Total Score
75
100
83
75
The package is only 51 days old and has one release, so there is not enough release history to demonstrate sustained maintenance.
All recent commits come from one contributor, creating concentration risk. Organization ownership provides some handoff capacity, but no second active contributor is shown.
Only one commit was recorded in the last 3 months from one active maintainer; for a package this new, that shows activity but not sustained maintenance capacity.
The repository has no stars, forks, or watchers. For a 51-day-old package this is limited supporting evidence rather than a decisive health problem.
Composer build tooling is present, but no security-scanning tooling is reported, leaving a modest transparency and defensive-process gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/bus Version ^11.0|^12.0|^13.0 | — | — |
illuminate/auth Version ^11.0|^12.0|^13.0 | — | — |
illuminate/http Version ^11.0|^12.0|^13.0 | — | — |
illuminate/mail Version ^11.0|^12.0|^13.0 | — | — |
illuminate/view Version ^11.0|^12.0|^13.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.