judicialcouncil/emma
The package has tests, a clear MIT license, and organization-backed ownership. Its repository has had no commits or releases since October 2020, and it lacks a security policy or security scanning, leaving maintenance and review concerns.
45%
Total Score
50
75
75
Health Score Breakdown
The package has had no release in nearly six years, with eight releases clustered around October 2020 and none in the last 12 months. This strongly lowers confidence in ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating inactive maintenance.
The project uses Composer and Phing, which supports reproducible build and test workflows, but it has no security scanning tools. The build tooling partly compensates for the security-process gap.
The repository has no security policy, so there is no stated process for reporting or handling vulnerabilities. This is a meaningful transparency gap for an API client.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Mark Roland |
Direct Dependencies
No direct dependencies.
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.