The stable version, clear README, matching repository, and release notes provide useful adoption context. However, repository commits and registry releases have both stopped for about one year, while security documentation and automated scanning are absent.
58%
Total Score
50
83
75
The package has 23 releases, but none in the last 12 months; the latest release was about one year ago. This indicates a meaningful maintenance slowdown despite its earlier release history.
There were zero commits and zero active maintainers in the last three months, consistent with maintenance having stalled for about one year. This materially raises abandonment risk.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these numbers provide little external evidence of maturity or active adoption.
Composer build tooling is present, but no security scanning tools are configured. That is a transparency and maintenance gap, though not a severe risk by itself.
The repository has no security policy. Consumers therefore have no documented security reporting process, which modestly lowers transparency.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
varimax/server Version @dev | — | — |
varimax/crontab Version @dev | — | — |
varimax/varimax Version @dev | — | — |
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.