Bump eslint-config-cityssm from 10.1.1 to 15.2.0

[dependabot]

Bumps eslint-config-cityssm from 10.1.1 to 15.2.0.

Release notes

Sourced from eslint-config-cityssm's releases.

v15.2.0

Highlights

• Updated eslint-config-love, eslint-plugin-jsdoc, and typescript-eslint.
• Reduced severity of @typescript-eslint/init-declarations to warn.

v15.1.0

Updated Plugins

• typescript-eslint
• cspell
• eslint-plugin-no-secrets
• eslint-plugin-n

Other Highlights

• Add to "write-good-comments" whitelist versions with first letter capitalized.
• Disable duplicated no-misused-promises rule.

v15.0.1

Disable eslint-comments/require-description.

v15.0.0

Updated Plugins

• eslint
• eslint-config-love
• cspell
• eslint-plugin-n

Other Highlights

• disable some redundant rules
• disable eslint-plugin-woke, add word list to cspell

v14.1.0

Highlights

• Updated typescript-eslint.
• Ignore magic number -1.
• Ignore unknown word ifnull.

v14.0.2

Ignore more web app words.

v14.0.1

Ignore more web app words.

v14.0.0

Highlights

... (truncated)

Commits

• 5e5d4d2 version bump
• 1101a56 update dependencies
• 20ddf18 reduce severity of init-declaration
• bb3625d boast about usage
• 515c2f8 version bump
• da90200 fix building whitelist
• 1a87081 generate the capitalized versions
• e4d8c77 update plugins
• c52f9e2 update dependencies
• 92d7732 disable duplicated rule
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	Transitive: environment, eval, filesystem, network, unsafe	+454	67.9 MB	dgowans

🚮 Removed packages: npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
GitHub dependency	npm/[email protected]	Dependency: eslint-plugin-woke@github:cityssm/eslint-plugin-woke Location: Package overview	package-lock.json package.json	⚠︎

View full report↗︎

Next steps

What are GitHub dependencies?

Contains a dependency which resolves to a GitHub URL. Dependencies fetched from GitHub specifiers are not immutable can be used to inject untrusted code or reduce the likelihood of a reproducible install.

Publish the GitHub dependency to npm or a private package repository and consume it from there.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]