Clear licensing, tests, and release documentation improve transparency, while the single-maintainer project has no security policy. Its small user base and absent recent commit activity also leave maintenance capacity uncertain.
62%
Total Score
50
88
83
Only one registry account has publish access. A single maintainer can be sufficient for a small project, but it creates limited publishing redundancy and a higher bus-factor concern.
The repository recorded zero commits and zero active maintainers in the last three months. For a young package, this is a meaningful sign that maintenance may have slowed or stopped.
The repository has one star, one fork, and no watchers. Popularity is not required for health, but these very low numbers provide little supporting evidence of broad review or adoption.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning coverage is a modest maintenance and assurance gap.
The repository has no SECURITY.md or other detected security policy. This reduces transparency about vulnerability reporting and handling, though it is not evidence of a vulnerability.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^12.0 | — | — |
laravel/sanctum Version ^4.0 | — | — |
illuminate/console Version ^12.0 | — | — |
illuminate/routing Version ^12.0 | — | — |
illuminate/support Version ^12.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.