Clear licensing, tests, release notes, and a matching repository improve transparency. Low adoption and no published security policy leave less external assurance.
72%
Total Score
80
100
83
75
Only one registry account has publish access. The organization-backed repository makes this less concerning for publishing administration, but it still leaves release access concentrated.
All 38 recent commits came from one contributor, creating a genuine continuity risk. Organization ownership provides some handoff capacity, but no second active contributor is shown.
The repository has no stars or forks and only one watcher, so there is little evidence of broad external adoption or review.
Composer is used for builds, but no security scanning tools are present in the repository, leaving automated vulnerability detection less evident.
The repository has no published security policy, reducing transparency about vulnerability reporting and response.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^3.0 | — | — |
predis/predis Version ^2.3 | — | — |
assegaiphp/util Version ^0.10.0 | — | — |
symfony/console Version ^8.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.