Package Health/jimmyjs/laravel-report-generator

jimmyjs/laravel-report-generator

The package is clearly documented, licensed, and tied to a matching source repository with release notes. Its maintenance has stalled, and there is no published security policy, so pin this version rather than expecting ongoing compatibility work.

Latest 2.2.0

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry maintainer is listed, which limits publishing redundancy; the linked user-owned repository provides some direct project backing but does not remove the single-maintainer risk.

Release history

The package has 35 releases and a historically regular median interval of about 13 days, but its latest release was over four years ago and there were no releases in the last 12 months. This is a meaningful maintenance concern.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the absence of releases for over four years, this raises abandonment and compatibility risk.

Repo issue activity

There are five open issues and one open pull request, with no issues or pull requests created or closed in the last month. This is consistent with limited current project attention.

Repo tooling

Composer is used as the build tool, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than evidence that the release is unsafe by itself.