CoreTrace/coretrace
coretrace is a C/C++ analysis orchestrator that runs multiple static and dynamic tools and produces unified reports to detect vulnerabilities, security issues, and memory misuse
Is CoreTrace/coretrace beginner-friendly?
In the last 30 days, CoreTrace/coretrace merged 79 of 83 pull requests from outside contributors, and its maintainers usually reply within 1 day. 4 beginner-friendly issues are open now.
- Stars
- 5
- Forks
- 4
- Open beginner issues
- 4
- Indexed issues
- 17
- Avg merge
- 1h 10m
- Merged PRs (30d)
- 79
- Dominant language
- C++
- License
- Apache-2.0
- Last GitHub push
- Oct 4, 2026
- Latest indexed
- Oct 6, 2026
- Contributing guide
- Contributing guide
- Code of conduct
- Code of conduct
- Beginner labels
- good first issue
How to contribute to CoreTrace/coretrace
- Read the contributing guide first: it says how the maintainers want changes proposed, tested and reviewed.
- Read its code of conduct: it covers issues and pull requests as well as chat.
- Your contributions will be published under the project's Apache-2.0 license.
- Pick one of the 4 open beginner-friendly issues below and comment that you want to work on it before you start.
Issues somebody may already be working on are listed last. List everything by date
-
bug severity/minor
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
bug severity/minor
Difficulty 3/5 1-2 days Newbie friendliness 50/100
Maintainers usually reply within 1 day
-
bug severity/major
Difficulty 3/5 Half a day Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug severity/major
Difficulty 4/5 3-5 days Newbie friendliness 50/100
Maintainers usually reply within 1 day
-
chore good first issue severity/minor
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
build severity/minor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
CoreTrace/coretrace#176 · 1 comment ·
Maintainers usually reply within 1 day
-
build good first issue severity/minor
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
build severity/minor
Difficulty 3/5 1-2 days Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
chore severity/minor
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
refactor severity/major
Difficulty 4/5 3-5 days Newbie friendliness 58/100
Maintainers usually reply within 1 day
-
enhancement severity/major
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
-
Builds without a build type are unoptimized: the README's commands and CI's main jobPossibly taken @SizzleUnrlsd claimed this today. Openbuild severity/minor
CoreTrace/coretrace#192 · 1 assignee ·
Maintainers usually reply within 1 day
-
build(deps): update coretrace-stack-analyzer past v0.22.0, which does not finish on CoreTrace's own codePossibly taken @SizzleUnrlsd claimed this today. Openbug build severity/major
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Maintainers usually reply within 1 day
-
test: add unit tests for ctrace::RunDirectoryPossibly taken @tecnolgd claimed this 2 days ago. Opengood first issue test
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
CoreTrace/coretrace#164 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day