The package is clearly licensed and documented, with tests and a repository that matches its name. Recent work has slowed, and the project has no security policy or automated security scanning, leaving less oversight than a mature dependency.
70%
Total Score
50
100
89
75
The repository is owned by an individual rather than an organization, so the project has less visible institutional backing. The matching repository and long project history provide some compensation.
The project has existed since 2018 with 29 releases, but only one release in the last 12 months. That indicates a mature package with a currently slow release cadence.
The repository recorded no commits and no active maintainers in the past three months. Although a release occurred about five months ago, the lack of subsequent development is a maintenance caution.
Composer build tooling is present, but no security scanning tools were detected. That leaves a meaningful oversight gap for a package that handles API integrations and credentials.
The repository has no security policy, so users have no documented security-reporting path. This is a transparency gap, though it is not evidence of a security incident.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version >=5.1 | — | — |
illuminate/support Version ^5.5|^6|^7|^8|^9|^10|^11|^12|^13 | — | — |
yandex/translate-api Version ^1.5.2 | — | — |
google/cloud-translate Version ^1.7.4 | — | — |
illuminate/translation Version ^5.5|^6|^7|^8|^9|^10|^11|^12|^13 | — | — |
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.