stream-combiner

Release historydanger

The latest release was about 11 years ago, with no releases in the last 12 months. Although the package had eight releases and a regular earlier cadence, this long gap materially raises abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the long release gap, this is strong evidence that maintenance has effectively stopped.

Build provenancecaution

No build attestation or trusted-publisher provenance is present, leaving publication origin less verifiable. This is a transparency gap, but it does not outweigh the direct maintenance evidence by itself.

Maintainerscaution

One registry account has publish access. That is a limited publishing base, though the linked repository is user-owned and the package is small, so this is a secondary concern rather than decisive evidence.

Project backingcaution

The repository is owned by an individual account rather than an organization. That is normal for a small package, but it provides less visible institutional backing for long-term maintenance.