(node:10154) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.

Open
#3,350 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, node.js, typescript
Domain
ci-cd, security

Research direction

Start with the GitHub Actions run and the codeql-action@v4 post-processing step that validates SARIF files. No source file or test is identified in the issue, so trace that entry point to find where the deprecated url.parse() call originates. Done means the warning no longer appears during SARIF post-processing and the action still completes its validation.

Written by the indexing model from the issue text.

Description

https://github.com/check-spelling-sandbox/rancher-desktop/actions/runs/20089313767/job/57633334730#step:7:27

Download action repository 'github/codeql-action@v4' (SHA:cf1bb45a277cb3c205638b2cd5c984db1c46a412)

Post-processing sarif files: ["/tmp/tmp.sDnlfIczKq"]
Validating /tmp/tmp.sDnlfIczKq
Adding fingerprints to SARIF file. See https://docs.github.com/en/enterprise-cloud@latest/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#providing-data-to-track-code-scanning-alerts-across-runs for more information.
(node:10154) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
Dominant language
TypeScript
Stars
1.6k
Forks
493
Avg merge
1d 13h
Merged PRs (30d)
44

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/codeql-action

All issues in github/codeql-action

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.