sue/child-process

It includes a real README, repository tests, an MIT declaration, and no install-time scripts. The single-maintainer project has no security policy and very little community activity, so future fixes may be limited.

Latest 1.1.2

Packagist

52%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was over three years ago, with no releases in the last 12 months. This is the strongest evidence of possible abandonment and materially lowers confidence in future maintenance.

Maintainers

Only one registry publishing account is listed, which leaves limited publishing redundancy. The linked repository is user-owned rather than organization-backed, so no compensating backing is shown.

Repo issue activity

There are no open issues or pull requests and no recent activity. The clean tracker is not evidence of active maintenance and, combined with the stale release history, reinforces abandonment risk.

Repo popularity

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these values provide little evidence of a broad community that could help sustain the package.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than proof of unsafe code.