The project is backed by an organization and has a matching repository, license, tests, and changelog. It lacks a security policy, while its seven runtime dependencies add maintenance surface.
62%
Total Score
75
50
88
75
Seven runtime dependencies, all within the same package family, create meaningful maintenance surface, although the focused dependency set is not unusually broad.
Only two releases have been published since June 2022, with no release in the last 12 months and a median interval of about 829 days. This indicates a slow and potentially weakening release cadence.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the long registry release gap, this is a meaningful maintenance concern.
The repository uses Composer for builds, but no security scanning tools were detected. The missing automated security coverage is a modest hygiene gap.
No security policy was found in the repository. This weakens vulnerability-reporting transparency, though it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
mecha-cms/x.page Version ^3.0.0 | — | — |
mecha-cms/x.user Version ^2.0.0 | — | — |
mecha-cms/x.alert Version ^3.0.0 | — | — |
mecha-cms/x.asset Version ^2.0.0 | — | — |
mecha-cms/x.layout 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.