geekwright/regdom

Documentation, licensing, tests, and release notes are solid, and the repository remains unarchived. Maintenance has slowed sharply, with no recent commits or releases; all nine workflow actions are unpinned and no security policy is present.

Latest v1.0.9

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry publishing maintainer is consistent with the repository being owned by one user. It offers limited bus-factor resilience, but registry access alone does not establish whether maintenance is active.

Release history

The package has had no release in roughly three years, despite 11 releases overall. That suggests a slowing maintenance pace and raises abandonment concerns for a library that depends on an external public suffix list.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old latest release, this is meaningful evidence of slowing maintenance.

Repo issue activity

There are no new or closed issues in the last month and one open pull request. This indicates little current activity, though the small project size and zero open issues limit the concern.

Repo popularity

The repository has three forks, one watcher, and no stars. Popularity is only supporting evidence, so the low counts modestly reduce external validation but do not determine health for a small library.