The package is well documented and tested, with a stable release and an organization behind the repository. Recent work is concentrated in one contributor, and the project has no security policy or automated security scanning.
72%
Total Score
90
100
89
88
All 10 commits in the last three months came from one contributor. Organizational ownership partly offsets this concentration, but the lack of a second active contributor remains a maintenance risk.
The repository has no stars, forks, or watchers. Popularity is only supporting evidence, so this lowers confidence in external adoption but does not outweigh the observed maintenance and packaging evidence.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces supply-chain visibility for a dependency project.
The repository has no security policy. This is a transparency and vulnerability-reporting gap, although it is not evidence of an unsafe release by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^1.0 || ^2.0 || ^3.0 | — | — |
psr/cache Version ^1.0 || ^2.0 || ^3.0 | — | — |
doctrine/orm Version ^3.4 | — | — |
sunrise/translator Version ^1.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.