The package is small and well documented, with tests, release notes, and a matching source repository. Its recent maintenance and workflow pinning leave some avoidable dependence risk.
72%
Total Score
50
100
93
67
The package and repository are owned by the same individual account. That is coherent ownership, though it does not provide the redundancy of organization backing.
The package has existed since 2017 and has seven releases, but it had no releases in the last 12 months and its median release interval is about 389 days. This supports a stable, slow-moving project but lowers confidence in active maintenance.
There were zero commits and zero active maintainers in the last three months. The recent repository push is compensating evidence, but the current inactivity still creates a modest abandonment concern.
The repository has no security policy. For a small formatter this is a transparency gap rather than a severe dependency risk, but it provides no documented vulnerability-reporting path.
The single workflow was fully analyzed with no untrusted checkouts, script injection, or audit findings, and it has no top-level write permissions. However, all four action references are unpinned, leaving avoidable build-integrity risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version ^2.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.