Clear MIT licensing, useful documentation, and organization backing improve transparency. However, the repository recorded no commits in three months and the package had no releases in the last 12 months, leaving maintenance capacity uncertain.
58%
Total Score
83
83
75
The package has 11 releases since January 2022, but none in the last 12 months; its latest release was published on August 22, 2025. This materially lowers confidence in ongoing maintenance.
There were zero commits and zero active maintainers in the last three months. Combined with no registry releases in the last year, this is the strongest evidence that maintenance may have slowed or stopped.
The repository has only 1 star and no forks, providing little external evidence of maturity or community support. Popularity is supporting evidence, so this is a modest concern rather than a standalone adoption blocker.
Composer build tooling is present, but no security-scanning tools were detected. This is a transparency and maintenance-hygiene gap, though not evidence of an unsafe release by itself.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a moderate transparency gap for a package used in production applications.
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.