zf1s/zend-service

Usable with caveats: it has a long release history, a recent stable release, and active organization backing. Maintenance evidence is thin, with only one commit in the last three months, no tests or changelog, and no security policy.

Latest 1.16.2

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A README is present, but neither the artifact nor repository contains tests or a changelog. For a small split library this is a real maintenance-transparency gap.

Repo bus factor

All recent activity comes from one contributor, creating concentration risk. The organization-owned repository provides some handoff capacity, so this is a caution rather than a severe risk.

Repo commit activity

Only one commit was made in the last three months by one active maintainer, which is thin recent maintenance evidence even though the package has a long release history.

Repo issue activity

There were no new or closed issues or pull requests in the last month, and issue totals are unavailable. This gives limited evidence of community review or maintenance activity.

Repo popularity

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but this provides little external confirmation of community adoption.