Prototype Pollution in JSON5 via Parse Method - https://github.com/advisories/GHSA-9c47-m6qq-7p4h fix available via `npm audit fix`

[BaseMax]

C:\Users\Max\react-native-decompiler>npm i && ts-node ./src/main.ts

up to date, audited 780 packages in 10s

96 packages are looking for funding
  run `npm fund` for details

2 high severity vulnerabilities

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
'ts-node' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Max\react-native-decompiler>ts-node
'ts-node' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Max\react-native-decompiler>npm i ts-node

up to date, audited 780 packages in 5s

96 packages are looking for funding
  run `npm fund` for details

2 high severity vulnerabilities

To address all issues, run:
  npm audit fix

Run `npm audit` for details.

C:\Users\Max\react-native-decompiler>ts-node
'ts-node' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Max\react-native-decompiler>npm audit fix

up to date, audited 780 packages in 4s

96 packages are looking for funding
  run `npm fund` for details

# npm audit report

json5  <2.2.2
Severity: high
Prototype Pollution in JSON5 via Parse Method - https://github.com/advisories/GHSA-9c47-m6qq-7p4h
fix available via `npm audit fix`
node_modules/tsconfig-paths/node_modules/json5
  tsconfig-paths  3.5.0 - 3.9.0 || 3.11.0 - 3.14.1
  Depends on vulnerable versions of json5
  node_modules/tsconfig-paths

2 high severity vulnerabilities

To address all issues, run:
  npm audit fix