neomerx/json-api
Licensing, documentation, and dependencies are clear and lean. No security policy is published, limiting transparency for future maintenance and vulnerability reporting.
57%
Total Score
25
100
86
50
Health Score Breakdown
The package has 75 releases over more than 11 years, but there have been no releases in over 6 years. This strongly raises abandonment risk despite the historically consistent release cadence.
The repository recorded no commits and no active maintainers in the last 3 months, while its last push was nearly 5 years ago. This confirms that maintenance has effectively stopped.
There were no new or closed issues and no merged pull requests in the last month, with 8 issues still open. This supports the broader evidence of inactive maintenance.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it does not outweigh the package's other maturity evidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 neomerx |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 6 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.