Clear documentation, tests, and a stable release support adoption. The missing security policy and complete reliance on one contributor leave maintenance and response capacity thin.
58%
Total Score
50
100
88
75
The repository is owned by an individual rather than an organization, so the single-contributor concentration is not offset by visible organizational backing.
One contributor made all eight recent commits, creating a concentrated maintenance dependency and increasing the risk that fixes or releases stop if that person becomes unavailable.
Eight commits were made in the last three months, indicating recent activity, but all activity came from only one active maintainer.
The repository has one star, no forks, and no watchers. Low adoption is supporting evidence of limited maturity, though it is not decisive for a small package.
Composer build tooling is present, but no security scanning tools were detected. That leaves a meaningful supply-chain hygiene gap for a package handling application logs and notifications.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/log Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0|^13.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.