split-array-stream

Release historydanger

The package has five releases but none in the last 12 months, with the latest release about eight years ago. That long gap materially raises abandonment and compatibility risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the release-history concern about long-term maintenance.

Build provenancecaution

No build attestation or trusted-publishing provenance is present, reducing publication transparency; this is a supply-chain hygiene gap rather than evidence that the release is unsafe.

Lifecycle scriptscaution

A prepare script runs during installation, which can add build or execution complexity; no provided signal shows that it is unsafe or unnecessary, so this is a limited concern.

Maintainerscaution

Only one registry maintainer is listed. A single-person publishing base increases continuity risk, especially alongside the lack of recent project activity.