ez-php/metrics-statsd

Tests, a changelog, a matching repository, and Composer security scanning provide useful transparency. Organization backing and no install scripts reduce operational risk, though the project lacks a security policy and established long-term history.

Latest 2.5.4

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is only 6 days old, with 10 releases arriving at a median interval of about 35 minutes. That shows active initial development but provides little evidence of sustained maintenance or release stability.

Repo bus factor

One contributor made all 2 recent commits, concentrating project knowledge in a single person. Organization ownership provides some backing, but no second active contributor is shown.

Repo commit activity

The repository has only 2 commits in the last 3 months, all within a very new project. Recent activity exists, but the small history does not yet demonstrate sustained maintenance.

Security policy

No repository security policy was found. This is a transparency gap for reporting vulnerabilities, although the available composer-audit tooling partly offsets broader dependency concerns.

Workflow audit

The sole workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings, and it scopes permissions at job level. However, all 8 action references are unpinned, leaving the workflow exposed to upstream action changes.