jleagle/gazelle-api-client
The README gives practical usage examples, and the package has a stable 1.0.1 release with a small, focused codebase. Its single-maintainer ownership and lack of security tooling leave little visible support if the integration breaks.
42%
Total Score
25
79
50
Health Score Breakdown
The latest release was published in January 2016, with no releases in the last 12 months; this is a strong sign of abandonment for an API client that may need ongoing compatibility work.
The repository has recorded zero commits and zero active maintainers in the last 3 months, consistent with the package having been inactive for about 10 years.
No declared license, license file, or repository license file was detected, leaving the legal terms for adopting the code unclear.
Only one registry maintainer is listed, so publishing and maintenance capacity appears concentrated in a single person; no organizational backing is shown to compensate for that concentration.
The repository has no security policy, reducing transparency about how vulnerabilities in this credential-using API client should be reported and handled.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 James Eagle |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 jleagle/helpers Version ~0.0 | — | — |
jleagle/curl-wrapper Version ~1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 11 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.