-
Notifications
You must be signed in to change notification settings - Fork 1
Dev #263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Dev #263
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| # Scan shipped JS/TS (sdk/typescript). Local sanity harnesses read | ||
| # ACCOUNTBLOX_ADDRESS / TEST_WALLET_*_PRIVATE_KEY from process.env and log | ||
| # public contract addresses; js/clear-text-logging taints all process.env | ||
| # and files High alerts that are not credential leaks. | ||
| name: Bloxchain Protocol JS/TS | ||
| paths-ignore: | ||
| - scripts/sanity/** | ||
| - scripts/sanity-sdk/** | ||
| - scripts/count-loc.cjs | ||
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: PracticalParticle/Bloxchain-Protocol
Length of output: 6827
🏁 Script executed:
Repository: PracticalParticle/Bloxchain-Protocol
Length of output: 10803
🌐 Web query:
GitHub CodeQL workflow configuration options paths paths-ignore default analyzed paths config file💡 Result:
In GitHub CodeQL workflow configurations, paths and paths-ignore can be used in two distinct ways: at the workflow trigger level and at the analysis configuration level [1][2]. It is critical to distinguish between them as they serve different purposes [1][3]. Workflow Trigger (on:pull_request:paths/paths-ignore) These options control whether the CodeQL workflow runs at all when a pull request is opened or updated [1][2]. - They do not determine which files are scanned during the analysis [1][3]. - If the workflow triggers (e.g., a file is modified that is not in the paths-ignore list), the CodeQL action will still analyze all changed files in the PR, including those you might have attempted to ignore at the trigger level [1][2]. CodeQL Configuration File (paths/paths-ignore) To actually restrict or exclude files from being analyzed, you must use a CodeQL configuration file (typically.github/codeql/codeql-config.yml) [1][4]. - This file is referenced in your workflow using the config-file parameter of the github/codeql-action/init action [5][3]. - Within this file, you can specify paths and paths-ignore to control exactly which directories or files are included in or excluded from the scan [1][4]. Example CodeQL Configuration File name: "My CodeQL Config" paths: - src/ # Only scan files in this directory paths-ignore: - src/node_modules # Exclude these directories/files from analysis - '/*.test.js' Workflow Reference - uses: github/codeql-action/init@v4 with: config-file:.github/codeql/codeql-config.yml Important Considerations - Language Support: The paths and paths-ignore options in the configuration file are primarily designed for interpreted languages (Python, Ruby, JavaScript/TypeScript) or when analyzing compiled languages without a build step [1][6]. If you are using a compiled language that requires a build, you should generally handle file exclusion within your build process itself rather than relying solely on these configuration options [7]. - Trigger vs. Analysis: Always remember that paths-ignore in the workflow trigger manages CI costs by skipping the scan, while paths-ignore in the configuration file manages scan scope by filtering analyzed files [2][3].
Citations:
🏁 Script executed:
Repository: PracticalParticle/Bloxchain-Protocol
Length of output: 1101
🏁 Script executed:
Repository: PracticalParticle/Bloxchain-Protocol
Length of output: 1101
Restrict CodeQL to the shipped SDK.
If the intended scope is
sdk/typescript, add apathsentry for that directory. The current configuration has no inclusion filter and leaves 26 JavaScript/TypeScript files outside the SDK in scope. Otherwise, update the comment to describe the broader scope.🤖 Prompt for AI Agents