gherkin

Registry deprecationdanger

The entire package is deprecated, with the registry directing users to @cucumber/gherkin. This is a direct adoption blocker even though the assessed version is stable.

Release historydanger

The package has 98 releases and a long history, but its latest release was in December 2019 and it had no releases in the last 12 months. That is a strong abandonment signal for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the archived state and lack of ongoing maintenance.

Repository archiveddanger

The linked repository is archived, indicating the project is no longer actively maintained; its last push was in November 2022.

Build provenancecaution

No build provenance attestation or trusted publisher information is present, reducing publication transparency. This is a secondary concern because the package is already deprecated and archived.