silviolleite/laravelpwa

Documentation, licensing, tests, and a stable release make integration clearer. The package has seen no registry release for about six years and no recent repository commits, so maintenance may be limited.

Latest 2.0.3

Packagist

58%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Project backing

The package and repository are owned by the same individual account. That is coherent ownership, but it indicates a single-person project rather than organization-backed maintenance.

Release history

The latest registry release was about six years ago, with no releases in the last 12 months. That long publishing gap is a meaningful maintenance concern despite the earlier regular release cadence.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old registry release, this materially raises abandonment risk.

Repo issue activity

There were no new or closed issues and no merged pull requests in the last month, while 61 issues and 10 pull requests remain open. This suggests limited recent maintenance.

Repo tooling

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