zf1s/zend-serializer

Healthy and reasonable to adopt, with a small maintenance risk. It has a long release history, four releases in the last year, an active organization-owned repository, and clear licensing, but recent work is limited to one contributor and the project has no tests or security policy.

Latest 1.16.2

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact includes a README but no tests or changelog, and the repository likewise has neither. For a small automatically split library this is a transparency and maintenance gap, though the package documentation explains its monorepo-derived structure.

Repo bus factor

All recent commits came from one contributor, creating a concentrated maintenance dependency. Organization ownership provides some handoff capacity, but no second active contributor is shown.

Repo commit activity

The repository recorded one commit by one active maintainer in the last three months. Recent activity exists, but the volume is thin for ongoing maintenance.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little external validation.

Repo tooling

Composer is used as a build tool, but no security scanning tools are configured. The missing scanning is a hygiene gap, not evidence that the release is unsafe.