The README, release notes, and organization-owned repository provide useful transparency for a small package. However, no recent maintenance and no repository security tooling make long-term support uncertain.
55%
Total Score
50
81
75
The repository recorded no commits and no active maintainers in the last three months, with the last push in March 2024. This indicates sustained inactivity and raises abandonment risk.
The package has only two releases, both published in March 2024, with no releases in the last 12 months. This is a meaningful maintenance concern despite the short initial release interval.
Composer build tooling is present, but no security scanning tools were detected. For a small logging package this is a modest transparency and maintenance gap, not evidence of unsafe behavior.
The repository has no security policy. This weakens vulnerability-reporting transparency, although the package's README, release notes, and organization backing provide some compensating evidence.
Version 0.2.0 is not a stable major release, so compatibility expectations are limited. It is not marked as a prerelease, which partly offsets the concern.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.