The repository is correctly linked, has a usable README, and published release notes. However, registry releases have stopped for nearly two years, recent commit activity is absent, and the release workflow has weak supply-chain hygiene.
58%
Total Score
50
81
50
No declared license, license file, or repository license file was detected. That leaves the legal terms for using this dependency unclear.
The package has only two releases, with none in the last 12 months and the latest published nearly two years ago. The repository was pushed more recently, which partly offsets the registry inactivity but does not restore release confidence.
The repository recorded zero commits and zero active maintainers in the last three months. The recent push timestamp is compensating evidence, but it does not show ongoing development during the measured period.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
All three analyzed action references are unpinned, the workflow has top-level write permissions, and the audit found a high-confidence archived action plus ad hoc package installation. The cache-poisoning finding has low confidence, so it adds little weight.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
zoujingli/think-install Version ^1.0|@dev | — | — |
zoujingli/think-library Version ^6.1|@dev | — | — |
zoujingli/weopen-developer Version ^1.0|@dev | — | — |
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.