sarbinski/json-api
Documentation and licensing are in place, and the package has a very small dependency surface. The repository and registry show no activity since April 2019, with no security policy or scanning, so maintenance risk is substantial.
32%
Total Score
0
100
71
75
Health Score Breakdown
Only two releases were published, and none appeared in the last 12 months; the latest release is more than seven years old. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release hiatus. No provided maintenance signal compensates for this.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a standalone adoption blocker.
The repository is not archived, which avoids an explicit abandonment marker, but its last push was in April 2019 and does not offset the inactive commit history.
The repository has no security policy. For a library handling API data, this weakens vulnerability-reporting transparency, although it is less serious than the prolonged inactivity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Stanislav Sarbinski |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 8 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.