The package is small and clearly identified, with a README and no install-time scripts. Its MIT license and non-deprecated status help, but the long maintenance gap makes it a poor long-term dependency.
42%
Total Score
25
78
75
Only two releases were published, both in December 2022, followed by roughly three years and nine months without a release. This is strong evidence of abandonment risk for a package intended for application integration.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long registry release gap. The repository is not archived, but there is no observed recent maintenance.
One registry maintainer is responsible for publishing the package, leaving little visible publishing redundancy. The linked repository is user-owned rather than organization-backed, which makes the thin maintainer base more significant.
The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these values provide no supporting evidence of broad adoption or community backup.
Composer build tooling is present, but no security scanning tooling was detected. This is a modest transparency and maintenance gap rather than a standalone severe 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.