The small dependency set, clear README, repository tests, release notes, and MIT licensing support routine adoption. Unpinned workflow actions, no security policy, and a thin release cadence leave maintenance hygiene weaker.
68%
Total Score
50
100
88
75
The repository is owned by an individual user rather than an organization, so the one-person registry maintainer base reflects limited visible project backing.
Only 4 releases have been published across about 6 years, with a median interval of about 2.5 years; one release in the last 12 months and a recent latest release partly offset the slow cadence.
There were no commits and no active maintainers in the last 3 months, which is a maintenance concern, although the recent release indicates the project is not clearly abandoned.
Composer build tooling is present, but no security scanning tools were detected; this is a modest transparency and maintenance gap for a dependency project.
The repository has no security policy. This does not show a security defect, but it weakens the project's documented process for handling dependency issues.
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.