Skip to content

Issues: github/codeql-coding-standards

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

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
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
A12-8-6: Compiler generated special functions are not consistently flagged 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
#811 opened Dec 5, 2024 by lcartey
A4-7-1: false positives in for loops Difficulty-High A false positive or false negative report which is expected to take 1+ week effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-Medium Standard-AUTOSAR
#798 opened Nov 14, 2024 by fjatWbyT
A4-7-1: integer data loss false positive erasing from container Difficulty-High A false positive or false negative report which is expected to take 1+ week effort to address false positive/false negative An issue related to observed false positives or false negatives. Impact-Medium Standard-AUTOSAR
#793 opened Nov 11, 2024 by fjatWbyT
A5-16-1: Constructing std::string is considered as sub-expression in ternary operation 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 user-report Issue reported by an end user of CodeQL Coding Standards
#754 opened Oct 18, 2024 by nbusser-sr
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
A1-1-2: does not understand -Wno-* flags 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
#689 opened Sep 17, 2024 by MichaelRFairhurst
RULE-11-9: Consider more types of assignment 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-MISRA-C
#671 opened Sep 6, 2024 by lcartey
A15-4-4: Functions that allocate are considered non-throwing 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
#662 opened Aug 13, 2024 by gg-sr
A8-5-2: Reports a violation even for correctly initialized variables as per the rule 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 user-report Issue reported by an end user of CodeQL Coding Standards
#645 opened Jul 17, 2024 by rak3-sh
A7-1-7: Exclude expression statements in macros 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
#629 opened Jun 26, 2024 by lcartey
A5-16-1: Ternary operator not used as a sub expression 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 user-report Issue reported by an end user of CodeQL Coding Standards
#612 opened Jun 5, 2024 by nbusser
M0-1-2 - A3-1-5 - A4-5-1 - M0-1-1 : Poor lambda support 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 user-report Issue reported by an end user of CodeQL Coding Standards
#605 opened Jun 2, 2024 by nbusser
A4-7-1: Guard using "." operator getting ignored Difficulty-High A false positive or false negative report which is expected to take 1+ week 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
#600 opened Jun 1, 2024 by nbusser
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
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
A3-9-1: Incorrectly alerts on template functions instantiated with fix-width integers 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 user-report Issue reported by an end user of CodeQL Coding Standards
#540 opened Feb 21, 2024 by rvermeulen
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
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
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.