raselsay/laravel-pdf

Usable with caveats: the package is clearly structured, licensed, tested, and not deprecated, but it has had no commits for about 6 months after only two releases on the same day. Its small, unproven project footprint and limited repository security hygiene warrant caution before adopting it for a critical application.

Latest v1.0.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The package and repository are owned by the same individual account, so the source appears aligned with the package, but there is no organizational backing to offset the very small maintainer footprint.

Release history

Only two releases exist, both published on the same day, and there have been no additional releases over roughly 6 months; this gives little evidence of sustained maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last 3 months, indicating currently inactive development and increasing abandonment risk.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month; this is neutral for a tiny project but offers no evidence of an active maintenance community.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is not required for health, but these counts provide no supporting evidence of community adoption or review.