uzulla/legacy_http_request
Long-term maintenance is uncertain, and workflow dependencies are not pinned. The package includes tests, release notes, and a clear legacy warning, but its narrow support story makes it a poor choice for new applications.
55%
Total Score
50
100
81
67
Health Score Breakdown
One registry maintainer is consistent with a small user-owned project, but it leaves limited visible publishing redundancy when recent activity is absent.
The package has only two releases, both in August 2024, with no releases in the past 12 months. This indicates a maturely settled release line only if the legacy scope remains unchanged; otherwise maintenance risk is real.
There were no commits and no active maintainers in the three months before collection; together with the last push in August 2024, this is evidence of prolonged inactivity.
The repository name does not match the package name and its README does not mention the package. Although name differences can occur in subpackages, both observations reduce confidence that the linked repository is clearly dedicated to this release.
The repository uses Composer build tooling, but no security scanning tools were detected. This is a modest transparency gap rather than a severe risk for this small legacy package.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 uzulla |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^6.5.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 years ago
- Created
- 2 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.