riki137/stream-ipc

Usable with caveats: the package is well documented, tested, licensed, and has a clean low-dependency design, but it has not had a release or commit activity for over a year. Its small one-person project and limited security tooling make long-term maintenance less certain.

Latest 1.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were no commits and no active maintainers during the last three months. Combined with the long release gap, this is the main abandonment concern for depending on the package.

Release history

Six releases were published, but none appeared in the last 12 months and the latest release is now over a year old. This lowers confidence that bugs and compatibility issues will receive timely fixes.

Repo tooling

Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency and maintenance gap rather than evidence that the package is unusable.

Repository archived

The linked repository is not archived, but its last push was over a year ago, so the absence of archival status does not offset the weak recent maintenance evidence.

Security policy

The repository has no security policy. For an IPC library, the lack of a documented vulnerability-reporting process is a genuine transparency gap, though it is not by itself evidence of unsafe code.