The package is licensed, documented, and its repository matches the package. A single individual publishes it, with no security policy or scanning to add confidence.
40%
Total Score
25
75
50
The package has only two releases, and none in the past 12 months; its latest release was about 6 years ago. This is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the past 3 months, consistent with the long release gap and providing no evidence of current maintenance.
Only one registry account has publishing access, and the project is backed by an individual rather than an organization. This leaves limited visible publishing capacity, although access records alone do not prove inactivity.
Composer build tooling is present, but no security scanning tools are configured. That removes a useful maintenance safeguard, though the small package scope limits how heavily this should weigh.
The repository has no security policy, so users have no documented channel or process for reporting vulnerabilities. This is a transparency and maintenance gap, not evidence of malicious behavior.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
yiisoft/yii2-debug Version ^2.1 | — | — |
vjik/yii2-psr-logger-proxy Version ^1.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.