daun/statamic-utils

This release appears healthy and suitable for dependency use: it is a stable major release from an actively maintained package with 26 releases over 630 days, 15 releases in the last 12 months, and a recent release cadence of about one week. The linked repository is active, correctly associated with the package, licensed, and has repository tests, documentation, changelog, and CI tooling. The main risks are single-maintainer concentration, the absence of repository security scanning and a security policy, and workflow permissions that are not explicitly restricted; these reduce resilience and transparency but do not indicate abandonment. Low repository popularity and no recent issue activity are not material concerns for this small, focused utility package.

Latest 3.7.3

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publishing access. This is a resilience concern for package publication, although the repository shows that the maintainer is currently active.

Project backing

The repository is owned by an individual user rather than an organization, so there is no organizational succession evidence to offset the concentrated maintainer activity.

Repo bus factor

All 57 recent commits came from one contributor, creating a meaningful bus-factor risk because the repository is user-owned rather than organization-backed.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a transparency and defense-in-depth gap rather than evidence of unsafe behavior.

Security policy

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.