chore(deps): bump qs from 6.15.0 to 6.15.2 in /docs by dependabot[bot] · Pull Request #12793 · noir-lang/noir

dependabot · 2026-05-26T09:52:24Z

Bumps qs from 6.15.0 to 6.15.2.

Changelog

6.15.2

[Fix] stringify: skip null/undefined entries in arrayFormat: 'comma' + encodeValuesOnly instead of crashing in encoder

[Fix] stringify: use configured delimiter after charsetSentinel (#555)

[Fix] stringify: apply formatter to encoded key under strictNullHandling (#554)

[Fix] stringify: skip null/undefined filter-array entries instead of crashing in encoder (#551)

[Fix] parse: handle nested bracket groups and add regression tests (#530)

[readme] fix grammar (#550)

[Dev Deps] update @ljharb/eslint-config

[Tests] add regression tests for keys containing percent-encoded bracket text

6.15.1

[Fix] parse: parameterLimit: Infinity with throwOnLimitExceeded: true silently drops all parameters

[Deps] update @ljharb/eslint-config

[Dev Deps] update @ljharb/eslint-config, iconv-lite

[Tests] increase coverage

Commits

9aca407 v6.15.2
5e33d33 [Dev Deps] update @ljharb/eslint-config
21f80b3 [Fix] stringify: skip null/undefined entries in arrayFormat: 'comma' + `e...
a0a81ea [Fix] stringify: use configured delimiter after charsetSentinel
e3062f7 [Fix] stringify: apply formatter to encoded key under strictNullHandling
0c180a4 [Fix] stringify: skip null/undefined filter-array entries instead of crashi...
3a8b94a [Tests] add regression tests for keys containing percent-encoded bracket text
96755ab [readme] fix grammar
a419ce5 [Fix] parse: handle nested bracket groups and add regression tests
3f5e1c5 v6.15.1
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [qs](https://github.com/ljharb/qs) from 6.15.0 to 6.15.2. - [Changelog](https://github.com/ljharb/qs/blob/main/CHANGELOG.md) - [Commits](ljharb/qs@v6.15.0...v6.15.2) --- updated-dependencies: - dependency-name: qs dependency-version: 6.15.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>

socket-security · 2026-05-26T09:53:10Z

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance
	ethers@6.16.0
	webpack@5.102.0 ⏵ 5.106.2	^-10	⁺²	⁺¹	⁺³
	browserify-fs@1.0.0
	@ltd/j-toml@1.38.0
	@web/test-runner-playwright@0.11.1
	@typescript-eslint/parser@8.58.0
	@types/path-browserify@1.0.3
	@types/pako@2.0.4
	@web/dev-server-import-maps@0.2.1
	@web/dev-server-esbuild@1.0.5
	@types/readable-stream@4.0.23
	@types/adm-zip@0.5.8
	buffer-esm@1.2.0
	mocha-each@2.0.1
	path-browserify@1.0.1
	process@0.11.10
	@types/mocha-each@2.0.4
	@types/sinon@21.0.1
	@types/chai@5.2.3
	@nomicfoundation/hardhat-toolbox-mocha-ethers@3.0.5
	@types/mocha@10.0.10
	@nomicfoundation/hardhat-node-test-runner@3.0.15
	@nomicfoundation/hardhat-typechain@3.0.9
	esbuild-register@3.6.0
	tsc-multi@1.1.0
	pako@1.0.11 ⏵ 2.1.0	^-1
	ts-command-line-args@2.5.1
	@typescript-eslint/eslint-plugin@8.58.0
	tsx@4.21.0
	@types/node@24.6.1 ⏵ 22.19.19
	@nomicfoundation/hardhat-keystore@3.0.9
	@nomicfoundation/hardhat-ignition@3.1.5
	@esm-bundle/chai@4.3.4
See 33 more rows in the dashboard

View full report

socket-security · 2026-05-26T09:53:12Z

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		Obfuscated code: npm `@humanwhocodes/retry` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/eslint@10.3.0` → `npm/@humanwhocodes/retry@0.4.2` ℹ Read more on: This package \| This alert \| What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@humanwhocodes/retry@0.4.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		Obfuscated code: npm `@typescript-eslint/eslint-plugin` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package.json → `npm/@typescript-eslint/eslint-plugin@8.58.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@typescript-eslint/eslint-plugin@8.58.0`. 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		Obfuscated code: npm `es-module-lexer` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/webpack@5.106.2` → `npm/es-module-lexer@2.0.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/es-module-lexer@2.0.0`. 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		Obfuscated code: npm `es-module-lexer` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/webpack@5.106.2` → `npm/es-module-lexer@2.0.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/es-module-lexer@2.0.0`. 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		Obfuscated code: npm `json-stream-stringify` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/@nomicfoundation/hardhat-ethers@4.0.11` → `npm/hardhat@3.4.5` → `npm/@nomicfoundation/hardhat-mocha@3.0.19` → `npm/@nomicfoundation/hardhat-keystore@3.0.9` → `npm/@nomicfoundation/hardhat-ignition@3.1.5` → `npm/@nomicfoundation/hardhat-network-helpers@3.0.8` → `npm/@nomicfoundation/hardhat-ignition-ethers@3.1.5` → `npm/@nomicfoundation/hardhat-verify@3.0.17` → `npm/@nomicfoundation/hardhat-node-test-runner@3.0.15` → `npm/@nomicfoundation/hardhat-typechain@3.0.9` → `npm/@nomicfoundation/hardhat-ethers-chai-matchers@3.0.8` → `npm/json-stream-stringify@3.1.6` ℹ Read more on: This package \| This alert \| What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/json-stream-stringify@3.1.6`. 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		Obfuscated code: npm `playwright-core` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/@playwright/test@1.58.2` → `npm/@web/test-runner-playwright@0.11.1` → `npm/playwright-core@1.58.2` ℹ Read more on: This package \| This alert \| What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/playwright-core@1.58.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		Obfuscated code: npm `rimraf` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/eslint@10.3.0` → `npm/rimraf@5.0.5` ℹ Read more on: This package \| This alert \| What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/rimraf@5.0.5`. 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		Obfuscated code: npm `tar` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/@playwright/test@1.58.2` → `npm/vite@8.0.10` → `npm/webpack-dev-server@5.2.4` → `npm/@aztec/bb.js@5.0.0-nightly.20260522` → `npm/@web/test-runner@0.20.2` → `npm/@web/test-runner-playwright@0.11.1` → `npm/tsx@4.21.0` → `npm/tar@7.5.13` ℹ Read more on: This package \| This alert \| What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/tar@7.5.13`. 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		Obfuscated code: npm `webpack` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: compiler/wasm/package.json → `npm/webpack@5.106.2` ℹ Read more on: This package \| This alert \| What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/webpack@5.106.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

github-actions

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Elaboration Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: `b02c85c`	Previous: `be64e1e`	Ratio
`private-kernel-inner`	`1.148` s	`0.704` s	`1.63`
`semaphore-depth-10`	`0.241` s	`0.192` s	`1.26`

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench

github-actions

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Brillig Compilation Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: `b02c85c`	Previous: `be64e1e`	Ratio
`private-kernel-inner`	`1.77` s	`1.088` s	`1.63`
`semaphore-depth-10`	`0.374` s	`0.296` s	`1.26`

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench

github-actions

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Execution Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: `b02c85c`	Previous: `be64e1e`	Ratio
`private-kernel-inner`	`0.039` s	`0.021` s	`1.86`
`rollup-block-root`	`0.005` s	`0.004` s	`1.25`

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench

github-actions

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Compilation Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: `b02c85c`	Previous: `be64e1e`	Ratio
`private-kernel-inner`	`7.748` s	`4.504` s	`1.72`
`semaphore-depth-10`	`1.21` s	`1.005` s	`1.20`

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench

github-actions

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Test Suite Duration'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: `b02c85c`	Previous: `1d07ff4`	Ratio
`test_report_zkpassport_noir_rsa_`	`2` s	`1` s	`2`

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench

github-actions

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Brillig Execution Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: `b02c85c`	Previous: `be64e1e`	Ratio
`private-kernel-inner`	`0.031` s	`0.015` s	`2.07`
`semaphore-depth-10`	`0.008` s	`0.006` s	`1.33`

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench

dependabot Bot added dependencies Updates or changes Noir's dependencies javascript Pull requests that update javascript code labels May 26, 2026

github-actions Bot added the documentation Improvements or additions to documentation label May 26, 2026

github-actions Bot reviewed May 26, 2026

View reviewed changes

TomAFrench approved these changes May 26, 2026

View reviewed changes

TomAFrench added this pull request to the merge queue May 26, 2026

github-merge-queue Bot removed this pull request from the merge queue due to no response for status checks May 26, 2026

TomAFrench added this pull request to the merge queue May 26, 2026

Merged via the queue into master with commit e5e4436 May 26, 2026
132 checks passed

TomAFrench deleted the dependabot/npm_and_yarn/docs/qs-6.15.2 branch May 26, 2026 13:18

Navigation Menu

Uh oh!

chore(deps): bump qs from 6.15.0 to 6.15.2 in /docs - #12793

chore(deps): bump qs from 6.15.0 to 6.15.2 in /docs#12793
TomAFrench merged 1 commit into
masterfrom
dependabot/npm_and_yarn/docs/qs-6.15.2

dependabot Bot commented on behalf of github May 26, 2026

Uh oh!

socket-security Bot commented May 26, 2026

Uh oh!

socket-security Bot commented May 26, 2026

Uh oh!

github-actions Bot left a comment

Uh oh!

github-actions Bot left a comment

Uh oh!

github-actions Bot left a comment

Uh oh!

github-actions Bot left a comment

Uh oh!

github-actions Bot left a comment

Uh oh!

github-actions Bot left a comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

dependabot Bot commented on behalf of github May 26, 2026

6.15.2

6.15.1

Uh oh!

socket-security Bot commented May 26, 2026

Uh oh!

socket-security Bot commented May 26, 2026

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

⚠️ Performance Alert ⚠️

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

⚠️ Performance Alert ⚠️

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

⚠️ Performance Alert ⚠️

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

⚠️ Performance Alert ⚠️

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

⚠️ Performance Alert ⚠️

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

⚠️ Performance Alert ⚠️

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant