Package `yaml` can be updated to security patched version >= 2.2.2
envgap__lint-staged__lint-staged-1291
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- In a clean container the reported failure did not reproduce, or the known fix did not make the project run.
02 / ENVIRONMENT RECIPE
- Base commit
e7ed6f741d2ea0f084b06f3e1ac3d1d57fadf737- Manifest
package.json- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
lint-staged/lint-staged #1291 · read the original issue
### Description Currently we are [using](https://github.com/okonet/lint-staged/blob/master/package.json#L48) `yaml@^2.2.1` version. This security bug [Uncaught Exception in yaml](https://github.com/advisories/GHSA-f9xv-q969-pqx4) is fixed and [released](https://github.com/eemeli/yaml/releases/tag/v2.2.2) in `V2.2.2` So we can include the updated package in our code as well.
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]