integready/laravel-telegram-logging
Its MIT licensing and matching repository make ownership and reuse clear. The tiny eight-file package has no tests or security tooling, so compatibility with current Laravel versions is uncertain.
39%
Total Score
50
75
75
Health Score Breakdown
The package has had no release in nearly seven years: its latest release was published on October 29, 2019, and it has had zero releases in the last 12 months. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, providing no evidence of current maintenance capacity.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but this offers no independent adoption signal to offset the stale maintenance history.
Composer build tooling is present, but no security scanning tools are configured. For a small package this is a hygiene gap rather than a standalone adoption blocker.
The repository has no security policy. This weakens vulnerability-reporting transparency, although it does not by itself show that the package is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 monolog/monolog Version ~1.25 | — | — |
laravel/framework Version 5.6.*|5.7.*|5.8.*|^6.0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 years ago
- Created
- 8 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.