Security/npm lockdown 2025 09 08 #1653
                
     Merged
            
            
          
  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.
  
    
  
    
🛡️ Security: Block Compromised NPM Releases & Centralize Package Installation
Summary
This PR centralizes package installation across GitHub workflows and adds security measures to prevent malicious package versions sneaking in.
ℹ️ There are currently no known vulnerabilities in the dependency tree, but this is a proactive measure to guard against yesterday's supply chain attack.
Changes
1. Centralize Package Installation and Hardening
.github/actions/install/action.ymlfor centralized dependency installationDISABLE_NPM_SCRIPTS2. Security Measures
.yarn/constraints.profor 19 malicious package versionsresolutionsinpackage.json:color: 4.2.3,color-string: 1.9.1,color-convert: 2.0.1color-name: 1.1.4,chalk: 4.1.2, plus 13 related packagesBenefits