Bump eslint-config-cityssm from 38.1.0 to 38.2.1

[dependabot]

Bumps eslint-config-cityssm from 38.1.0 to 38.2.1.

Release notes

Sourced from eslint-config-cityssm's releases.

v38.2.1

Fixes some of the recently identified vulnerabilities.

Plugin Updates

• eslint
• eslint-plugin-jsdoc
• eslint-plugin-security

Full Changelog: cityssm/eslint-config-cityssm@v38.2.0...v38.2.1

v38.2.0

Vulnerabilities in dependencies of html-eslint and eslint, but not a major risk.

Cannot update to eslint 10 yet. Wating on eslint-config-love and cspell to support.

Plugin Updates

• eslint/json
• html-eslint
• eslint-config-love
• eslint-plugin-jsdoc
• eslint-plugin-n
• eslint-plugin-no-unsanitized
• eslint-plugin-package-json
• eslint-plugin-perfectionist
• eslint-plugin-sonarjs
• typescript-eslint

Full Changelog: cityssm/eslint-config-cityssm@v38.1.0...v38.2.0

Commits

• c984966 version bump
• a723256 update jsdoc and security plugins
• 0f29d63 update eslint
• 3d79c71 plugin updates, bump to 38.2.0
• 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)

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	eslint-config-cityssm@​38.1.0 ⏵ 38.2.1	+7			+1

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		Obfuscated code: npm @html-eslint/eslint-plugin is 98.0% likely obfuscated Confidence: 0.98 Location: Package overview From: package-lock.json → npm/eslint-config-cityssm@38.2.1 → npm/@html-eslint/eslint-plugin@0.55.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/@html-eslint/eslint-plugin@0.55.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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[deepsource-io]

DeepSource Code Review

DeepSource reviewed changes in the commit range afa806a...6fba49b on this pull request. Below is the summary for the review, and you can see the individual issues we found as review comments.

For detailed review results, please see the PR on DeepSource ↗

PR Report Card

Security	× 6 issues		Overall PR Quality
Reliability	× 0 issues
Complexity	× 0 issues
Hygiene	× 0 issues

Code Review Summary

Analyzer	Status	Summary	Details
JavaScript		No new issues detected.	Review ↗

How are these analyzer statuses calculated?

Administrators can configure which issue categories are reported and cause analysis to be marked as failed when detected. This helps prevent bad and insecure code from being introduced in the codebase. If you're an administrator, you can modify this in the repository's settings.