averay/extensible-blocks

The package has had only one release, and it is still version 0.1.0 after more than two years. The linked repository was pushed recently and has a clear README, license, and read-only workflow permissions, but all five workflow actions are unpinned and no security policy is present.

Latest v0.1.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry maintainer is consistent with an individually owned project, and the linked repository is owned by the same individual. This indicates a thin bus of responsibility but not an unexplained ownership mismatch.

Release history

Only one release exists, published more than two years ago, with no releases in the last 12 months; this limits evidence of release maturity, although recent repository activity partly offsets abandonment concerns.

Repo commit activity

There were no commits and no active maintainers in the last three months, weakening evidence of ongoing development; the recent repository push prevents this from being conclusive abandonment evidence.

Repo popularity

The repository has zero stars and forks and one watcher. This is weak supporting evidence of maturity, but popularity alone does not determine whether a small package is healthy.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe dependency risk.