pavelzanek/laravel-deepl
Its MIT licensing, matching repository, and tested source provide useful transparency. A single maintainer and no security policy leave limited visible support for long-term maintenance.
60%
Total Score
50
100
88
83
Health Score Breakdown
Only one registry maintainer is listed. This is not inherently unsafe for a user-owned project, but it leaves limited visible publishing redundancy when combined with absent recent activity.
The repository is owned by an individual rather than an organization, so the single-owner maintenance model is visible and should be weighed with the inactive commit history.
The package has had no release in nearly two years and no releases in the last 12 months, which is a meaningful maintenance concern despite five releases overall.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with a project whose development has stopped for nearly two years.
Composer build tooling is present, but no security-scanning tool is reported, leaving a modest transparency and maintenance gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Pavel Zaněk |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.0 | — | — |
deeplcom/deepl-php Version ^1.9 | — | — |
illuminate/support Version ^11.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 2 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.