Usable with caveats: the release is licensed, stable, and backed by a non-archived organization repository, but maintenance evidence is thin. Only two releases exist across 663 days, recent repository activity is absent, and the linked repository does not identify this package in its README.
62%
Total Score
75
79
75
Only two releases have appeared across 663 days, with one release in the last 12 months; this sparse cadence provides limited evidence of sustained maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, leaving little evidence of ongoing development despite the recent push timestamp.
The repository name does not match the package name and its README does not mention the package, so the source-package relationship is not clearly demonstrated.
The repository has only 3 stars and 2 forks, indicating a small user base; this is supporting caution but not decisive because a small package can still be maintained.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented; this is a transparency gap, though not by itself evidence of abandonment.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.