Skip to content

🚨 [security] Update @vue/eslint-config-typescript 14.6.0 → 14.8.0 (minor)#239

Open
depfu[bot] wants to merge 1 commit into
mainfrom
depfu-update-npm-vue-eslint-config-typescript-14.8.0
Open

🚨 [security] Update @vue/eslint-config-typescript 14.6.0 → 14.8.0 (minor)#239
depfu[bot] wants to merge 1 commit into
mainfrom
depfu-update-npm-vue-eslint-config-typescript-14.8.0

Conversation

@depfu

@depfu depfu Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!


Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​vue/eslint-config-typescript (14.6.0 → 14.8.0) · Repo

Release Notes

14.8.0

What's Changed

New Contributors

Full Changelog: v14.7.0...v14.8.0

14.7.0

What's Changed

  • fix: respect global ignores when scanning for vue files to lint by @haoqunjiang in #239
  • feat: support ESLint 10 as peer dependency

Full Changelog: v14.6.0...v14.7.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ debug (indirect, 4.4.1 → 4.4.3) · Repo · Changelog

Security Advisories 🚨

🚨 debug@4.4.2 contains malware after npm account takeover

Impact

On 8 September 2025, the npm publishing account for debug was taken over after a phishing attack. Version 4.4.2 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments.

Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt.

The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload.

Patches

npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper.

On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. This version is functionally identical to the previously known-good version, published as a patch version bump above the compromised version.

Users should upgrade to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch.

Those operating private registries or registry mirrors should purge the offending versions from any caches.

References

Point of Contact

In the event suspicious behavior is still observed for the package listed in this security advisory after performing all of the above cleaning operations (see Patches above), please reach out via one of the following channels of communication:

Release Notes

4.4.3

Functionally identical release to 4.4.1.

Version 4.4.2 is compromised. Please see #1005.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 1 commit:

↗️ semver (indirect, 7.7.2 → 7.8.4) · Repo · Changelog

Release Notes

7.8.4

7.8.4 (2026-06-09)

Bug Fixes

7.8.3

7.8.3 (2026-06-08)

Bug Fixes

Chores

7.8.2

7.8.2 (2026-06-04)

Bug Fixes

7.8.1

7.8.1 (2026-05-21)

Bug Fixes

7.8.0

7.8.0 (2026-05-08)

Features

Bug Fixes

Documentation

Chores

7.7.4

7.7.4 (2026-01-16)

Bug Fixes

Documentation

Dependencies

Chores

7.7.3

7.7.3 (2025-10-06)

Bug Fixes

Chores

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 34 commits:

↗️ typescript-eslint (indirect, 8.41.0 → 8.61.0) · Repo · Changelog

Release Notes

8.61.0

8.61.0 (2026-06-08)

🚀 Features

  • ast-spec: change type of UnaryExpression.prefix to always true (#12372)
  • ast-spec: tighten types of ArrowFunction, YieldExpression, TSTypePredicate (#12373)

🩹 Fixes

  • rule-schema-to-typescript-types: respect ECMAScript line terminators (#12374)

❤️ Thank You

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

8.60.1

8.60.1 (2026-06-01)

🩹 Fixes

  • eslint-plugin: respect ECMAScript line terminators in ts-comment rules (#12352)
  • eslint-plugin: [no-shadow] correct rule to match ESLint v10 handling (#12182)

❤️ Thank You

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

8.60.0

8.60.0 (2026-05-25)

🚀 Features

  • rule-tester: added updates of RuleTester from upstream (#12291)

🩹 Fixes

  • playground TS version selector is not working (#12326, #12325)

❤️ Thank You

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

8.59.4

8.59.4 (2026-05-18)

🩹 Fixes

  • eslint-plugin: [no-floating-promises] stack overflow when using recursive types (#12294)
  • project-service: throw error cause in getParsedConfigFileFromTSServer (#12321)
  • typescript-eslint: export Compatible* types from typescript-eslint to resolve pnpm TS error (#12340)

❤️ Thank You

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ vue-eslint-parser (indirect, 10.2.0 → 10.4.1) · Repo

Release Notes

10.4.1

🐛 Bug Fixes

  • fix: compatibility with @babel/eslint-parser v8 by @JounQin in #294

Full Changelog: v10.4.0...v10.4.1

10.4.0

⚙️ Changes

  • feat: updated scope analyzer to mark variables as used to prevent false positives with no-useless-assignment by @ota-meshi in #288

Full Changelog: v10.3.0...v10.4.0

10.3.0

✨ Enhancements

⚙️ Infrastructure Updates

Full Changelog: v10.2.0...v10.3.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 23 commits:

🆕 brace-expansion (added, 5.0.6)

🆕 minimatch (added, 10.2.5)

🆕 @​typescript-eslint/eslint-plugin (added, 8.61.0)

🆕 @​typescript-eslint/project-service (added, 8.61.0)

🆕 @​typescript-eslint/scope-manager (added, 8.61.0)

🆕 @​typescript-eslint/tsconfig-utils (added, 8.61.0)

🆕 @​typescript-eslint/types (added, 8.61.0)

🆕 @​typescript-eslint/typescript-estree (added, 8.61.0)

🆕 @​typescript-eslint/utils (added, 8.61.0)

🆕 @​typescript-eslint/visitor-keys (added, 8.61.0)

🆕 eslint-visitor-keys (added, 5.0.1)

🆕 @​typescript-eslint/parser (added, 8.61.0)

🆕 @​typescript-eslint/type-utils (added, 8.61.0)

🆕 balanced-match (added, 4.0.4)

🗑️ graphemer (removed)

🗑️ @​typescript-eslint/eslint-plugin (removed)

🗑️ @​typescript-eslint/eslint-plugin (removed)

🗑️ @​typescript-eslint/project-service (removed)

🗑️ @​typescript-eslint/project-service (removed)

🗑️ @​typescript-eslint/scope-manager (removed)

🗑️ @​typescript-eslint/scope-manager (removed)

🗑️ @​typescript-eslint/tsconfig-utils (removed)

🗑️ @​typescript-eslint/tsconfig-utils (removed)

🗑️ @​typescript-eslint/types (removed)

🗑️ @​typescript-eslint/types (removed)

🗑️ @​typescript-eslint/typescript-estree (removed)

🗑️ @​typescript-eslint/typescript-estree (removed)

🗑️ @​typescript-eslint/utils (removed)

🗑️ @​typescript-eslint/utils (removed)

🗑️ @​typescript-eslint/visitor-keys (removed)

🗑️ @​typescript-eslint/visitor-keys (removed)

🗑️ @​typescript-eslint/parser (removed)

🗑️ @​typescript-eslint/parser (removed)

🗑️ @​typescript-eslint/type-utils (removed)

🗑️ @​typescript-eslint/type-utils (removed)


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Only updates dependecies depfu

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant