yuriidiachuk/laravel-typed-i18n
The project includes repository tests, release notes, a clear license, and Dependabot scanning. Its short history, one-person registry maintenance, three months without commits, and broad unpinned workflow actions leave meaningful continuity and build-hygiene concerns.
65%
Total Score
50
100
83
50
Health Score Breakdown
A post-autoload-dump install-time script can run code during dependency installation, creating some operational exposure, though this signal alone does not show harmful behavior.
Only one account has registry publish access, limiting release continuity if that maintainer becomes unavailable; the repository is user-owned rather than organization-backed.
The repository is owned by an individual matching the package namespace, so the package has clear ownership but no organizational backing to broaden maintenance capacity.
The package is only 95 days old and has three releases, all published within a short initial window, so there is limited evidence of sustained maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, a meaningful sign that maintenance may have paused after the initial releases.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Yurii Diachuk |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/contracts Version ^11.0|^12.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
Weekly Downloads
Info
- Last Published
- 3 months ago
- Created
- 3 months 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.