brahmic/clientdto
Healthy and suitable to depend on. Frequent releases, a stable version, active repository updates, and complete documentation and tests outweigh the small contributor footprint and limited security tooling.
82%
Total Score
83
100
89
90
Health Score Breakdown
Only one registry account has publishing access, creating some bus-factor and release-continuity risk. However, the frequent release history and active repository provide compensating evidence of current maintenance.
The repository has zero stars and forks and only one watcher. This limits external validation and community support, though popularity is supporting evidence and the active release history is stronger evidence of current maintenance.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a transparency gap, though it does not by itself indicate that the package is unsafe to depend on.
The repository has no security policy. That weakens vulnerability-reporting transparency, although the package's documentation, tests, and active releases provide some compensating project hygiene.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Coder Moder |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/http Version ^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0 | — | — |
spatie/laravel-data Version ^4.13 | — | — |
illuminate/collections Version ^10.0|^11.0|^12.0 | — | — |
spatie/temporary-directory Version ^2.3 | — | — |
Weekly Downloads
Info
- Last Published
- 12 days 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.