[Snyk] Upgrade @sectester/core from 0.16.5 to 0.50.0

[TheRedHatter]

Snyk has created this PR to upgrade @sectester/core from 0.16.5 to 0.50.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 57 versions ahead of your current version.

• The recommended version was released a month ago.

Release notes

Package name: @sectester/core

• 0.50.0 - 2026-03-17
  

  0.50.0 (2026-03-17)

  Features

  • reporter: introduce bitbucket reporter (#289) (03e58e1)
• 0.49.0 - 2026-01-22
  

  0.49.0 (2026-01-22)

  Features

  • repeater: handle limits event (#279) (d2569c2)
• 0.48.1 - 2026-01-22
  

  0.48.1 (2026-01-22)

  Bug Fixes

  • repeater: update timeout error handling to include ETIMEDOUT code (#277) (4ccf972)
• 0.48.0 - 2026-01-21
  

  0.48.0 (2026-01-21)

  Features

  • scan: add ability to run broken access control test with required options (#270) (a2876c9)
• 0.47.0 - 2025-09-15
  

  0.47.0 (2025-09-15)

  Features

  • reporter: add support for GitLab JUnit test report (#265) (159c743)
• 0.46.0 - 2025-09-10
  

  0.46.0 (2025-09-10)

  Features

  • reporter: add code quality reporter (#264) (7755425)
• 0.45.0 - 2025-07-09
  

  0.45.0 (2025-07-09)

  Features

  • scan: add star metadata (#259) (3f1f1c3)
• 0.44.0 - 2025-07-02
  

  0.44.0 (2025-07-02)

  Features

  • runner: allow configuring fail-fast behavior (#258) (427749a)
• 0.43.2 - 2025-05-31
  

  0.43.2 (2025-05-31)

  Bug Fixes

  • repeater: ensure repeater is deployed on connect (#257) (aaf4cfa)
• 0.43.1 - 2025-05-31
  

  0.43.1 (2025-05-31)

  Bug Fixes

  • scan: handling conflict on errors (#256) (0b1838b)
• 0.41.1 - 2025-04-17
• 0.41.0 - 2025-04-16
• 0.40.2 - 2025-04-10
• 0.40.1 - 2025-03-24
• 0.40.0 - 2025-03-24
• 0.39.0 - 2025-03-05
• 0.38.0 - 2025-03-02
• 0.37.2 - 2025-03-02
• 0.37.1 - 2025-03-02
• 0.37.0 - 2025-03-01
• 0.36.2 - 2025-02-28
• 0.36.1 - 2025-02-28
• 0.36.0 - 2025-02-18
• 0.35.3 - 2025-02-17
• 0.35.2 - 2025-02-17
• 0.35.1 - 2025-02-15
• 0.35.0 - 2025-01-24
• 0.34.0 - 2025-01-23
• 0.33.3 - 2024-10-21
• 0.33.1 - 2024-07-13
• 0.33.0 - 2024-07-12
• 0.32.0 - 2024-07-12
• 0.31.0 - 2024-07-09
• 0.30.0 - 2024-07-05
• 0.29.1 - 2024-06-22
• 0.29.0 - 2024-06-20
• 0.28.0 - 2024-06-19
• 0.27.0 - 2023-08-03
• 0.26.0 - 2023-07-31
• 0.25.0 - 2023-07-28
• 0.24.1 - 2023-07-20
• 0.24.0 - 2023-07-20
• 0.23.2 - 2023-06-27
• 0.23.1 - 2023-06-19
• 0.23.0 - 2023-06-18
• 0.22.0 - 2023-06-17
• 0.21.0 - 2023-06-17
• 0.20.2 - 2023-06-16
• 0.20.1 - 2023-06-12
• 0.20.0 - 2023-06-05
• 0.19.3 - 2023-06-05
• 0.19.2 - 2023-06-05
• 0.19.1 - 2023-05-24
• 0.19.0 - 2023-05-23
• 0.18.1 - 2023-05-02
• 0.18.0 - 2023-03-16
• 0.17.0 - 2023-02-09
• 0.16.5 - 2022-10-28

from @sectester/core GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• 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 upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[TheRedHatter]

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

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	jest@​26.6.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: npm pbkdf2 returns predictable uninitialized/zero-filled memory for non-normalized or unimplemented algos CVE: GHSA-h7cp-r72f-jxh6 pbkdf2 returns predictable uninitialized/zero-filled memory for non-normalized or unimplemented algos (CRITICAL) Affected versions: >= 3.0.10 < 3.1.3 Patched version: 3.1.3 From: public/package-lock.json → npm/pbkdf2@3.1.2 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/pbkdf2@3.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Critical CVE: npm pbkdf2 silently disregards Uint8Array input, returning static keys CVE: GHSA-v62p-rq8g-8h59 pbkdf2 silently disregards Uint8Array input, returning static keys (CRITICAL) Affected versions: >= 1.0.0 < 3.1.3 Patched version: 3.1.3 From: public/package-lock.json → npm/pbkdf2@3.1.2 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/pbkdf2@3.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[TheRedHatter]

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

Status	Scan Engine	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.