goldnead/statamic-events

This release appears healthy and reasonably safe to depend on: it has a matching, active source repository, frequent recent releases, substantial recent commit activity from two contributors, tests in the repository, a changelog, a security policy, and read-only workflow permissions. The main limitations are that the project is only 36 days old, has no observed adoption signals, relies on a single registry publisher, and has no automated security-scanning tool reported; these warrant monitoring but do not indicate abandonment or an immediate dependency-health concern.

Latest v2.5.0

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 for a user-owned project. However, registry access reflects administrative rights rather than actual maintenance, and repository activity shows a second active contributor.

Project backing

The repository is owned by the user account goldnead rather than an organization, so there is no organizational handoff capacity to compensate for maintainer concentration. Actual repository activity from two contributors nevertheless provides current maintenance evidence.

Release history

The package is young at 36 days but has 10 releases in the last 12 months, with a median interval of about 2.3 days. This demonstrates active iteration, though the short history limits evidence of long-term maintenance.

Repo issue activity

There are no open issues and one open pull request, but no issues or pull requests were merged in the last month. With 53 recent commits, the lack of issue activity is not enough to indicate abandonment, though it leaves limited evidence of user-driven maintenance.

Repo popularity

The repository has zero stars, forks, and watchers, so there is no external adoption evidence. Given the package's 36-day age, this is a maturity limitation rather than a severe health failure.