Clear documentation, tests, licensing, and a focused dependency set make the release straightforward to evaluate. The project has little adoption and no recent commit activity, while security tooling is absent. Its early release history leaves maintenance capacity unproven.
62%
Total Score
25
100
81
88
There were zero commits and zero active maintainers in the last three months. For a package only about 134 days old, that is a meaningful warning that maintenance may have stopped soon after launch.
The repository is owned by an individual user account matching the registry namespace. This identifies ownership but provides no organization-level maintenance capacity.
The package is about 134 days old and has only two releases, both published within about one hour. This is limited evidence of an established maintenance cadence.
The repository has four stars, one fork, and no watchers, showing a very small user and contributor audience. Popularity is supporting evidence rather than a verdict, but it offers little external maintenance signal here.
Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap for a deployment-related package, though it is not severe on its own.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version ^11.0 || ^12.0 || ^13.0 | — | — |
illuminate/support Version ^11.0 || ^12.0 || ^13.0 | — | — |
illuminate/filesystem 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.