Repository navigation
[BUG] Fix LGTM/CodeQL alerts #960
Description
Description
There are 10+ CodeQL alerts on the whole repository. This should be fixed immediately.
Expected behavior
CodeQL/LGTM alerts should be fixed.
Actual behavior
We have 10+ CodeQL/LGTM alerts.
Possible fix
No response
Steps to reproduce
Not applicable here, IMO.
Context
This makes our code less elegant and professional. We should try to use the best code possible.
Additional information
Anyone who wants to work on this, feel free to do so. Just make sure you comment here before working on the issue. 🙂
Activity
Kim8178184977 commentedon Sep 19, 2022
is there any one working on it
Panquesito7 commentedon Sep 19, 2022
Nope, not currently. Do you wanna work on this? 🙂
Kim8178184977 commentedon Sep 20, 2022
sure I will try My best sir 😊
Panquesito7 commentedon Sep 20, 2022
Cool, thank you! Let us know if you need any help.
Kim8178184977 commentedon Sep 21, 2022
sir, i can't find the repository can you give me the name of it
Panquesito7 commentedon Sep 21, 2022
Here you can see all the alerts/warnings: https://lgtm.com/projects/g/TheAlgorithms/C/context:cpp
Meghanagowd commentedon Apr 11, 2025
"I’d like to work on fixing LGTM alerts in [file.c]. Please assign me!"
wjc2821296948 commentedon Oct 12, 2026
I am working on two concrete memory-safety issues related to this umbrella issue: the undersized allocation in
leetcode/src/5.c(malloc(sizeof(s))) and the input buffer allocation/bounds handling inmisc/lexicographic_permutations.c. I will keep the fixes focused and include regression/self-tests where practical.