fix: AG-143 Resolve path traversal vulnerabilities in kiro hooks#29
Draft
fix: AG-143 Resolve path traversal vulnerabilities in kiro hooks#29
Conversation
bach-snyk
force-pushed
the
resolve-path-traversal-vulns-in-kiro-hooks
branch
3 times, most recently
from
3222460 to
ec0c662
Compare
chore: Update logic to include workspace path chore: Update order of args chore: Replace double with single quotes in build script chore: Update whitespace chore: Test commit chore: Test commit chore: Test commit chore: Move file chore: Format file name and update safe_open chore: Remove utils, update installer.sh chore: Update vscode settings with trusted commands chore: Update install
bach-snyk
force-pushed
the
resolve-path-traversal-vulns-in-kiro-hooks
branch
from
402e3c9 to
ebe1dc6
Compare
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
1 participant
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.
open_debounce_filethat leverages thesafe_open_within_basefunction defined in a previous PRSTATE_DIRvar to appease thesnyk code testscanbuild.shto be linter compliant.vscode/settings.jsonwhen running the installer with the background_scanner as a trusted comman; this makes it so that the script doesn't need to constantly prompt the user when running after a file edit