The six-file tree and two runtime dependencies keep adoption straightforward. The MIT declaration and matching repository help, but there is no security policy or scanning and the project has little community activity.
43%
Total Score
25
100
78
88
The latest release was in January 2018, about 8 years ago, and there were no releases in the last 12 months. This is strong evidence of abandonment risk despite the package having a stable release history overall.
The repository had no commits and no active maintainers in the last 3 months, consistent with the long release gap. This materially reduces confidence that defects or compatibility issues will be addressed.
The registry namespace and repository owner match, but the owner is an individual user rather than an organization. This provides limited backing context and does not offset the inactivity.
The repository has 1 star, 0 forks, and 1 watcher, providing little evidence of a user or contributor community to identify and address problems.
Composer is used for the build, which is appropriate, but no security-scanning tools are present. The missing scanning is a modest supply-chain hygiene gap, not a standalone severe risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
zongphp/request Version ~2.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.