Healthy and suitable to depend on. It has a long release history, a current stable release, active recent commits from two contributors, tests, documentation, and a matching repository; the main caveats are limited security-policy and workflow-permission hygiene.
88%
Total Score
80
100
94
80
Registry publishing access is held by one maintainer, which is a modest publishing bus-factor concern; however, repository activity shows a second active contributor.
The repository is user-owned rather than organization-owned, so the small maintainer and contributor base provides less institutional handoff capacity, though recent activity remains healthy.
Composer build tooling is present, but no security-scanning tool was detected, leaving a minor transparency and automated-risk-detection gap.
The repository has no SECURITY.md or equivalent security policy, making vulnerability reporting and response expectations less transparent.
The only workflow does not declare top-level token permissions. No write permissions were observed, but explicit least-privilege configuration would provide stronger workflow hygiene.
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.