estebanforge/hyperblocks

HyperBlocks appears suitable for dependency use: it is a stable 1.6.1 release with 33 releases over 164 days, recent repository activity, a matching and documented source repository, tests, changelog, and a clear GPL-2.0-or-later license. The main concern is concentrated maintenance: all 49 commits in the last 3 months came from one contributor, while the repository has no security scanning or security policy and has very limited popularity. These are meaningful resilience and transparency gaps, but they are outweighed by strong recent maintenance and package hygiene.

Latest 1.6.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. This is a resilience concern for releases, although the linked repository shows active development by the same maintainer.

Project backing

The linked repository is owned by a user account rather than an organization, so there is no organizational backing to offset the concentrated maintainer base.

Repo bus factor

One contributor made all 49 commits in the last 3 months, giving the project a bus factor of one and creating a meaningful continuity risk despite the recent activity.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is not inherently unhealthy, but it provides little evidence of community engagement or externally surfaced maintenance.

Repo popularity

The repository has 1 star, 0 forks, and 0 watchers. Low popularity is supporting evidence rather than a verdict, but it means there is little visible external adoption or community redundancy.