The client is MIT-licensed, has a stable version, and runs no install-time scripts. However, its last release and repository activity date to about eight years ago, with one maintainer and no security policy; pinning it carries abandonment risk.
40%
Total Score
25
81
75
The package has had seven releases, but none in the last 12 months and its latest release was about eight years ago. This strongly indicates abandonment risk despite its earlier release cadence.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the latest release. No provided signal shows current maintenance capacity.
Only one registry maintainer is listed, leaving little visible publishing capacity if that maintainer becomes unavailable. The repository is user-owned rather than organization-backed, so there is no shown compensating team structure.
Composer is used for builds, which is appropriate, but no security scanning tools were detected. This adds a modest hygiene concern alongside the maintenance gaps.
The repository has no security policy. This is a transparency and vulnerability-reporting gap, although it is less significant than the prolonged inactivity.
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.