forknetwork/guzzle3
The package has tests, a changelog, release notes, and a matching repository, but its source has had no commits or active maintainers for years. Its own README identifies Guzzle 3 as end of life, so pinning it creates substantial abandonment risk.
18%
Total Score
50
61
75
Health Score Breakdown
The artifact has a README, tests, changelog, and release notes, and the README explicitly says Guzzle 3 is no longer maintained and end of life. The documentation helps consumers, but cannot compensate for abandonment.
The latest release was in November 2016, with 0 releases in the last 12 months and 74 releases total. This long period without releases is strong evidence of abandonment.
The repository had 0 commits and 0 active maintainers in the last 3 months, consistent with the README's end-of-life statement and indicating no current maintenance capacity.
The repository has only 2 stars, 0 forks, and 1 watcher. Low popularity is supporting evidence of limited adoption, though it is less important than the clear inactivity.
The project uses Composer and Phing, showing established build tooling, but has no security-scanning tools. This is a secondary gap given the stronger evidence of abandonment.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Michael Dowling |
| Guzzle Community |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 symfony/event-dispatcher Version ~2.1|~3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 14 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.