The MIT license, readable documentation, and repository tests provide useful transparency. Its single-person ownership and missing security policy leave little evidence of ongoing support.
48%
Total Score
25
81
75
The package has had no release in over six years, with all 9 releases concentrated on September 23, 2020. This is strong evidence of abandonment risk, though the package is not registry-deprecated.
The repository recorded 0 commits and 0 active maintainers in the past 3 months, consistent with the long gap in releases and indicating no current maintenance capacity.
Only one registry account has publish access. For a user-owned project this is a thin maintainer base, increasing continuity risk when combined with the absence of recent activity.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and maintenance-hygiene gap rather than evidence of unsafe behavior.
The repository has no security policy, leaving no documented route for reporting vulnerabilities or communicating security handling. This adds a transparency gap for a package with no recent maintenance evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
google/cloud Version ^0.140.0 | — | — |
guzzlehttp/guzzle Version ^7.0 | — | — |
illuminate/support Version ^5.6||^6.6||^7.0||^8.0 | — | — |
scn/deepl-api-connector Version dev-master | — | — |
themsaid/laravel-langman Version ^1.3 | — | — |
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.