bzhzz/jos-client
The package has a small, explicit source tree and no install-time scripts, but its documentation and project safeguards are thin. Its maintenance record is the main concern, with no releases or commits for about five years and no security policy.
42%
Total Score
38
100
72
83
Health Score Breakdown
The package has made no releases in the last 12 months, and its latest release was about five years ago. This is strong evidence of abandonment risk despite the five-release history.
There were no commits and no active maintainers in the last three months. Combined with the last push being about five years ago, this materially increases abandonment risk.
No license is declared, and no license file was found in either the package or repository. This creates a concrete legal and transparency problem for dependency adoption.
Only one registry account has publishing access. This is a limited publishing base, but registry access does not establish the project's actual maintenance capacity.
The repository is owned by an individual account rather than an organization, so there is no visible organizational backing to offset the single-maintainer and stale-activity concerns.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 wzx |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 pimple/pimple Version ^3.0 | — | — |
monolog/monolog Version ^1.12|^2.0 | — | — |
guzzlehttp/guzzle Version ^6.3.1|^7.0.1 | — | — |
symfony/http-foundation Version ^2.7 || ^3.0 || ^4.0|| ^5.0 | — | — |
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 5 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.