Documentation, licensing, and release notes make integration straightforward. Maintenance is concentrated in one contributor, and all four workflow actions are unpinned, though the workflow uses read-only permissions and shows no audited dangerous findings.
82%
Total Score
50
100
94
83
The repository is owned by a user account rather than an organization, so the single-contributor maintenance concentration is not compensated by visible organizational backing.
All two recent commits came from one contributor, leaving maintenance dependent on a single active person and increasing abandonment risk.
The repository had two commits in the last three months, so activity continues, but the cadence is modest for a package with frequent releases.
Composer build tooling is present, but no security-scanning tool was detected, leaving a modest transparency and maintenance gap.
The repository has no security policy. This is a documentation gap, though it is partly offset by the small, clearly identified project structure and active release history.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
cycle/orm Version ^2.12.3 | — | — |
psr/container Version ^1.0 || ^2.0 | — | — |
cycle/database Version ^2.15 | — | — |
cycle/annotated Version ^4.4 | — | — |
spiral/tokenizer Version ^2.14 || ^3.0 | — | — |
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.