Package Health/matthewbdaly/laravel-dynamic-serving

matthewbdaly/laravel-dynamic-serving

Clear documentation, tests, licensing, and a matching repository support basic transparency. However, the project has had no release or commit activity for about 8 years and has no security scanning or policy, making future compatibility and maintenance uncertain.

Latest 0.0.2

Packagist

40%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, with the latest about 8 years ago and no releases in the last 12 months. This is strong evidence of abandonment risk, although the small package scope may reduce maintenance needs.

Repo commit activity

There were no commits and no active maintainers in the last 3 months, consistent with the roughly 8-year release gap. This materially increases abandonment and compatibility risk.

Repo tooling

The project uses Composer, providing normal build tooling, but no security scanning tools were found. For a small middleware package this is a hygiene gap rather than proof of unsafe code.

Repository archived

The repository is not archived, which preserves a path for maintenance, but it was last pushed about 8 years ago. The inactive repository therefore does not offset the age of the release.

Security policy

The repository has no security policy, leaving vulnerability-reporting and response expectations unclear. This adds transparency risk, though it is less serious than the long inactivity.