are-we-there-yet

Registry deprecationdanger

The registry marks the entire package as deprecated with the message “This package is no longer supported,” which is a severe dependency-maintenance risk.

Release historydanger

The package has a long history and 21 releases, but its latest release was over two years ago and it had no releases in the last 12 months, reinforcing the abandonment concern.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months; combined with the archived repository and package deprecation, this indicates maintenance has stopped.

Repository archiveddanger

The linked repository is archived, so it is no longer an actively maintained source despite having been pushed in May 2024.

Workflow auditcaution

The audit completed successfully, but all 38 action references are unpinned and it found high-confidence template-injection issues in two workflows; these are meaningful maintenance and workflow-hygiene concerns, though no untrusted checkout or script-injection path was found.