[Snyk] Security upgrade mocha from 8.3.2 to 9.1.2

[ekmixon]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • js/node/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	696/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 7.5	Regular Expression Denial of Service (ReDoS) SNYK-JS-ANSIREGEX-1583908	Yes	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: mocha

The new version differs by 64 commits.

• 18a1055 build(v9.1.2): release
• 011a5a4 fix: regex in 'update-authors.js'
• 06f3f63 build(v9.1.2): update CHANGELOG [ci skip]
• a87461c chore(deps): remove 'wide-align' (Segmentation Fault when trying to run my own custom op with default EP. microsoft/onnxruntime#4754)
• c7f56d1 docs: how to use 'rootHooks' in the browser (ONNXRuntime JAVA JNI build failure  microsoft/onnxruntime#4755) [ci skip]
• 8421974 fix(browser): stop using all global vars in 'browser-entry' (Wezuo/zero stage2 prototype microsoft/onnxruntime#4746)
• 27bfc74 docs: add complete '--delay' example (Fix for mainz model microsoft/onnxruntime#4744) [ci skip]
• 4860738 chore(devDeps): update 'eslint' and its plugins (Yanchen/nuphar/clip 11 microsoft/onnxruntime#4737)
• abfddf8 docs: fix broken table width under 450 screen width (Remove docstring for removed parameter microsoft/onnxruntime#4734)
• 97b8470 chore(esm): remove code for Node versions <10 (Add Experimental WinRT API IDL as placeholder for adding new winrt features microsoft/onnxruntime#4736)
• 654b5df build(v9.1.1): release
• a26cca9 build(v9.1.1): update CHANGELOG [ci skip]
• e975675 chore: update some devDependencies (C# samples: Faster R-CNN microsoft/onnxruntime#4733)
• 9e0369b fix(parallel): 'XUNIT' and 'JSON' reporter crash (Test failure on Windows microsoft/onnxruntime#4623)
• 014e47a build(v9.1.0): release
• 3a14b28 build(v9.1.0): update CHANGELOG [ci skip]
• 171e211 feat(reporter): add output option to 'JSON' ([Android NNAPI EP] Add QLinearAdd op Support, move some throw with return status microsoft/onnxruntime#4607)
• bbf0c11 feat: add new option 'fail-zero' (Add Debuggability to Check Model Weights microsoft/onnxruntime#4716)
• 757b85d docs: improve 'grep()' and clarify docs (Added explicit instructions to build for Jetson microsoft/onnxruntime#4714)
• f19d3ca docs: remove unsupported 'no-timeout' option (Support log sigmoid gradient microsoft/onnxruntime#4719) [ci skip]
• 9f82ccb chore(gha): update 'stale.yml' (Add a generic collection of session configurations to the SessionOptions microsoft/onnxruntime#4718) [ci skip]
• 09ffc30 Set CSP on karma to prevent 'evalError' regression (Remove the requirement of reading CUDA's version.txt in CI microsoft/onnxruntime#4706)
• 02bf13d Update devDep '@ babel/preset-env' and pin 'regenerator-runtime' (Can't export GPT2-XL to ONNX: ModelProto exceeds maximum protobuf size of 2GB microsoft/onnxruntime#4707)
• 54a5788 Add new option "node-option" ([Nuphar] added Gemm-to-MatMul conversion in model editor microsoft/onnxruntime#4691)

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.