This is a healthy, actively maintained stable release with a clear BSD-3-Clause license, tests in both the artifact and repository, recent release activity, and an active non-archived source repository. Maintenance risk is limited: only one registry publisher is listed, but the repository shows two active contributors and balanced recent commit activity. The main gaps are the absence of a security policy and explicit top-level GitHub Actions permissions, plus no repository security-scanning tool; these are transparency and workflow-hardening concerns rather than evidence that the package is unsafe to depend on.
86%
Total Score
80
100
89
80
One registry account has publish access, which creates some publishing concentration, but this is mitigated by the repository's two active contributors and recent activity.
The repository is owned by an individual user rather than an organization, so the small maintainer and contributor base should be considered when assessing continuity.
The repository has zero stars and forks and only two watchers, indicating limited external adoption; this is supporting caution rather than a health verdict because other maintenance evidence is strong.
Composer build tooling is present, but no security-scanning tool is configured; the latter is a hygiene gap, not a standalone severe risk.
No repository security policy was found, reducing transparency around vulnerability reporting and response procedures.
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.