royalcms/aliyun
The MIT license, stable version, and small dependency set provide a clear baseline. Maintenance has effectively stopped, while the very short README and repository mismatch make the package harder to verify and adopt.
38%
Total Score
50
100
60
83
Health Score Breakdown
Only two releases exist, and the latest was published over six years ago with no releases in the last 12 months. This is strong evidence of abandonment risk for a maintained integration library.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided signal shows current maintenance capacity.
The package includes a README, but it is only 17 characters and offers virtually no consumer guidance. Missing tests and a changelog are normal for published artifacts and are not concerns here.
The repository name does not match the package name and its README does not mention the package, making package ownership and source alignment harder to verify. The organization backing reduces, but does not remove, this concern.
The repository has no security policy, leaving no documented path for reporting vulnerabilities. This is a transparency gap, though it is less significant than the maintenance concerns.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Royal Wang |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 ezimuel/guzzlestreams Version ^3.0.1 | — | — |
Weekly Downloads
Info
- Last Published
- 6 years ago
- Created
- 7 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.