chore(deps-dev): bump ip-address from 10.0.1 to 10.2.0

[dependabot]

Bumps ip-address from 10.0.1 to 10.2.0.

Commits

• See full diff 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.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​puppeteer@​24.26.1 ⏵ 22.15.0	+1		+2	-46
	npm/​node-forge@​1.3.3
	npm/​pdfassembler@​0.1.0-beta.8
	npm/​jest@​29.7.0
	npm/​lightningcss@​1.30.2 ⏵ 1.31.1	+1		+1
	npm/​@​signpdf/​signer-p12@​3.3.0
	npm/​pdf-rfc3161@​0.1.4
	npm/​@​pdfsmaller/​pdf-encrypt@​1.0.2
	npm/​@​types/​node-forge@​1.3.14
	npm/​@​types/​jest@​29.5.14
	npm/​bun@​1.3.2
	npm/​@​signpdf/​signpdf@​3.3.0
	npm/​@​types/​node@​20.19.22 ⏵ 20.19.23	+1		+1
	npm/​@​types/​node@​20.19.22 ⏵ 20.19.24	+1		+1
	npm/​tsx@​4.20.6 ⏵ 4.21.0
	npm/​@​signpdf/​placeholder-plain@​3.3.0
	npm/​chalk@​5.6.2 ⏵ 4.1.2
	npm/​ora@​8.2.0 ⏵ 5.4.1	+1
	npm/​ajv@​8.18.0 ⏵ 8.17.1	+1	-1
	npm/​typescript@​5.9.3
	npm/​ts-jest@​29.4.5
	npm/​tsdown@​0.16.0
	npm/​@​aws-sdk/​client-s3@​3.1000.0
	npm/​@​aws-sdk/​s3-request-presigner@​3.1000.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 crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard CVE: GHSA-xwcq-pm8m-c4vf crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard (CRITICAL) Affected versions: < 4.2.0 Patched version: 4.2.0 From: cli/package-lock.json → npm/@signpdf/placeholder-plain@3.3.0 → npm/crypto-js@3.3.0 ℹ 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/crypto-js@3.3.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		Critical CVE: Handlebars.js has JavaScript Injection via AST Type Confusion CVE: GHSA-2w6w-674q-4c4q Handlebars.js has JavaScript Injection via AST Type Confusion (CRITICAL) Affected versions: >= 4.0.0 < 4.7.9 Patched version: 4.7.9 From: cli/package-lock.json → npm/ts-jest@29.4.5 → npm/handlebars@4.7.8 ℹ 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/handlebars@4.7.8. 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 pdfkit is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: cli/package-lock.json → npm/@signpdf/placeholder-plain@3.3.0 → npm/pdfkit@0.10.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/pdfkit@0.10.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 pdfkit is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: cli/package-lock.json → npm/@signpdf/placeholder-plain@3.3.0 → npm/pdfkit@0.10.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/pdfkit@0.10.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.

View full report