iliaal/nameparser

This release appears healthy and reasonable to depend on: it is actively maintained, has a stable 1.5.0 release line, a clear MIT license, a matching and well-documented source repository, reproducible-looking Composer metadata, and recent repository activity with 66 commits over three months. The main concerns are that the package is young, nearly all recent commits come from one contributor, and the repository lacks a security policy; however, the second active contributor, repository tests, readme, changelog, dependency tooling, and restrictive workflow permissions provide meaningful compensation. The limited popularity is not itself a dependency-health problem.

Latest 1.5.0

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, which creates publishing continuity risk; this is partly offset by the active source repository and its second recent contributor.

Project backing

The repository is owned by an individual rather than an organization, so the concentrated maintainer activity represents a genuine single-owner continuity risk.

Release history

Seven releases in 88 days, with a median interval of about 15 days, show active early maintenance, though the package has limited long-term history.

Repo bus factor

Commit activity is highly concentrated, with one contributor responsible for about 98.5% of recent commits; the presence of a second contributor reduces but does not remove this continuity risk.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.