The package is small and self-contained, with tests, a README, an MIT license, and no runtime dependencies. Its single release and inactive repository make future fixes uncertain.
61%
Total Score
50
100
89
75
The registry namespace and repository belong to the same individual account, so the source ownership aligns with the package identity. Individual ownership provides less organizational continuity than a backed project.
The package has only one release, published about 2 years and 6 months ago, with no releases in the last 12 months. This limits evidence of ongoing maintenance.
There were no commits and no active maintainers in the last 3 months. Combined with the single-release history, this is meaningful evidence of limited ongoing maintenance.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these counts provide little additional confidence in project maturity.
No security policy was found in the repository. This is a transparency gap, though the package's small scope and lack of runtime dependencies partly limit its practical impact.
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.