raylin666/guzzle
The project is small and has no security policy or automated security scanning. Its README and changelog help, and the MIT declaration is clear, but future maintenance is uncertain.
38%
Total Score
25
78
83
Health Score Breakdown
The latest release was in January 2022, with no releases in the last 12 months and only two releases overall. This is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving no evidence of active maintenance.
Only one registry account has publishing access. The single-maintainer base increases continuity risk, and no organizational backing is shown to offset it.
The repository has 0 stars, 1 fork, and 1 watcher. Popularity is not decisive by itself, but these very low counts provide little supporting evidence of maturity or community oversight.
Composer build tooling is present, but no security-scanning tools were detected. That leaves an important maintenance and supply-chain hygiene gap for a dependency.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 raylin666 |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 raylin666/pool Version ^2.0 | — | — |
raylin666/utils Version ^1.0 | — | — |
psr/http-message Version ^1.0 | — | — |
guzzlehttp/guzzle Version ^6.3 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 5 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.