limenet/laravel-pdf
Clear licensing, a usable README, repository tests, and regular releases support adoption. Maintenance rests with one active contributor, while all 12 workflow actions are unpinned and a high-confidence automation check is flagged.
65%
Total Score
50
100
100
50
Health Score Breakdown
Only one account has registry publish access. That is a meaningful publishing continuity risk for a user-owned project, though recent releases show the maintainer remains active.
The repository is owned by a user account rather than an organization, so the concentrated ownership and contributor activity are not offset by visible organizational backing.
One contributor made all 2 recent commits, leaving no demonstrated backup contributor and increasing abandonment risk if that maintainer becomes unavailable.
The repository recorded only 2 commits in the last 3 months, so maintenance activity is present but light relative to the package's ongoing release cadence.
The repository has no published security policy, reducing transparency about how vulnerabilities should be reported and handled.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Linus Metzler |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 laravel/framework Version ^12.0 || ^13.0 | — | — |
spatie/laravel-package-tools Version ^1.13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 5 months ago
- Created
- 3 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.