The project has a small public footprint and limited security process. Its repository includes tests and the package has a clear README, while the organization-backed source remains active.
78%
Total Score
67
100
88
50
Only one registry account has publish access, which is a modest publishing continuity risk. Organization ownership of the linked repository provides some compensating project backing.
There is one open issue and no issues or pull requests were opened or closed in the last month. This is a mild transparency and activity gap, but not evidence of abandonment given the recent push and release history.
The repository has zero stars and forks and one watcher, indicating limited adoption evidence. Popularity is supporting evidence, so this lowers confidence more than it undermines the otherwise active maintenance signals.
The repository uses Make and Composer, showing basic build tooling, but no security scanning tools were detected. The missing scanning process is a modest security-hygiene concern.
No repository security policy was found, leaving vulnerability reporting expectations undocumented. This is a transparency gap, not evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version * | — | — |
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.