gringlas/go-client
There is no security scanning or security policy, leaving limited evidence of ongoing quality control. The MIT license and minimal dependency footprint are positives, but they do not offset the maintenance gap.
35%
Total Score
0
100
50
75
Health Score Breakdown
The latest release was published in May 2020, more than six years ago, with no releases in the last 12 months. That strongly raises abandonment risk despite six historical releases.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and providing no evidence of current maintenance.
Composer is used for the build, but no security scanning tools are configured. The absence of scanning adds a modest maintenance and dependency-hygiene concern.
The repository has no security policy, which reduces transparency for reporting and handling vulnerabilities. This is a meaningful governance gap for a client library.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Sebastian Köller |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 6 years ago
- Created
- 6 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.