Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Optional tools are fetched from master, and cmake/ikos.cmake is included nowhere

Open
  • Is something wrong?
#174 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
69/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
cmake, cpp, shell
Domain
build-system, devops

Research direction

Read the three named CMake modules, scripts/release/check-pinned-dependencies.sh, and the relevant section of CMakeLists.txt. Pin flawfinder and TscanCode, update the script exclusions, and remove the unused ikos module and commented include. Run check-pinned-dependencies.sh, ctest, and configure and build with both options enabled to verify the acceptance criteria.

Written by the indexing model from the issue text.

Description

build severity/minor

Three build modules fetch GIT_TAG master:

  • cmake/flawfinder.cmake:7 (-DENABLE_FLAWFINDER=ON);
  • cmake/tscancode.cmake:7 (-DENABLE_TSCANCODE=ON);
  • cmake/ikos.cmake:55, which nothing includes: its include is commented out in CMakeLists.txt:144, and ikos is found through PATH.

scripts/release/check-pinned-dependencies.sh skips these three files because no release ships those tools. As a result, two builds of the same commit with the same option can get different versions of flawfinder or TscanCode, and cmake/ikos.cmake is dead code.

To do

  • Pin flawfinder and TscanCode to a tag or a commit, like the other dependencies.
  • Remove them from the exclusion list of check-pinned-dependencies.sh.
  • Delete cmake/ikos.cmake and the commented include.

Acceptance

  • check-pinned-dependencies.sh checks every file in cmake/, and ctest passes.
  • A build with -DENABLE_FLAWFINDER=ON -DENABLE_TSCANCODE=ON still configures and builds.

From the technical debt register (docs/quality/technical-debt.md, D7).

Dominant language
C++
Stars
5
Forks
4
Avg merge
1h 4m
Merged PRs (30d)
71

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CoreTrace/coretrace

All issues in CoreTrace/coretrace

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.