A clear README, tests, changelog, and MIT license make the package straightforward to evaluate and integrate. Security scanning is absent, and the repository has had no commits in three months, so long-term maintenance remains uncertain.
64%
Total Score
50
100
83
83
The repository is owned by an individual account rather than an organization, and the registry has one maintainer, leaving limited visible continuity if that maintainer becomes unavailable.
The package is only 168 days old and all six releases arrived in a burst with a median interval of about 15 minutes, so sustained maintenance is not yet established.
There were no commits and no active maintainers in the last three months. For a package only 168 days old, that is a meaningful sign that maintenance may have stopped after the initial release burst.
The repository has two stars, no forks, and no watchers. This is limited adoption evidence, but popularity is supporting context rather than a health verdict.
Composer build tooling is present, but no security scanning tools are configured, leaving a repository hygiene gap for a package that handles captured API data.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^9.0|^10.0|^11.0 | — | — |
illuminate/console Version ^9.0|^10.0|^11.0 | — | — |
illuminate/support Version ^9.0|^10.0|^11.0 | — | — |
illuminate/database Version ^9.0|^10.0|^11.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.