The small library has no repository tests, security policy, or meaningful community activity. MIT licensing, a matching repository, and no install-time scripts provide some transparency, but they do not offset the long maintenance gap.
38%
Total Score
0
67
75
The package has had no release in nearly six years, with all four releases clustered on November 12, 2020. This is strong evidence of abandonment for a dependency that may need compatibility or security maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the stale release history and leaving no observed maintenance capacity.
The artifact includes a README, but it is only 114 characters and the repository reports no tests. The short documentation and lack of tests reduce transparency for a library consumers must integrate, while the missing changelog is not itself a packaging concern.
The repository has zero stars and zero forks, with one watcher. Popularity is only supporting evidence, but these numbers provide no meaningful external indication of adoption or review.
The repository has no security policy, so there is no stated route for reporting vulnerabilities or communicating fixes. This is a hygiene gap that adds to the risk of relying on an inactive package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
topthink/framework Version ^6.0.0 | — | — |
liz/flysystem-qiniu Version ^1.10 | — | — |
overtrue/flysystem-cos Version ^2.0.0 | — | — |
xxtime/flysystem-aliyun-oss Version ^1.4 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.