alializade/laravel-pdf

The package includes a README, tests, an MIT declaration, and a matching source repository. Its small release history and no commits in the last three months leave maintenance uncertain; the missing security policy adds a smaller transparency gap.

Latest 1.1

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with no releases for about three years, this is concrete evidence of inactive maintenance.

Project backing

The package and repository are owned by the same individual account rather than an organization. That is consistent ownership, but it provides less visible institutional backing for long-term maintenance.

Release history

Only two releases were published, both in July 2023, with no releases in the last 12 months. The package is not deprecated, but its release record gives little evidence of ongoing maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy. For a package that processes application data and depends on a PDF engine, this weakens the documented path for reporting and handling vulnerabilities.