/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

binary-husky/gpt_academic

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T13:04:41.794Z

3mo ago

binary-husky/gpt_academic

gpt_academic is a Python-based, modular LLM interaction app focused on practical use cases like paper reading, polishing, writing, PDF/LaTeX translation and summarization, and codebase analysis/self-interpretation. It supports multiple LLM providers, local models, and plugin-like custom buttons/functions, and it is actively maintained with a very large fork/star footprint.

Loading tags...

Stars70,326

Forks8,393

Default branchmaster

Last pushed2026-01-25T12:33:10Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork only if you want its older, customized academic workflow and can accept missing upstream features. For most adopters, upstream is the safer choice because this fork is materially stale and has likely removed useful UI, localization, and integration pieces.

Prefer this fork only if its academic presentation tweaks and local workflow fit your team better than upstream’s broader, actively maintained feature set. If you want the newest models, bug fixes, and platform support, upstream is the safer choice.

Choose this fork only if its added academic/document-centric workflows match your exact use case and you are willing to own maintenance. For most users, upstream is the safer choice because it is much newer, broader, and more actively maintained.

Choose this fork if you want a Hugging Face Space-oriented academic chat interface with presentation-focused enhancements and can tolerate being far behind upstream. Choose upstream if you want current model support, newer document features, and lower maintenance risk.

Choose this fork if your priority is packaging, installers, or release automation. Choose upstream if you want the latest functional improvements, model integrations, and active maintenance.

Choose this fork only if its custom document/UI changes are specifically what you want and you are comfortable owning an older, highly diverged codebase. For most adopters, upstream is the safer default because this fork is stale and likely missing newer fixes and features.

Choose this fork if you want a more focused academic/code-analysis experience and value presentation improvements over breadth. Choose upstream if you want current maintenance, broader integrations, and the full feature set.

Choose this fork only if its older, customized academic workflow is specifically what you want. If you want the safest, most current gpt_academic experience, upstream is the better default because this fork is stale and substantially diverged.

Prefer this fork only if you want an old, customized academic workflow and do not need upstream freshness. For most adopters, upstream is the safer choice because this fork is stale and substantially diverged.

Prefer upstream unless you specifically need this frozen snapshot. This fork adds no concrete capabilities and is materially behind current upstream maintenance and feature work.

Fork comparison

ifyz/chatgpt_academic

38/100

stale

significant_divergence

Choose this fork only if you want its older, customized academic workflow and can accept missing upstream features. For most adopters, upstream is the safer choice because this fork is materially stale and has likely removed useful UI, localization, and integration pieces.

Likely purpose

A lab or个人 research-focused fork for users who want an older, customized GPT Academic experience and are willing to trade freshness for a tailored academic/document workflow.

Best for

Research groups that already know this fork and only need its specific workflow.; Users who prefer a stripped-down academic tool over upstream feature breadth.; Developers willing to maintain a divergent fork instead of tracking upstream closely.

Additional features

Document-ingestion workflows appear to be extended around conversation-doc, unstructured parsing, and markitdown-style paper extraction.
The fork appears to add or tune paper-structure extraction and related academic document processing paths.
The tree suggests additional local test/project-analysis material beyond the upstream core app, likely to support experiment-driven workflows.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

It is far behind upstream overall, so many upstream fixes, provider updates, and new features are likely missing.
English, Traditional Chinese, and Japanese translation assets were removed, making localization and multilingual docs harder.
The Live2D/waifu UI plugin was deleted, so the more playful frontend experience is gone.
The NLTK downloader helper was removed, which makes some language-processing setup less convenient.
Large deletions in the LLM bridge layer suggest provider integration and request routing are likely less complete than upstream.
It trails upstream by 387 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Can suit users who prefer a lighter, more opinionated research fork over a fast-moving upstream.
Likely keeps the core academic-paper workflow while pruning optional UI and localization baggage.
May be easier to study or adapt if you want a narrower, older codebase.

Risks

Very stale relative to upstream: 387 commits behind and only 87 ahead.
Large-scale deletions across docs, UI, and helper code imply regressions and missing capabilities.
High divergence raises merge and maintenance cost if you later want upstream updates.
Loss of localization and UI extras may make it less friendly for broader teams.