phramework/jsonapi-client
Clear licensing, tests, and a documented package make adoption easier. The long release gap and inactive repository indicate meaningful abandonment risk, while no security policy leaves maintenance expectations unclear.
42%
Total Score
50
81
50
Health Score Breakdown
The latest release was published nearly five years ago, with no releases in the last 12 months. Although the package has 23 releases and a roughly 60-day historical median interval, the prolonged gap materially raises abandonment risk.
There were no commits and no active maintainers in the last three months, providing direct evidence that current maintenance has stopped or is extremely limited.
There were no new or closed issues and no merged pull requests in the last month, with nine open issues remaining. This reinforces the lack of active maintenance.
Composer build tooling is present, but no security scanning tools were detected. This is a maintenance hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. For a client library handling API interactions, this reduces transparency around vulnerability reporting and response.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Xenofon Spafaridis |
| Alexandros Kalliontzis |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 phramework/util Version ^0.0.0 | — | — |
guzzlehttp/guzzle Version ^6.3.3|^7.1.1 | — | — |
phramework/operator Version * | — | — |
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 10 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.