The MIT license, focused dependency set, README, tests, and matching repository provide useful transparency. Missing security tooling and a small project footprint leave less evidence of ongoing care.
58%
Total Score
50
100
83
83
The repository is owned by a user account rather than an organization, so there is no organizational backing signal. That is not itself a defect, but it provides less evidence of maintainer capacity.
The package has only two releases, both clustered in October 2025, with no later release during the following 11 months. This suggests an initial burst followed by limited ongoing maintenance.
There were zero commits and zero active maintainers in the last three months. Combined with the old last push, this is meaningful evidence of weak current maintenance.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but this leaves little external adoption signal to offset the sparse maintenance record.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a modest repository hygiene concern, not evidence that the package is unsafe by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
topthink/think-queue Version ^3.0 | — | — |
php-amqplib/php-amqplib Version ^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.