michel/httpclient
Clear documentation, tests, licensing, and a dependency-light design make the release easy to inspect. The missing security policy and scanning reduce transparency; pin this version while the project establishes a longer track record.
63%
Total Score
50
100
83
83
Health Score Breakdown
One registry maintainer creates a thin publishing base and a single point of failure. The matching source repository shows this is a small, user-owned project rather than organization-backed maintenance.
The package is only 16 days old and has two releases, with about 16 days between them. This shows recent publishing but provides too little history to establish durable maintenance.
There were no commits from active maintainers in the last three months, leaving maintenance capacity unproven. The repository was pushed recently and the package is only 16 days old, so this is caution rather than evidence of abandonment.
Composer build tooling is present, but no security scanning tools were detected. The absence of scanning is a transparency and maintenance-hygiene gap, not a standalone severe risk.
The repository has no security policy, so there is no documented channel or process for handling vulnerabilities. This lowers transparency for a network-facing HTTP client.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Michel.F |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 5 days ago
- Created
- 9 months 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.