Skip to content

chore(deps): lock file maintenance#1906

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance
Open

chore(deps): lock file maintenance#1906
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Nov 1, 2021

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 4am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Nov 1, 2021
@netlify
Copy link
Copy Markdown

netlify Bot commented Nov 1, 2021

Deploy Preview for nuxt failed. Why did it fail? →

Name Link
🔨 Latest commit 3cd41ca
🔍 Latest deploy log https://app.netlify.com/projects/nuxt/deploys/6a033308bb7a1a0008e70975

@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 26416e8 to a25ebbf Compare January 28, 2022 16:00
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from a25ebbf to f23b4c7 Compare March 12, 2022 22:01
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from 08bb48b to 8682fd6 Compare December 15, 2022 15:25
@renovate renovate Bot changed the title chore(deps): lock file maintenance Lock file maintenance Dec 17, 2022
@renovate renovate Bot changed the title Lock file maintenance chore(deps): lock file maintenance Dec 17, 2022
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from 060168b to 40a004e Compare April 4, 2024 08:17
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 9ddf1e3 to bc637ea Compare August 13, 2025 12:48
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from bc637ea to bea6d1f Compare August 19, 2025 11:38
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from bea6d1f to b824389 Compare August 31, 2025 12:03
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from b824389 to 9fbd56c Compare September 25, 2025 17:27
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 9fbd56c to d16106f Compare October 21, 2025 19:51
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from d16106f to 9f7c47e Compare November 10, 2025 22:47
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 9f7c47e to 9785117 Compare November 18, 2025 13:48
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 9785117 to 8a95167 Compare December 3, 2025 16:36
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 8a95167 to 86acd04 Compare December 31, 2025 18:41
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 86acd04 to 240d915 Compare January 8, 2026 20:50
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from ecae70f to 2833d9d Compare January 23, 2026 21:17
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 2833d9d to 370f9f3 Compare February 2, 2026 16:16
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 115808e to 2d8c233 Compare February 17, 2026 18:38
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 2d8c233 to 7c17510 Compare March 5, 2026 17:07
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 7c17510 to d25758b Compare March 13, 2026 13:06
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from d25758b to 3c67aa0 Compare April 1, 2026 15:45
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 3c67aa0 to 6354846 Compare April 8, 2026 15:48
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 6354846 to e932ce4 Compare April 29, 2026 17:37
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from e932ce4 to 3cd41ca Compare May 12, 2026 14:02
@socket-security
Copy link
Copy Markdown

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 High
Obfuscated code: npm @typescript-eslint/eslint-plugin is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: ?npm/@nuxtjs/eslint-config-typescript@12.1.0npm/@typescript-eslint/eslint-plugin@6.21.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@6.21.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 High
Obfuscated code: npm node-fetch-native is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: ?npm/@docus/theme@1.2.2npm/node-fetch-native@1.6.7

ℹ 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/node-fetch-native@1.6.7. 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 High
Obfuscated code: npm string.prototype.trimend is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: ?npm/@nuxtjs/eslint-config-typescript@12.1.0npm/string.prototype.trimend@1.0.9

ℹ 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/string.prototype.trimend@1.0.9. 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 High
Obfuscated code: npm ts-api-utils is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: ?npm/@nuxtjs/eslint-config-typescript@12.1.0npm/ts-api-utils@1.4.3

ℹ 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/ts-api-utils@1.4.3. 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 High
Obfuscated code: npm ts-api-utils is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: ?npm/@nuxtjs/eslint-config-typescript@12.1.0npm/ts-api-utils@1.4.3

ℹ 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/ts-api-utils@1.4.3. 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

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

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants