The package is clearly identified, MIT-licensed, and has a matching repository with a usable README. Its one-person project has had no commits or releases for about four years, and it has no security policy.
52%
Total Score
50
100
88
75
The repository is owned by the same individual namespace as the package, with no organization backing shown. That is consistent ownership, but it leaves a thin maintenance base when combined with inactive commits.
Only two releases exist, with none in the last 12 months and the latest release about four years ago. This strongly limits evidence of ongoing maintenance, although the package is not deprecated.
There were no commits and no active maintainers in the last three months, consistent with the last repository push being about four years ago. This is the main abandonment concern for depending on the package.
Composer is used for builds, but no security scanning tools are configured. That is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters for a queue-management component but is less severe than archived or deprecated status.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
yiisoft/yii2 Version ~2.0.0 | — | — |
yiisoft/yii2-jui Version ~2.0.0 | — | — |
2amigos/yii2-chartjs-widget Version ~2.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.