38%
Total Score
unhealthy
About four years without a release, a one-person project, and a repository/package-name mismatch make this a risky dependency.
Only three releases were published, all clustered in August 2022, with no release in about four years and none in the last 12 months. This is strong evidence of abandonment risk.
The package has one registry maintainer, and the project backing signal identifies an individual-owned repository rather than organization backing. That leaves limited visible continuity capacity.
The artifact has no README, tests, or changelog. Missing tests and changelog are normal for published artifacts, but the absent README reduces consumer transparency for a validation library.
The repository name does not match the package name, and no README package mention was available. This creates uncertainty that the linked repository is the package's actual project source.
The repository has zero stars and forks and only one watcher. Popularity is not decisive by itself, but it provides no supporting evidence of community adoption or oversight.
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.