kriss/multi-process

Release historycaution

The package has six releases over about three years, but none in the last 12 months; the latest release was published in February 2025. This indicates a meaningful maintenance slowdown, though the release history is established rather than abandoned.

Repo commit activitycaution

There were zero commits and zero active maintainers in the last three months. Combined with no registry releases in the last year, this is a concrete maintenance and abandonment concern.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, indicating very limited visible adoption. Popularity is supporting evidence rather than a verdict, so this mildly lowers confidence in long-term project resilience.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tool is configured. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This reduces transparency for a dependency that runs process-management code.