Merged
Conversation
tf-seti
changed the title
tf-seti
force-pushed
the
appsec/harden-yarn-config
branch
from
e06f4d4 to
b67e351
Compare
|
❌ The last analysis has failed. |
|
✅ Security Analysis ResultsGreat news! No security issues found in this pull request. Analysis Summary:
Security analysis powered by Claude Sonnet 4.6 via pr-auditor | Questions? Contact #dx-team or check out this page |
|
🥷 Code experts: robespmun robespmun has most 👩💻 activity in the files. See details
Activity based on git-commit:
Knowledge based on git-blame: ✨ Comment |
Thr44
approved these changes
Apr 28, 2026
|
🎉 This PR is included in version 2.10.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Harden yarn configuration
This PR hardens yarn configuration against recent supply chain attacks
(shai hulud, shai hulud 2, litellm, axios).
More details in Hardening Development Supply Chain.
Changes
.yarnrcsecurity settings:ignore-scripts true— blocks all postinstall script execution (RATs, cryptominers, credential exfiltration)save-exact true— forces exact version pins onyarn add(no^prefix)Dependabot cooldown (if npm ecosystem configured):
What you need to know
ignore-scriptsapplies to bothyarn installandyarn add— postinstall scripts will not run in either case.husky,esbuildnative binaries), run them explicitly:References
Automated by Application Security · supply-chain-hardening batch change
Created by Sourcegraph batch change
david.salvador/harden-yarn-config.