The repository has no security policy or security scanning, and its lone registry maintainer provides limited visible continuity. The stable version and clear license help, but do not offset the package’s very limited project history.
42%
Total Score
50
100
83
83
One registry account has publish access. A single maintainer can be sufficient for a small extension, but it provides little visible redundancy when the project is otherwise inactive.
The repository is owned by an individual account rather than an organization. This is not inherently unhealthy, but it offers less backing context for a project with only one maintainer.
Only one release exists, published in November 2018, with no releases in the last 12 months. This is strong evidence of an inactive project and raises abandonment risk.
The repository recorded zero commits and zero active maintainers over the last three months, consistent with the package’s long period without releases. No newer activity is provided to offset that concern.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these counts provide no external adoption signal to compensate for the limited maintenance record.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
kartik-v/yii2-field-range Version dev-master | — | — |
kartik-v/yii2-krajee-base Version >=2.0.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.