The package is clearly identified, MIT-licensed, documented, and backed by an organization with a matching source repository. No security policy or security scanning is present, so transparency and maintenance confidence remain limited.
66%
Total Score
100
100
83
67
This is a young package with one release, published 95 days ago, so there is little release history to demonstrate sustained maintenance.
The repository has zero stars, forks, and watchers. For a package only 95 days old this is limited supporting evidence rather than a decisive health concern.
Composer is used for the build, but no security-scanning tools are configured. That leaves an avoidable gap in automated security hygiene.
The repository has no security policy, leaving no stated process for reporting or handling vulnerabilities.
The single workflow was fully analyzed with no unsafe-trigger or high-confidence audit findings, but both of its two action references are unpinned. This weakens build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^10.0|^11.0|^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.