spiffy/spiffy-authorize

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement named. Package-wide deprecation is a severe adoption risk even though the specific release is not separately withdrawn.

Release historydanger

The package has only two releases, and the latest was published about 12 years ago; there have been no releases in the last 12 months. This strongly indicates abandonment.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, with its last push in 2014. That confirms the long release gap is not merely a registry publishing gap.

Licensecaution

Neither the package metadata nor the repository contains a recognized license or license file. That creates a real legal and adoption risk for a dependency.

Repo toolingcaution

The repository uses Composer, but no security-scanning tooling is reported. This is a modest hygiene gap and does not outweigh the package's abandonment evidence.