mohamedhekal/laravel-vulnerability-audit
Documentation, tests, licensing, and security tooling are solid. The small project footprint limits confidence in long-term support.
60%
Total Score
50
93
67
Health Score Breakdown
One registry maintainer is consistent with a small user-backed project, but it leaves limited visible publishing redundancy.
The package and repository are owned by the same individual, so the source relationship is clear, but there is no organization backing to broaden maintenance capacity.
This is the only release, published 421 days ago, with no releases in the last 12 months; that leaves the package's maintenance trajectory unproven.
The repository has had zero commits and zero active maintainers in the last three months, weakening evidence of ongoing maintenance after the initial release.
The repository has no security policy, which is a transparency gap for a package whose purpose is security auditing.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Mohamed Hamad |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 symfony/console Version ^6.0 | — | — |
league/flysystem Version ^3.0 | — | — |
guzzlehttp/guzzle Version ^7.0 | — | — |
laravel/framework Version ^10.0|^11.0 | — | — |
barryvdh/laravel-dompdf Version ^2.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.