The MIT license and focused 41-file codebase are clear. Solo ownership, no README, and no security policy provide little support or consumer guidance.
42%
Total Score
50
100
67
83
Only one release exists, published nearly two years ago, with no releases in the last 12 months. That provides little evidence of continued maintenance.
The published artifact has no README, which makes a library harder to evaluate and integrate. Missing tests and changelog files are normal packaging practice and are not concerns here.
The repository is owned by an individual account rather than an organization, so there is no observed organizational backing to offset the thin maintenance history.
The repository has had zero commits and zero active maintainers in the last three months, reinforcing the risk that development has stopped.
The repository has no security policy, leaving vulnerability-reporting expectations unclear; this is a transparency gap for a dependency.
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.