The package includes tests, extensive documentation, and a stable release line. Maintenance is active, but the small contributor base and workflow configuration leave avoidable operational gaps.
78%
Total Score
67
100
94
75
The repository is owned by an individual account rather than an organization, so the concentrated contributor activity represents a genuine continuity concern.
Three contributors were active, but one supplied about 72% of recent commits. The second contributor remained active, partly reducing but not removing concentration risk.
Composer is used for builds, but no security-scanning tools were detected. This is a modest transparency and maintenance gap for a package handling background operations.
The repository has no security policy, leaving vulnerability-reporting expectations and response guidance undocumented.
The single analyzed workflow has top-level write permissions and all five action references are unpinned. No untrusted checkout, script injection, or high-confidence audit finding was detected, so this is a hygiene caution rather than a severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
evolution-cms/evo-ui Version ^1.1 | — | — |
evolution-cms/evolution Version ^3.5.7 | — | — |
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.