The repository is tiny, has one registry maintainer, and provides no security scanning or security policy. Its MIT license and direct package/repository match improve transparency, but do not offset the long inactivity.
42%
Total Score
25
75
75
The package has had no release in nearly five years: its latest release was October 25, 2021, with zero releases in the last 12 months. This is strong evidence of abandonment for a dependency that may need compatibility or security fixes.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's stalled release history and indicating no recent maintenance capacity.
Only one registry account has publish access. That is not inherently unhealthy, but combined with the absence of recent release and commit activity it leaves little visible continuity if that maintainer stops work.
Composer build tooling is present, but no security scanning tools are configured. This is a maintenance and transparency gap, though it is less serious than the lack of recent development.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This reduces transparency for a package that handles application request logging.
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.