lesname/validator

This release appears generally suitable to depend on: it has a five-year history, 40 releases, five releases in the last 12 months, a current non-archived repository, an organization owner, repository tests, security scanning, and no install-time lifecycle scripts. The main concerns are that recent commit activity is concentrated entirely in one contributor, the repository does not match the package name and does not provide a confirmed README mention, repository popularity is minimal, and no security policy is present. These reduce resilience and transparency but do not outweigh the evidence of ongoing maintenance and structured project tooling.

Latest 0.6.13

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor made 100% of the five recent commits, creating a genuine single-maintainer continuity risk; organization ownership provides some potential handoff capacity but no second active contributor is shown.

Repo commit activity

Five commits were made in the last three months, showing recent activity, but all were produced by one active maintainer, limiting maintenance redundancy.

Repo package mention

The repository name does not match the package name, and no README package mention was confirmed, leaving some uncertainty that the linked repository is the package's dedicated source.

Repo popularity

The repository has zero stars and forks and only one watcher, so there is little external adoption evidence; popularity is supporting evidence, not decisive on its own.

Security policy

No repository security policy was found, reducing vulnerability-reporting transparency, although this is a documentation gap rather than evidence of abandonment.