npm run build:bindings reports 1 high vuln and 1 moderate vuln via node

[Fizzixnerd]

Unsure if they have been triaged, but adding this issue in case they haven't. I can't find anything by searching "vuln" in previous issues.

Ideally this would not display.

fizzixnerd@o1-walkerbook:~/src/o1js$ npm run build:bindings

> [email protected] build:bindings
> ./src/bindings/scripts/build-o1js-node.sh

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=20' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '10.2.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=20' },
npm WARN EBADENGINE   current: { node: 'v18.19.1', npm: '10.2.4' }
npm WARN EBADENGINE }

added 586 packages, and audited 587 packages in 4s

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

2 vulnerabilities (1 moderate, 1 high)

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
Checking if jemalloc is available... Yes, using jemalloc as an allocator
[INFO]: 🎯  Checking for the Wasm target...
[INFO]: 🌀  Compiling to Wasm...
warning: unused manifest key: build
... <SNIP> ...

PS let me know if I'm misusing any of the tags I've been using.