The organization-backed project has one active contributor and no published security policy, limiting maintenance resilience. Its small dependency surface and release notes for 4.0.0 reduce adoption friction.
78%
Total Score
83
100
94
50
One contributor made all 7 commits in the last 3 months, creating a meaningful continuity risk. Organization backing provides some handoff capacity, but no second recent contributor is shown.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the release is unsafe.
The repository has no security policy. That makes vulnerability reporting and response expectations less clear for adopters.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but its one action use is unpinned. The absence of a top-level permissions block is not concerning by itself.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
thelia/installer Version ^1.6 | — | — |
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.