The repository is not archived, has a security policy, and the release includes clear licensing and notes. Its long release gap, no recent commits, and repository/package naming mismatch make long-term maintenance and provenance less certain.
52%
Total Score
75
100
81
100
The package has had only two releases, with none in the last 12 months and the latest released in 2017. This is a substantial maintenance concern despite the existing repository and release notes.
There were no commits and no active maintainers in the last three months, consistent with a project that has seen little recent development. The 2023 last push provides some evidence of continued ownership but does not remove the concern.
The repository name does not match the package name and its README does not mention the package. Although the repository is organization-owned, this mismatch leaves package provenance less clear.
The repository uses Make, Composer, and Phing, showing a defined build process, but no security scanning tooling was detected. This is a moderate hygiene gap rather than evidence of abandonment by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log 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.