The package is small, clearly licensed, and has a matching organization-owned repository. Its dependency surface is narrow, but the repository shows no commits in three months and the workflow uses an unpinned action with broad write permissions.
62%
Total Score
75
100
86
50
The package has 289 releases over nearly five years, but only one release in the last 12 months; this indicates a sharp slowdown despite a substantial historical record.
The repository had zero commits and zero active maintainers in the last three months, which is a concrete maintenance concern for a package intended to be depended on.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy. For a small logging component this is a limited governance gap, but it reduces clarity about vulnerability reporting.
The only workflow has a pull_request_target trigger without an untrusted checkout or script-injection sink, so the trigger is not dangerous on its own. However, its action is unpinned and the workflow grants top-level write permissions, creating moderate supply-chain hygiene concerns.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/log Version ^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.