Clear documentation and a tested artifact make integration straightforward. A single active contributor and no security policy or scanning leave some continuity and oversight risk.
76%
Total Score
50
100
93
75
Only one registry account has publish access. This is a continuity concern for a user-owned project, although the recent release cadence provides compensating evidence of active maintenance.
One contributor made all six recent commits, leaving no demonstrated handoff capacity if that maintainer becomes unavailable.
Six commits were made in the last three months, indicating current activity, though all activity is concentrated in one maintainer.
Composer build tooling is present, but no security-scanning tooling was detected, leaving repository-level security hygiene less visible.
The repository has no security policy, so there is no documented process for reporting and handling vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
abivia/cogs Version ^2 | — | — |
nesbot/carbon Version ^3 | — | — |
symfony/cache Version ^8.1 | — | — |
mlocati/ip-lib Version ^1 | — | — |
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.