The project has recent releases and commits from two contributors under an organization, with a stable 3.0.0 release and clear documentation. Workflow references are unpinned, and the repository lacks security scanning and a security policy.
82%
Total Score
100
100
86
50
The repository name does not match the package name and its README does not mention the package, so the package-to-source relationship is less transparent despite the repository being linked.
Composer build tooling is present, but no security-scanning tool was detected. This is a process gap rather than evidence of abandonment.
The repository has no security policy. That weakens vulnerability-reporting transparency, although the active repository and recent releases provide some compensating maintenance evidence.
The only workflow was fully analyzed with no dangerous triggers or audit findings, but its single action reference is unpinned. The missing top-level permissions block is acceptable on its own, while the unpinned action is a modest reproducibility and supply-chain hygiene gap.
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.