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

A12-1-1: Does not apply transitively false positive/false negative An issue related to observed false positives or false negatives.
#829 opened Dec 23, 2024 by nbusser-sr
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
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
DCL53-CPP: Reports non syntactically ambiguous object declarations 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
#812 opened Dec 6, 2024 by lcartey
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
A2-10-5: id name reuse false positive with template specialization 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 user-report Issue reported by an end user of CodeQL Coding Standards
#806 opened Dec 2, 2024 by fjatWbyT
M7-5-1: Class members are considered as **automatic** variables 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-High user-report Issue reported by an end user of CodeQL Coding Standards
#805 opened Nov 29, 2024 by nbusser-sr
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
RULE-10-3: Essential type of binary bitwise operations is incorrect 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
#786 opened Oct 28, 2024 by lcartey
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
RULE-8-13: Consider possible macro false positives 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-Low Standard-MISRA-C
#775 opened Oct 22, 2024 by lcartey
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
A20-8-5-A20-8-6: Cannot create a smart pointer with nullptr value 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 user-report Issue reported by an end user of CodeQL Coding Standards
#721 opened Sep 30, 2024 by nbusser-sr
A2-7-3: missing documentation when there's a comment after doxygen grouping 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-AUTOSAR user-report Issue reported by an end user of CodeQL Coding Standards
#718 opened Sep 27, 2024 by fjatWbyT
A2-7-3: documented type alias to template instantiation considered undocumented 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-AUTOSAR user-report Issue reported by an end user of CodeQL Coding Standards
#709 opened Sep 22, 2024 by fjatWbyT
Simplify link target handling enhancement New feature or request Standard-MISRA-C
#700 opened Sep 19, 2024 by lcartey
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
ProTip! Type g i on any issue or pull request to go back to the issue listing page.