The package has a solid release history, clear licensing, and a repository that matches the package. A single maintainer, no recent issue activity, and no security policy reduce confidence in ongoing support.
62%
Total Score
50
100
94
75
Only one registry account has publishing access, creating some continuity risk. The matching repository and sustained release history provide partial compensation.
The repository recorded zero commits and zero active maintainers over the last three months. This is a meaningful maintenance concern, although the recent release history provides some counterevidence.
There were no new or closed issues or pull requests in the last month, while 103 issues remain open. This weakens evidence of active support and issue handling.
Composer is used for builds, but no security scanning tooling is present in the repository. The missing scanner is a modest security-hygiene gap.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version ^2.0 | — | — |
workerman/webman-framework Version ^2.1 | — | — |
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.