Package Health/goldnead/statamic-brand-context

goldnead/statamic-brand-context

This is a healthy-looking but very young package with strong evidence of active development and reasonable release hygiene. It has 27 stable releases over 46 days, was pushed very recently, has substantial recent commit activity from two contributors with balanced participation, a matching repository, documented licensing, README and changelog coverage, repository tests, a security policy, and read-only workflow permissions. The main reservations are its short operating history, zero public popularity metrics, a single registry maintainer, and the absence of automated security scanning; these reduce maturity and transparency somewhat but do not outweigh the current maintenance evidence.

Latest v1.13.1

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Maintainers

Only one account has registry publish access, which creates publishing concentration; however, registry access is administrative evidence and does not outweigh the repository's observed two-contributor activity.

Project backing

The repository is owned by the named individual goldnead rather than an organization, so there is no organizational maintenance redundancy; this is consistent with, but does not independently worsen, the observed two-contributor activity.

Release history

Twenty-seven releases in the first 46 days demonstrates active publishing, but the very short package history means long-term maintenance is not yet established.

Repo popularity

The repository has zero stars, forks, and watchers, so there is no external adoption evidence; given the package is only 46 days old, this is a maturity concern rather than a severe health failure.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. The missing scanning is a hygiene gap, though it is partly offset by the repository's other security controls.