The project has one registry maintainer, no tests, and no security policy. Its README, license declaration, matching repository, and GitHub release provide useful transparency, but do not offset the maintenance concern.
42%
Total Score
25
100
69
75
The package has had three releases, but none in the last 12 months; its latest release was published in April 2025 despite being assessed more than a year later.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the absence of recent releases and raising abandonment risk.
Only one account has registry publishing access, leaving little visible publishing redundancy. The repository is also owned by an individual, so there is no organization backing shown to compensate for that thin base.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide no adoption signal to offset the maintenance concerns.
Composer build tooling is present, but no security scanning tools are configured. This is a modest transparency and maintenance gap for a package handling messaging infrastructure.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ody/task Version ^0.1.2 | — | — |
ody/process Version ^0.1.2 | — | — |
php-amqplib/php-amqplib Version ^3.7 | — | — |
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.