Its small scope and clear README keep the adoption burden low. The long maintenance gap, single maintainer, and lack of a security policy make future fixes uncertain.
44%
Total Score
25
75
75
The package has only three releases, all clustered at its first publication in July 2020, with no releases in the last six years. This is strong evidence of abandonment for a security-sensitive wrapper.
The repository recorded zero commits and zero active maintainers in the last three months, and its last push was about six years ago. The stable version does not compensate for the absence of current maintenance.
One registry maintainer creates a thin bus factor, especially alongside the absence of recent releases and commits. The repository is user-owned rather than organization-backed, so there is no provided evidence of broader maintenance capacity.
The repository has zero stars and forks and only one watcher, providing little supporting evidence of community review or adoption. Popularity is secondary, but it does not offset the maintenance gap.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities in a password-related package. Its small scope reduces exposure but does not remove this transparency gap.
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.