copy-concurrently

Registry deprecationdanger

The package is explicitly deprecated with the message “This package is no longer supported.” The deprecation applies to the package, making this release unfit despite other healthy metadata.

Release historydanger

The package has six releases, but its latest release was in August 2017 and it has had no releases in the last 12 months. This long release gap reinforces the abandonment concern.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last three months. This confirms that current maintenance activity is absent rather than merely infrequent.

Repository archiveddanger

The linked repository is archived, and its last push was in February 2022. An archived source repository is a strong abandonment signal and leaves little expectation of future maintenance.

Project backingcaution

The repository is owned by the npm organization, which provides some project backing context. That backing is outweighed by the repository being archived and the package being deprecated.