mohamed-hathout/debugger
The README and small dependency set make adoption straightforward, while the MIT declaration and lack of install scripts reduce avoidable friction. Limited repository security practice and a single publisher leave less evidence of long-term maintenance capacity.
62%
Total Score
50
100
83
75
Health Score Breakdown
Only one account has registry publish access, and project backing identifies the repository owner as an individual rather than an organization. That leaves limited observable publishing redundancy.
Five releases are recorded, with four in the last 12 months, but the releases are tightly clustered and the latest is the only recent endpoint shown. This provides some release activity without strong evidence of a sustained cadence.
The repository has one star, no forks, and no watchers. Low popularity is only supporting evidence, but it provides little external evidence of maturity or community support.
Composer is used as the build tool, but no security scanning tools are reported. For a package that handles application debugging data, this is a modest transparency and maintenance gap.
The linked repository has no security policy. This weakens the project's stated process for receiving and handling security reports.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Mohamed Hathout |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 laravel/framework Version ^12.19 | — | — |
livewire/livewire Version ^3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 1 year 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.