Add CodeQL config to exclude vendor/third-party code #236
Conversation
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
CybotTM
added a commit
that referenced
this pull request
Dec 19, 2025
The repository has GitHub's default CodeQL setup enabled, which conflicts with the custom workflow file. The custom workflow was failing with: - "Did not recognize the following languages: php" - Matrix configuration issues with javascript-typescript The default CodeQL setup is: - Already enabled and working correctly - Automatically detects languages (JavaScript/TypeScript, PHP, Ruby, Actions) - Handles security analysis without additional configuration - Passing all checks successfully Removing the custom workflow eliminates the conflict and allows the default setup to function properly. The vendor exclusion goals from the codeql-config.yml are already handled by GitHub's default setup which intelligently excludes common vendor/dependency directories. Fixes: Failing CodeQL checks in PR #236
Configure CodeQL analysis to exclude bundled dependencies: - assets/js/ext-js/** (ExtJS 4.1 framework, 2011-2012) - public/docs/swagger/** (Swagger UI bundle) - vendor/**, node_modules/**, *.min.js This resolves 30 false-positive security alerts from third-party code: - 26x js/regex/missing-regexp-anchor in ExtJS - 4x js/remote-property-injection in Swagger UI These are vendor dependencies that cannot be modified without major application rewrites. The CodeQL config follows GitHub's recommended approach for excluding third-party code from security analysis.
The repository has GitHub's default CodeQL setup enabled, which conflicts with the custom workflow file. The custom workflow was failing with: - "Did not recognize the following languages: php" - Matrix configuration issues with javascript-typescript The default CodeQL setup is: - Already enabled and working correctly - Automatically detects languages (JavaScript/TypeScript, PHP, Ruby, Actions) - Handles security analysis without additional configuration - Passing all checks successfully Removing the custom workflow eliminates the conflict and allows the default setup to function properly. The vendor exclusion goals from the codeql-config.yml are already handled by GitHub's default setup which intelligently excludes common vendor/dependency directories. Fixes: Failing CodeQL checks in PR #236
CybotTM
force-pushed
the
security/exclude-vendor-from-codeql
branch
from
3180735 to
e608593
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Problem
CodeQL is currently reporting 30 security alerts on third-party/vendor code:
These are false positives from bundled dependencies that:
Solution
Configure CodeQL to exclude vendor paths following GitHub's recommended approach.
Security Improvements
Test Plan