The package has little consumer documentation, an MIT license file that conflicts with its proprietary manifest declaration, and weak repository hygiene. Its organization-backed repository is not archived and the dependency footprint is minimal, but the maintenance evidence remains thin.
42%
Total Score
50
100
67
75
Only one release exists, published nearly three years ago, with no releases in the last 12 months. That provides little evidence of ongoing maintenance for a package developers may depend on.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long release gap and indicating no recent development activity.
The artifact includes an MIT license file, but the manifest declares the package as proprietary. This mismatch creates avoidable licensing uncertainty even though a recognized license is present.
The package contains no README, tests, or changelog. Missing tests and changelog are normal for a published artifact, but the absence of a README is a real consumer-transparency gap for a library.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counts provide no external adoption or review signal to offset the weak maintenance record.
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.