mfd/typo3-prometheus

This is a generally healthy, established package with releases dating back to 2017, four releases in the last 12 months, a stable non-prerelease version, an active non-archived organizational repository, and a clear package/repository match. The main concerns are limited recent contributor activity concentrated entirely in one contributor, no repository tests or changelog, no security policy, and workflows that do not declare top-level token permissions; these are meaningful hygiene and continuity gaps but do not outweigh the evidence of ongoing maintenance and project backing.

Latest 2.2.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A substantive README documents installation, usage, metrics, and security considerations, but neither the artifact nor repository contains tests or a changelog. The GitHub Releases integration provides some release communication, but the missing tests and changelog remain modest transparency gaps.

Repo bus factor

All two recent commits came from one contributor, producing a 100% top-contributor share and a one-person recent contributor base. This creates a genuine continuity risk, partially mitigated by the repository being owned by an organization.

Repo commit activity

The repository received two commits in the last three months, demonstrating ongoing activity, but only one active maintainer contributed them. The cadence is therefore positive but thin.

Repo issue activity

There are four open issues and no open pull requests, with no issues or pull requests created or closed in the last month. This suggests limited recent community activity, although it does not by itself establish abandonment.

Repo popularity

The repository has 12 stars and 2 forks, indicating a small user and contributor footprint. Popularity is supporting evidence rather than a requirement, so this is only a mild maturity concern.