fix: replace weak hash functions with SHA-256 #3168
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.
Checklist
npm install && npm run lint && npm test
passesDescription of change
This PR replaces weak cryptographic hash functions (MD5 and SHA1) with SHA-256 across the
node-gyp
codebase to improve security. The changes affect hash generation for:Security Impact: Addresses potential security vulnerabilities by replacing deprecated hash functions that are susceptible to collision attacks.
Performance & Functionality: No impact on build speed or functionality. All existing features work exactly the same with stronger security guarantees.
Compatibility: Maintains full backward compatibility while using modern cryptographic standards.