unzip-response

Registry deprecationdanger

The entire package is deprecated with the message “Renamed to decompress-response,” making this release unsuitable for a new dependency despite otherwise healthy metadata.

Release historydanger

The package has had no release in over nine years, with the latest registry release in May 2017. That strongly raises abandonment and compatibility risk.

Repo commit activitycaution

There were no commits or active maintainers in the three months measured, indicating little recent development activity even though the repository remains available.

Workflow auditcaution

The single workflow was fully analyzed with no audit findings or untrusted checkout and script-injection paths. However, both action references are unpinned, which is a modest workflow hygiene gap.