Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 1, 2022

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: Branch creation - On day 1 of the month, every 12 months ( * * 1 */12 * ) (UTC), 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 has been generated by Mend Renovate using a curated preset maintained by Sanity. View repository job log here

@socket-security
Copy link

socket-security bot commented Sep 1, 2022

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 npm is 94.0% likely obfuscated

Confidence: 0.94

Location: Package overview

From: package-lock.jsonnpm/npm@8.19.4

ℹ 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/npm@8.19.4. 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

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 73802b3 to 4c7b24d Compare March 11, 2023 12:55
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 4c7b24d to f4d4f22 Compare August 10, 2025 13:06
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 755df17 to 740f897 Compare August 19, 2025 16:58
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 740f897 to 82dac32 Compare August 31, 2025 09:45
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 82dac32 to 471ec14 Compare September 25, 2025 19:32
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 471ec14 to da8a023 Compare October 21, 2025 17:41
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from da8a023 to 00d6021 Compare November 11, 2025 00:14
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 00d6021 to ea5d4cc Compare November 18, 2025 22:44
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from ea5d4cc to 218b725 Compare December 3, 2025 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant