exclude lock files and tools folder from export to prevent scanning#322
Merged
shadowhand merged 1 commit intowebmozarts:masterfrom Oct 29, 2025
Merged
Conversation
Collaborator
|
Thanks! Fixed in version v1.12.1. |
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
2 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.
I am creating this MR because I stumbled upon an issue that was apparently introduced in version 1.12.0 where the security scan is flagging vulnerability issues in the tools path.
To circumvent this, we are locking the dependency to the previous version
~1.11.0.We believe PR #304 might be the culprit, as it added the
/toolsdirectory but didn't update.gitattributesto exclude it from distribution.