Package Health/thelia/thelia-blocks-module

thelia/thelia-blocks-module

This is a generally healthy, actively maintained release: the package has existed for about 4 years and 10 months, has 45 releases including 6 in the last 12 months, is on a stable non-prerelease version, is not deprecated, and its repository is active and not archived. The main concerns are a highly concentrated contributor base, no repository tests or changelog, absent security policy and security scanning, workflows without top-level token permissions, and a repository that neither matches the package name nor mentions it in its README. These issues warrant review before adoption, but the strong release cadence, recent commits, organization backing, and clean workflow-risk findings make the package a reasonable dependency rather than an abandonment concern.

Latest 3.1.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The package has a substantial README, but neither the artifact nor repository contains tests or a changelog. The README documents module architecture and usage, yet the missing validation and change-history artifacts reduce transparency.

Repo bus factor

Two contributors were active, but the top contributor made 13 of 14 commits, or about 93%. The organization backing provides some handoff capacity, yet current activity remains highly concentrated.

Repo issue activity

There are 16 open issues, no new or closed issues in the last month, and 4 pull requests merged in that period. Recent merge activity is positive, but the unresolved issue backlog and lack of issue movement warrant some caution.

Repo package mention

The repository name does not match the package name and its README does not mention the package, creating uncertainty that the linked repository is the canonical source for this release. Organization ownership and the substantial matching module file tree provide some context but do not remove the transparency gap.

Repo popularity

The repository has only 3 stars and 7 forks, indicating limited visible adoption. Popularity is supporting evidence rather than a verdict, so this is not a major health failure.