repowiseassafelovic/gpt-researcher

assafelovic / gpt-researcher

pythonmain5d84d2f63.7K linessynced on Aug 12, 2026

Code health

7.2out of 10Good

Hotspots average 2.0, the place fixes pay off most.

Explore this codebase

Do next · 3

3 things worth doing in the week to Jul 14, the last indexed commit.

Worth planning

  • Start breaking up create_chat_completion_with_tools (CCN 24, 109 lines)

    gpt_researcher/utils/tools.py:158

    create_chat_completion_with_tools nests deeply; easier to read and change once split; its file is imported by 1 file, changed 1 time in 90 days.

    gain
    up to +1.7 health on this file(inferred)
    finding
    Nested complexity
    size
    CCN 24, 109 lines, nests 8 deep
    severity
    high
    worth a check
  • Address the finding in <anonymous@1>

    frontend/scripts.js:1

    <anonymous@1> has a bumpy road finding; function changed in 18 commits; changed 1 time in 90 days.

    gain
    up to under +0.1 health on this file(inferred)
    finding
    Bumpy road
    size
    CCN 293, 1,803 lines, nests 4 deep
    severity
    high
    worth a check
  • Start breaking up from_provider (CCN 41, 170 lines): first lift lines 206-213

    gpt_researcher/llm_provider/generic/base.py:206

    from_provider has many paths; easier to read and change once split; function changed in 29 commits; its file is imported by 10 files, changed 6 times in 90 days.

    gain
    up to +1.5 health on this file(inferred)
    finding
    Complex method
    size
    CCN 41, 170 lines
    severity
    high
    worth a check

Improve what Repowise can see

  • Add a test coverage report

    Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.

    line coverage
    Unknown, no report

Everything we found

5 areas