Skip to content

Issues: github/codeql-coding-standards

Beta
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

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

DIR-15-8-1: move assignment self-assignment false positive false positive/false negative An issue related to observed false positives or false negatives.
#889 opened Apr 24, 2025 by fjatWbyT updated Apr 24, 2025
Add support for tss_t thread local objects in Objects.qll Difficulty-Medium A false positive or false negative report which is expected to take 1-5 days effort to address Impact-Low Standard-MISRA-C
#877 opened Mar 27, 2025 by MichaelRFairhurst updated Mar 27, 2025
DIR-4-15: Add support for fpclassify() functions. Difficulty-Low A false positive or false negative report which is expected to take <1 day effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-Low
#875 opened Mar 25, 2025 by MichaelRFairhurst updated Mar 25, 2025
Flag duplicate code identifiers as invalid enhancement New feature or request
#861 opened Feb 18, 2025 by lcartey updated Mar 9, 2025
RULE-21-15: Improve detection of compatible types Difficulty-Medium A false positive or false negative report which is expected to take 1-5 days effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-Medium Standard-MISRA-C
#573 opened Apr 25, 2024 by lcartey updated Mar 7, 2025
RULE-8-4: Improve detection of compatible types Difficulty-Medium A false positive or false negative report which is expected to take 1-5 days effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-Low Standard-CERT-C
#780 opened Oct 24, 2024 by lcartey updated Mar 7, 2025
A4-7-1: Incorporate CERT C integer data loss rules Difficulty-Medium A false positive or false negative report which is expected to take 1-5 days effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-High Standard-AUTOSAR
#491 opened Jan 17, 2024 by lcartey updated Jan 28, 2025
A5-6-1: Replace with INT33-C implementation Difficulty-Medium A false positive or false negative report which is expected to take 1-5 days effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-High Standard-AUTOSAR
#492 opened Jan 17, 2024 by lcartey updated Jan 28, 2025
RULE-25-21, others: Consider something like a library TracesToExplicit<T> Difficulty-Low A false positive or false negative report which is expected to take <1 day effort to address enhancement New feature or request Impact-Low
#848 opened Jan 27, 2025 by MichaelRFairhurst updated Jan 27, 2025
CON34-C: Implementation seems to check incorrect aspects of thread storage duration objects false positive/false negative An issue related to observed false positives or false negatives. Standard-CERT-C
#801 opened Nov 20, 2024 by MichaelRFairhurst updated Jan 27, 2025
M5-0-12: Incorrect alerts on assignments of valid numerical values Difficulty-Low A false positive or false negative report which is expected to take <1 day effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-Medium Standard-AUTOSAR
#541 opened Feb 21, 2024 by rvermeulen updated Jan 20, 2025
A15-4-2: Ignore elided calls when calculating the exception graph Difficulty-Medium A false positive or false negative report which is expected to take 1-5 days effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-High Standard-AUTOSAR top-25-fps user-report Issue reported by an end user of CodeQL Coding Standards
#158 opened Jan 6, 2023 by lcartey updated Jan 20, 2025
A1-1-1: Implementation of Rule only looks for deprecated features and not use of implementation extensions Difficulty-Medium A false positive or false negative report which is expected to take 1-5 days effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-High Standard-AUTOSAR user-report Issue reported by an end user of CodeQL Coding Standards
#86 opened Sep 16, 2022 by rcseacord updated Jan 20, 2025
STR34-C: Rule improvements Difficulty-Medium A false positive or false negative report which is expected to take 1-5 days effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-High Standard-CERT-C
#577 opened May 1, 2024 by lcartey updated Jan 20, 2025
A8-2-1: query not implemented Difficulty-High A false positive or false negative report which is expected to take 1+ week effort to address Impact-Medium Standard-AUTOSAR
#162 opened Jan 11, 2023 by rcseacord updated Jan 20, 2025
A0-1-1: initialization of constexpr used as NTTP is detected as useless assignment Difficulty-Medium A false positive or false negative report which is expected to take 1-5 days effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-Medium Standard-AUTOSAR user-report Issue reported by an end user of CodeQL Coding Standards
#728 opened Oct 3, 2024 by fjatWbyT updated Jan 17, 2025
A2-7-3: template function prototypes with comments are not correctly detected Difficulty-Medium A false positive or false negative report which is expected to take 1-5 days effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-High Phase III Standard-AUTOSAR user-report Issue reported by an end user of CodeQL Coding Standards
#528 opened Feb 9, 2024 by rvermeulen updated Jan 16, 2025
A12-1-1: Does not apply transitively Difficulty-Low A false positive or false negative report which is expected to take <1 day effort to address false positive/false negative An issue related to observed false positives or false negatives. false-positive An issue representing a false positive report. Impact-Medium Standard-AUTOSAR user-report Issue reported by an end user of CodeQL Coding Standards
#829 opened Dec 23, 2024 by nbusser-sr updated Jan 16, 2025
RULE-18-1: Picky about how pointers are tracked, doesn't consider derefs before 1 from end, or array-to-pointer conversions Difficulty-Medium A false positive or false negative report which is expected to take 1-5 days effort to address false positive/false negative An issue related to observed false positives or false negatives. false-negative An issue representing a false negative report. Impact-Medium Standard-AUTOSAR Standard-MISRA-C
#840 opened Jan 16, 2025 by MichaelRFairhurst updated Jan 16, 2025
A5-2-2, RULE-1-2: Utilize new module to improve macro handling Difficulty-Low A false positive or false negative report which is expected to take <1 day effort to address enhancement New feature or request Impact-Low Standard-AUTOSAR Standard-MISRA-C
#839 opened Jan 16, 2025 by MichaelRFairhurst updated Jan 16, 2025
RULE-2-2, etc: use new macro deduplication module for improved results Difficulty-Low A false positive or false negative report which is expected to take <1 day effort to address enhancement New feature or request false positive/false negative An issue related to observed false positives or false negatives. false-negative An issue representing a false negative report. Impact-Low Standard-AUTOSAR Standard-MISRA-C Stardard-MISRA-C++
#838 opened Jan 16, 2025 by MichaelRFairhurst updated Jan 16, 2025
A15-4-4: Query incorrectly alerts functions that raise/can raise exceptions Difficulty-Medium A false positive or false negative report which is expected to take 1-5 days effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-Low
#824 opened Dec 17, 2024 by rak3-sh updated Dec 22, 2024
RULE-10-4: False negatives as rule does not currently consider ternaries Difficulty-Low A false positive or false negative report which is expected to take <1 day effort to address false positive/false negative An issue related to observed false positives or false negatives. false-negative An issue representing a false negative report. Impact-Low Standard-MISRA-C
#821 opened Dec 12, 2024 by MichaelRFairhurst updated Dec 12, 2024
A2-10-1: False positive around null identifiers on tuple-like types in structural binding (relevant C++17 only) C++17 Difficulty-Low A false positive or false negative report which is expected to take <1 day effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-Low Standard-AUTOSAR wontfix This will not be worked on
#581 opened May 7, 2024 by knewbury01 updated Dec 11, 2024
DCL30-C: Replace implementation with cpp/return-stack-allocated-memory Difficulty-Medium A false positive or false negative report which is expected to take 1-5 days effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-Medium Standard-CERT-C
#495 opened Jan 19, 2024 by lcartey updated Dec 10, 2024
ProTip! Follow long discussions with comments:>50.