te4g/docker-client
The small dependency set and clear MIT licensing keep integration straightforward. The lack of recent repository activity and security policy leaves maintenance and response capacity uncertain.
62%
Total Score
50
100
88
75
Health Score Breakdown
The repository is owned by an individual user rather than an organization. This is not inherently unhealthy, but it provides less visible institutional backing when combined with the thin recent activity.
The package has five releases over about 34 months, with only one release in the last 12 months. That is a modest maintenance cadence and lowers confidence, though the release history is not dormant.
The repository recorded zero commits and zero active maintainers in the last three months. Together with only one release in the last 12 months, this is a meaningful maintenance concern.
Composer build tooling is present, but no security scanning tools were detected. For a library that handles Docker API access, the missing automated security checks reduce transparency and response confidence.
The repository has no published security policy. That leaves vulnerability-reporting and response expectations unclear, which is a real transparency gap for a client that can access Docker services.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Te4g |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 nyholm/psr7 Version ^1.8 | — | — |
symfony/http-client Version ^7.3 || ^8.0 | — | — |
jane-php/open-api-runtime Version ^7.9 | — | — |
Weekly Downloads
Info
- Last Published
- 8 months 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.