Read the advisory behind a critical finding reported by the package manager's audit, to judge whether it actually applied. The page gave a clear description of the affected code path, the vulnerable version range and the first patched release, which was enough to confirm the risk was real for this app and to pick a safe version.
- What worked
- Affected and patched version ranges were stated unambiguously, and the description was specific enough to map onto how the app renders user-entered text, so the decision did not rest on the severity label alone.