This is a generally healthy and actively maintained release: the package has existed for over 6 years, has 53 releases including 8 in the last 12 months, is not deprecated, uses a stable version, has a small runtime dependency set, and is backed by a non-archived organization-owned repository with matching package references. The main concerns are that recent repository commits are concentrated in one contributor, the repository has no tests or security policy, and the package artifact lacks a README; however, the repository contains documentation and a changelog, uses GitHub Releases, has recent pull-request activity, and the package is clearly licensed. It appears reasonable to depend on, with normal monitoring of maintenance continuity and security practices.
82%
Total Score
80
100
94
90
All two recent commits came from one contributor, creating a concentrated short-term commit base. Organization ownership partially mitigates handoff risk, but the observed contributor concentration remains a caution.
Only two commits were recorded in the last 3 months and they came from one active maintainer, suggesting limited recent direct commit activity; recent pull-request activity provides some compensation but does not eliminate the maintenance concern.
Composer build tooling is present, supporting reproducible package management, but no security scanning tools were detected, leaving a security-hygiene gap.
The repository has no security policy, which weakens vulnerability-reporting transparency and is a genuine hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.0|^11.0|^12|^13 | — | — |
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.