daun/statamic-loupe

This release appears healthy and suitable for dependency use: it is a stable 4.2.0 release with 18 releases over 654 days, six releases in the last 12 months, recent repository activity, a matching and clearly documented source repository, an MIT license, changelog, and comprehensive repository tests. The main concerns are that all 13 commits in the last three months came from one contributor, the repository has very low popularity, and it lacks an explicit security policy and top-level workflow permissions declaration. These are meaningful resilience and hygiene gaps, but they do not outweigh the evidence of active maintenance and release continuity.

Latest 4.2.0

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. This is a mild publishing resilience concern, although the linked repository shows the same individual actively maintaining the project.

Project backing

The repository is owned by a user account rather than an organization, so there is no organization-level backing to offset the concentrated maintainer activity.

Repo bus factor

One contributor made all 13 commits in the last three months, creating a clear single-maintainer continuity risk with no demonstrated backup contributor.

Repo popularity

The repository has only 3 stars, 0 forks, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these values provide little external adoption or review evidence.

Repo tooling

The repository uses Composer build tooling, but no security scanning tools were detected. The missing scanning is a hygiene gap, though it is not evidence of abandonment by itself.