Its six runtime dependencies increase the maintenance surface, and the repository has no security policy. The README and MIT declaration provide basic consumer and licensing transparency.
56%
Total Score
50
50
83
75
Six runtime dependencies, including multiple cloud-provider SDKs, create a relatively broad maintenance surface for a small package. No compensating development or test dependency profile is shown.
Only one registry publishing account is listed. This is not proof of abandonment, but it leaves limited visible publishing redundancy for a project owned by an individual.
The repository is owned by an individual user rather than an organization. That is not inherently unhealthy, but it provides less visible institutional backing for a package with one registry maintainer.
The package has made no releases in the last 12 months, and its latest release was about 17 months ago. This is meaningful evidence of slowing maintenance, despite a history of 14 releases.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with no releases in the last 12 months, this points to inactive maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
topthink/think-api Version v1.0.31 | — | — |
alibabacloud/dypnsapi-20170525 Version 1.0.9 | — | — |
alibabacloud/dysmsapi-20170525 Version ^2.0 | — | — |
tencentcloud/tencentcloud-sdk-php Version 3.0.710 | — | — |
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.