[Snyk] Fix for 1 vulnerabilities

[snyk-rfrazier]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-14724253	170

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[snyk-rfrazier]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[snyk-rfrazier]

This set of upgrades carries a high risk, driven primarily by the major version jump for the tap testing framework from v11 to v18.

• tap (11.1.5 → 18.0.0): This is a significant upgrade with numerous breaking changes. Key changes include:

  • Node.js Support: Support for Node.js versions below 12 has been dropped. [7]
  • Coverage Enforcement: Test coverage is now enabled by default and fails if 100% coverage is not met. [9]
  • Configuration: File matching now uses include/exclude globs instead of test-regex. [9]
  • API Changes: Assertion aliases (e.g., t.similar) have been removed and moved to an optional @tapjs/synonyms plugin. [9]

• body-parser (1.9.0 → 1.20.4): While a minor upgrade, its usage is now deprecated. Since Express v4.16.0, body parsing is built-in. [2, 5] It is recommended to remove the body-parser dependency and use express.json() and express.urlencoded() instead. [2]

• express (4.12.4 → 4.22.0): This is a low-risk minor version upgrade with no significant breaking changes cited. [11]

Recommendation: The tap upgrade will require significant refactoring of test configurations and potentially test code. This should be addressed carefully before merging.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.