This is a healthy, actively maintained release with a stable v1.0.9 version, 15 releases over 145 days, recent repository activity, repository tests and changelog coverage, a matching and clearly identified source repository, and a permissive MIT license. The main reservations are that the project is relatively small and lightly adopted, maintenance is concentrated among two contributors with one responsible for about 71% of recent commits, no security policy is published, and all analyzed workflows grant top-level write permissions. These are meaningful hygiene and continuity concerns, but they do not outweigh the strong recent development, release, testing, and repository evidence.
84%
Total Score
70
100
94
80
Only one registry account has publish access, which is a continuity concern for a user-owned project, although repository activity shows that the project is currently being maintained.
The repository is owned by an individual user rather than an organization, so there is no organizational maintenance handoff indicated; this reinforces the modest maintainer-continuity concern.
Recent work is shared by two contributors, but the top contributor accounts for about 71% of commits; this creates some continuity risk without indicating immediate abandonment.
The repository has only 3 stars, 0 forks, and 1 watcher, indicating limited external adoption and validation; this is supporting caution rather than a decisive health failure.
The repository has no SECURITY policy, leaving vulnerability-reporting and response expectations undocumented; this is a transparency gap for dependents.
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.