ezijing/nacos
The package lacks a consumer README, which makes integration harder. Its user-owned project has had no release or repository activity since January 2021, and adoption evidence is minimal.
35%
Total Score
100
75
75
Health Score Breakdown
The package has no README, which is a meaningful consumer-facing documentation gap for a library. The absence of published tests and a changelog is normal packaging practice and does not add concern.
Only three releases were published, all clustered in January 2021, with no releases in the last five years. This strongly lowers confidence in ongoing maintenance.
The repository has zero stars and forks and only one watcher, offering little supporting evidence of community adoption or review. Popularity is not decisive by itself, but it reinforces the maintenance concern.
The repository is not archived, but its last push was in January 2021, providing no evidence of active source maintenance since then.
No security policy is present, reducing transparency for reporting and handling vulnerabilities. This is a hygiene and maintenance concern rather than evidence that the package is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 hyperf/utils Version ~2.1.0 | — | — |
hyperf/guzzle Version ~2.1.0 | — | — |
hyperf/contract Version ~2.1.0 | — | — |
hyperf/load-balancer Version ~2.1.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.