lornequinn/starter

This release has credible package structure, an MIT declaration, tests in both the artifact and repository, a matching and package-referencing repository, and recent release activity. However, the linked repository is archived, with zero commits and zero active maintainers in the last 3 months; that severe abandonment signal outweighs the recent v0.1.2 publication and makes this a significant liability for a new dependency. The package is also young and pre-1.0, maintained by one registry account, and lacks some security-governance hygiene, so adoption should require a clear plan to vendor, fork, or replace it if maintenance is needed.

Latest v0.1.2

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded 0 commits and 0 active maintainers over the last 3 months, providing no evidence of ongoing maintenance and reinforcing the archived-repository concern.

Repository archived

The linked repository is explicitly archived, which is a severe abandonment risk even though it was pushed recently on September 4, 2026; archival status materially outweighs that recency.

Lifecycle scripts

The package declares four Composer lifecycle scripts, including post-create-project and post-update hooks. These are plausible for a Laravel starter template, but they increase install-time behavior and deserve review before adoption.

Maintainers

Only one registry account has publish access. That is a limited operational bus factor for a user-owned project, and no stronger organizational backing is provided by the project_backing signal.

Package scaffolding

Tests are present in both the package artifact and source repository, which is appropriate for this Laravel starter project. The missing README and changelog reduce transparency, but the repository contains tests and the package appears to be a project scaffold rather than a conventional library.