horde/service_gravatar
Tests, release notes, and organization backing improve confidence in the project. Security scanning is absent, and workflow references are only partly pinned, so ongoing dependency hygiene is weaker than its documentation suggests.
68%
Total Score
83
100
83
75
Health Score Breakdown
The package is about 2 years and 9 months old with seven releases, but only one release in the last 12 months. This indicates a mature but relatively slow release cadence.
There were zero commits and zero active maintainers in the last three months. This is a meaningful maintenance concern, even though the repository is not archived and a newer registry release exists.
The repository has one star and two forks, indicating limited public adoption. Popularity is supporting evidence only, so this modestly lowers maturity confidence but does not determine fitness.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. This weakens vulnerability-reporting transparency for a library that makes network requests, though it is not a severe risk on its own.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Michael Slusarz |
| Gunnar Wrobel |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 horde/url Version ^3 || dev-FRAMEWORK_6_0 | — | — |
horde/http Version ^3 || dev-FRAMEWORK_6_0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 months ago
- Created
- 12 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.