The project has a long release history, a stable version, a matching repository, and an organization behind it. Recent maintenance is sparse and concentrated in one contributor, while the repository lacks a security policy and uses one unpinned workflow action.
68%
Total Score
75
100
86
75
The package has existed for about 6 years with 37 releases, but only 1 release in the last 12 months despite a historical median interval of about 16 days, indicating a clear slowdown.
All recent commit activity came from one contributor, creating a thin current maintenance base; organization backing provides some handoff potential but no second active contributor is shown.
Only 1 commit was recorded in the last 3 months, showing limited recent maintenance activity even though the repository is still active.
Composer is used for builds, but no security scanning tools were detected, leaving a modest transparency and maintenance-process gap.
The repository has no security policy, so users have no documented reporting or response process visible in the collected project evidence.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.