The single maintainer, three-star repository, and absent security policy provide little visible support for future fixes. A clear MIT license, substantial README, and no install-time scripts reduce adoption friction but do not offset the maintenance concern.
38%
Total Score
25
79
75
The package has had no release in more than six years and only three releases overall, indicating severe abandonment risk. Its very short initial release interval does not compensate for the prolonged silence.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance activity.
One registry maintainer creates a thin publishing base and increases continuity risk if that person becomes unavailable. The repository is user-owned rather than organization-backed, so there is no provided evidence of broader support.
Three stars, no forks, and one watcher show a very small user and contributor footprint. Popularity is only supporting evidence, but this offers little indication of a durable maintenance community.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a package handling API credentials and communications services.
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.