joindin/api-client
The project has no README, tests, or changelog, which makes integration and maintenance harder. Its BSD-3-Clause license and example-rich source tree provide useful transparency, but there is no evidence of recent upkeep.
30%
Total Score
0
100
67
88
Health Score Breakdown
The package is about 11 years old, has only 4 releases, and has had no releases in the last 12 months; this is strong evidence of stagnation.
The repository shows 0 commits and 0 active maintainers in the last 3 months, consistent with the last push being in 2014 and indicating substantial abandonment risk.
The artifact has no README, while the repository also reports no tests or changelog. The example files partly help consumers, but the missing project documentation and validation reduce transparency.
The repository name does not match the package name, and no README mention was available. Although this may be a subpackage naming difference, package ownership is less clearly established.
The repository has no security policy. This is a maintenance and disclosure-process gap, though it is less significant than the lack of recent release and commit activity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ~4.1 | — | — |
symfony/serializer Version ~2.5 | — | — |
guzzlehttp/guzzle-services Version ~0.3 | — | — |
Weekly Downloads
Info
- Last Published
- 12 years ago
- Created
- 12 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.