The project has one publisher and no security policy or scanning, which leaves limited visible maintenance capacity. Its MIT license, substantial README, matching repository, and release notes provide useful transparency, but they do not offset the long inactivity.
43%
Total Score
25
75
50
Only two releases exist, and the latest was published in August 2018; there have been no releases in about 8 years. This is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the latest push being in August 2018. The prolonged lack of observed activity materially lowers maintenance confidence.
One registry maintainer is listed, which leaves little visible publishing redundancy for a user-owned project. This compounds the lack of recent release and commit activity.
Composer is used as the build tool, but no security-scanning tools are present. That reduces automated supply-chain hygiene, without indicating that the package is malicious.
The repository has no security policy, so there is no documented process for receiving or disclosing vulnerability reports. This is a transparency gap, though it is less serious than the long inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
alhimik1986/yii2_js_view_module 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.