Consumer documentation is present, and installation has no lifecycle scripts. The release and repository have been inactive since September 2020, while the linked repository does not identify this package; that makes future fixes and provenance uncertain. Apache-2.0 licensing and a stable version reduce adoption friction.
48%
Total Score
50
86
75
Only two releases are recorded, both by September 2020, with no release in the last 12 months. This is a substantial maintenance concern for a package intended as a dependency.
The repository has recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance activity.
The repository name does not match the package name and its README does not mention the package. That weakens confidence that the linked source repository actually belongs to this release.
The linked repository has no security policy. For an SDK that may handle service credentials and user data, this is a transparency and issue-reporting gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
alibabacloud/tea-rpc Version ^0.1.5 | — | — |
alibabacloud/tea-utils Version ^0.2.0 | — | — |
alibabacloud/tea-oss-sdk Version ^0.3.0 | — | — |
alibabacloud/tea-fileform Version ^0.3.0 | — | — |
alibabacloud/endpoint-util Version ^0.1.0 | — | — |
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.