The project is newly published, with three releases within hours and no observed three-month commit history yet. It has tests, a substantial README, an MIT license, organization backing, and no install scripts; the repository has no security policy or security scanning.
68%
Total Score
75
100
71
83
The package is 0 days old, with three releases in the first day and a median interval of about 3 hours 27 minutes. This shows active initial publishing but provides no established maintenance record.
There were 0 commits and 0 active maintainers in the last three months, but the repository and release were created only hours ago. This is insufficient history rather than evidence of abandonment, though it limits confidence.
The repository has 0 stars, forks, and watchers. For a package published on the same day, this is weak supporting evidence but not a health verdict by itself.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a modest transparency gap, not a severe risk on its own.
The repository has no security policy. That weakens the documented process for reporting and handling vulnerabilities, although it does not indicate an unsafe release by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^8.0 | — | — |
illuminate/queue Version ^8.0 | — | — |
illuminate/console Version ^8.0 | — | — |
illuminate/support Version ^8.0 | — | — |
illuminate/database Version ^8.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.