Explicit, declarative queue arguments for Magento's MessageQueue framework
66%
Total Score
caution
A brand-new package with only two releases and no observed commit activity has little maintenance history.
The package is maintained under a personal repository rather than an organization-backed project. That is normal for a small module but provides less visible institutional continuity.
The package is only hours old and has two releases, so there is not enough history to establish sustained maintenance. The rapid early releases are not evidence of abandonment, but the record remains unproven.
There were zero commits and zero active maintainers in the last three months. Because the repository and package were created only hours ago, this is mainly a lack of maintenance history rather than confirmed abandonment.
Composer is used for the build, but no security-scanning tool was detected. This is a modest repository hygiene gap, while the package's tests and clear source tree provide some compensating transparency.
The repository has no security policy. That weakens vulnerability-reporting transparency, although it does not by itself indicate that the code is unsafe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
magento/framework Version 102.0.*||103.0.* | — | — |
magento/framework-message-queue Version 100.3.*||100.4.* | — | — |
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.