Documentation, licensing, release notes, and a matching repository reference make adoption clearer. The remaining concerns are workflow pinning and missing repository security controls.
78%
Total Score
67
93
75
All recent commits came from one contributor, creating a meaningful continuity risk; organization backing provides some capacity to hand maintenance off.
The repository recorded one commit from one active maintainer over the last 3 months, showing recent activity but a thin maintenance base.
Composer is used for builds, but no security scanning tools were detected, so automated vulnerability coverage is limited.
The repository has no published security policy, leaving vulnerability reporting and response expectations unclear.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but all 6 action references are unpinned, weakening build reproducibility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
solarium/solarium Version ^6.4.1 || ^7.0 | — | — |
symfony/http-kernel Version ^6.4 || ^7.3 || ^8.0 | — | — |
symfony/framework-bundle Version ^6.4 || ^7.3 || ^8.0 | — | — |
symfony/dependency-injection Version ^6.4 || ^7.3 || ^8.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.