It has a readable package, tests, a declared license, and a small dependency surface. Its long-standing lack of development makes future fixes and compatibility work uncertain.
35%
Total Score
0
100
67
75
Only two releases were published, both in March 2016, with no release in about 10 years. This is strong evidence of abandonment for a package intended as an ongoing dependency.
There were no commits or active maintainers in the last three months, consistent with the repository's last activity being about 10 years ago. This materially increases abandonment risk.
The repository name does not match the package name and its README does not mention the package. Although the organization backing provides some context, the linkage remains less transparent.
The repository has zero stars and forks and only one watcher. Popularity is not decisive, but these counters provide no supporting evidence of adoption or community support.
Composer build tooling is present, but no security-scanning tooling was detected. The build setup is a positive; the missing scanner is a minor hygiene gap rather than a standalone severe risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ~1.0.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.