The project has recent releases, tests, a license, and a repository that still receives releases. Maintenance capacity is thin: one registry maintainer and no commits in the last three months, with no security policy or automated security scanning.
58%
Total Score
67
100
81
83
Only one account has registry publish access. That is workable for a small package but leaves limited publishing capacity if the maintainer becomes unavailable.
There were no commits and no active maintainers in the last three months. Although releases occurred recently, the lack of recent source activity suggests limited ongoing maintenance capacity.
The repository has zero stars and forks and one watcher. Low visibility is supporting evidence of limited adoption, not a decisive health failure, but it provides little external resilience.
Composer build tooling is present, but no security scanning tools are configured, leaving security-quality checks less transparent.
The repository has no security policy, so there is no documented channel or process for reporting and handling vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^3.0.0 | — | — |
fig/log-test Version ^1.2 | — | — |
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.