Production-ready structured logging for Laravel microservices with OpenTelemetry support
38%
Total Score
unhealthy
Risky: high-confidence workflow injection exposure and no repository commits in the last three months outweigh strong package documentation.
Both high-confidence template-injection findings are in workflows, including a workflow_run workflow, which makes the automation a supply-chain concern rather than mere cosmetic hygiene. All 16 action references are unpinned, and two workflows grant top-level write access, adding further workflow risk.
The repository recorded zero commits and zero active maintainers in the last three months. For a package whose latest release was months earlier, this is meaningful evidence of slowing maintenance.
The repository has no stars, forks, or watchers. Popularity is only supporting evidence, so this lowers maturity confidence modestly but is not decisive for a young package.
No repository security policy was found. This is a modest transparency gap for a package handling logging and sensitive-header redaction, but it is not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^9.0|^10.0|^11.0|^12.0|^13.0 | — | — |
monolog/monolog Version ^3.5 | — | — |
illuminate/support Version ^9.0|^10.0|^11.0|^12.0|^13.0 | — | — |
open-telemetry/api Version ^1.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.