neuron-php/cli

This release appears suitable for dependency use, with strong evidence of active maintenance and reasonable package maturity: it has 21 releases over roughly 13 months, 16 releases in the last 12 months, a very recent push, an MIT license, comprehensive README and test coverage, and a non-archived repository backed by an organization. The main reservations are that recent repository activity is entirely concentrated in one contributor, the repository has no security policy or security-scanning tooling, and its CI workflow does not declare top-level token permissions. These are meaningful transparency and continuity gaps, but they do not outweigh the package's active release cadence, tests, and organizational backing.

Latest 0.8.16

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, which is a continuity concern, although registry access records do not establish actual maintenance capacity and the repository is organization-owned.

Repo bus factor

All 3 recent commits came from one contributor, creating a genuine single-person continuity risk; organization ownership provides some compensating handoff capacity but does not remove the concentration.

Repo commit activity

There were 3 commits in the last 3 months, with one active maintainer. The recent activity is present but relatively light and concentrated, warranting some maintenance caution.

Repo popularity

The repository has no stars, forks, or watchers, so external adoption is not demonstrated; popularity is supporting evidence only and this does not outweigh the active releases and maintenance signals.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured. The missing scanning is a transparency gap, while build tooling is appropriate for the package ecosystem.