Package Health/shineyork/laravel-package-maker

shineyork/laravel-package-maker

The matching repository, MIT declaration, release notes, and lack of install-time scripts provide useful transparency. One maintainer, no tests or security tooling, and no activity for about seven years leave little evidence of ongoing support.

Latest 2.0

Packagist

42%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, both published in August 2019, with no release in about seven years. That is strong evidence of abandonment for a package developers may need to maintain with current Laravel and PHP versions.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push having occurred in August 2019. No newer maintenance evidence compensates for this gap.

Maintainers

A single registry maintainer creates a thin publishing base, though the linked repository is owned by the same person and the package is small. This still leaves limited visible continuity if that maintainer stops supporting it.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured. For an old package with no recent activity, the absence of automated security checks reduces maintenance transparency.

Security policy

The repository has no security policy, making vulnerability reporting and response expectations unclear. This is a transparency gap, although it is less significant than the package's prolonged inactivity.