The package is small but has a clear MIT license, repository tests, and no install-time scripts. Its single-maintainer, low-activity project offers limited evidence of ongoing support.
55%
Total Score
50
78
75
One registry maintainer is responsible for publishing. This is not inherently unsafe for a user-owned project, but it leaves a thin publishing base if that maintainer becomes unavailable.
The repository contains tests, while the published artifact omits tests and a changelog; those omissions are normal packaging practice. The package has no README, which modestly reduces consumer guidance.
The registry namespace and repository owner match a personal user account rather than an organization. That is consistent ownership, but it provides limited backing beyond one individual.
Only two releases were published, both by March 2024, with no release in roughly two and a half years. This is meaningful evidence of limited maintenance for a package expected to evolve.
There were no commits and no active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.
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.