Speccy uses dompurify with XSS vulnerability

Thought I would bring this up here as [Speccy ](https://github.com/wework/speccy) is a dead repo (last updated 3 years ago). It looks like Speccy is being used here and the latest version of Speccy is using an older version of [redoc](https://github.com/wework/speccy/blob/master/package-lock.json#L6443) which is using a [bad version](https://github.com/wework/speccy/blob/master/package-lock.json#L6450) of dompurify according to [snyk ](https://snyk.io/vuln/npm:dompurify).

Wondering what are thoughts around removing speccy from the repo?

Start by tracing where Speccy is used in this repository, then inspect the Speccy package-lock.json entries at lines 6443 and 6450 and the linked Snyk advisory. Confirm whether removing Speccy affects existing OpenAPI workflows; done means the vulnerable dependency is no longer part of the repository without breaking those workflows.

Written by the indexing model from the issue text.