splitstack/laravel-rome

This is a young but currently active and reasonably transparent package. The linked repository is not archived, was pushed on the assessment date, has 17 commits from two active contributors in the last three months, includes extensive tests and CI, and has no install lifecycle scripts or registry deprecation. However, the package is only 56 days old with two releases and remains on the 0.1.x line, while 94% of recent commits come from one contributor; low repository adoption, no security policy, incomplete workflow permission declarations, and no changelog add real maturity and maintenance-risk concerns. It is a plausible dependency for teams comfortable with an early-stage package, but should be monitored rather than treated as mature infrastructure.

Latest v0.1.1

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. This is a mild resilience concern for a user-owned project, although repository activity shows a second active contributor.

Project backing

The repository is owned by an individual GitHub user rather than an organization, so there is no organizational maintenance capacity to offset the concentrated contributor base.

Release history

The package is only 56 days old and has two releases separated by about 56 days, providing limited evidence of long-term maintenance and release reliability.

Repo bus factor

Recent activity is highly concentrated: one contributor made 16 of 17 commits, or about 94%, despite a second contributor being active. This creates a meaningful continuity risk for a user-owned project.

Repo popularity

The repository has 7 stars, 0 forks, and 0 watchers. This is limited community validation, but popularity is supporting evidence rather than a standalone health verdict.