lijinma/commander
Its single maintainer and absent security policy limit continuity and transparency. The MIT license, clear README, small dependency footprint, and non-archived repository are positive, but do not offset the maintenance risk.
40%
Total Score
25
67
83
Health Score Breakdown
The latest release was about 11 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency, despite the package having four historical releases.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with its last push being about 6 years ago. This materially weakens confidence in ongoing maintenance.
The registry lists one maintainer. That is not inherently unsafe for a small user-owned project, but it leaves little visible publishing redundancy alongside the stale activity.
Composer build tooling is present, but no security-scanning tooling was detected. This is a modest hygiene gap and does not outweigh the stronger maintenance evidence.
The linked repository has no security policy and no documented process for reporting or handling vulnerabilities. This lowers transparency for a package that may be used in production command-line tooling.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Jinma li |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 lijinma/php-cli-color Version ~1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 11 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.