spiffy/spiffy-dispatch

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement specified. This is a severe adoption risk because the registry no longer presents it as an actively supported dependency.

Release historydanger

The package has only one release, published in July 2014, and none in the following 12 years. That strongly indicates abandonment for a dependency intended for ongoing use.

Repo commit activitydanger

The repository has had zero commits and zero active maintainers in the last three months, consistent with its last push being in January 2015. This leaves little evidence of current maintenance capacity.

Repository archivedcaution

The linked repository is not archived, which avoids an explicit repository shutdown signal. However, its last push was in January 2015, so the non-archived status does not compensate for the inactivity.

Security policycaution

The repository has no security policy. This is a transparency and reporting gap, although the package's broader inactivity and deprecation are more consequential.