The README is only 365 characters and documents a different package, while the repository has no tests or security policy. MIT licensing and no install scripts are reassuring, but they do not offset the long inactivity.
42%
Total Score
50
67
75
Only one registry account has publish access, which limits visible publishing capacity for a user-owned project. The concern is compounded by the absence of recent release and commit activity.
A README is present, but it is short and appears unrelated to this package; the absence of tests and a changelog is normal for a published artifact and is not itself a gap.
The package has had no release in more than five years, with zero releases in the last 12 months. This is strong evidence of abandonment risk, despite the package not being deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No newer activity is provided to compensate for the apparent inactivity.
The repository name matches the package, but its README does not mention the package and instead documents a different Hanzi package. That weakens confidence that the published package and source repository are transparently aligned.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.