/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

sansan0/TrendRadar

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-30T12:05:04.486Z

3mo ago

sansan0/TrendRadar

TrendRadar is a Python-based, Docker-friendly public-opinion and trend monitoring tool. It aggregates multi-platform hot topics and RSS feeds, applies AI filtering/translating/summarization, and can push alerts to chat and notification channels. The repo is active and large in adoption, with 50,024 stars and 22,827 forks, and recent commits show ongoing work on AI modules, MCP support, Docker hardening, and UI/report improvements.

Loading tags...

Stars50,024

Forks22,827

Default branchmaster

Last pushed2026-03-28T11:17:18Z

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 if you want broader practical functionality and a more productized workflow around monitoring, analysis, and notifications. Choose upstream if you care more about staying current, minimizing divergence, or preserving the original project shape.

Prefer this fork if you value onboarding, guided deployment, and MCP-oriented workflows over strict upstream freshness. Prefer upstream if you need the latest fixes, broader compatibility, or a lower-risk maintenance path.

Adopt this fork only if you specifically want its branding or documented positioning. If you want the most complete and current implementation, upstream is the safer choice because this fork shows no code divergence and is 13 commits behind.

Prefer this fork only if its report UX and custom notification/MCP flow are exactly what you need. If you want ongoing maintenance, upstream compatibility, and the latest fixes, upstream is the safer default.

Prefer this fork if you specifically want Chinese-platform monitoring and report generation in a narrower workflow. Prefer upstream if you want the newer MCP, AI, Docker, and broader maintenance path.

Choose this fork only if you specifically want its localized Chinese-platform framing and can accept lagging 33 commits behind upstream. For most adopters, upstream is the safer choice because it appears more current and better maintained.

Prefer this fork if you want a more guided, AI- and MCP-centered TrendRadar experience and do not mind divergence. Prefer upstream if you want the newest fixes, less maintenance risk, and a cleaner path for future updates.

Choose this fork if you want a more opinionated, documentation-rich TrendRadar variant and you are comfortable owning divergence. Choose upstream if you want the newest report, MCP, Docker, and notification behavior with lower integration risk.

Choose this fork if you want added sources, a visual dashboard, and more automation. Choose upstream if you value staying current with the main project and want the safest path for future upgrades.

Choose this fork if you want a more customized, analysis-heavy TrendRadar experience and can accept drift from upstream. Choose upstream if you value fresher maintenance, tighter compatibility, and fewer merge risks.

Fork comparison

zspy66/TrendRadar

54/100

slowing

significant_divergence

Choose this fork if you want broader practical functionality and a more productized workflow around monitoring, analysis, and notifications. Choose upstream if you care more about staying current, minimizing divergence, or preserving the original project shape.

Likely purpose

To turn TrendRadar into a more turnkey self-hosted trend-monitoring and AI analysis tool for users who want broader source coverage, deeper MCP workflows, and more polished deployment and notification handling than upstream.

Best for

People who want a feature-rich, self-hosted trend and public-opinion monitor with broad notification support.; Teams that need MCP-based natural-language analysis workflows.; Users who prefer a more turnkey, opinionated fork over tracking upstream closely.; Chinese-language users or teams centered on the fork's documented platform and notification ecosystem.

Additional features

Expanded multi-platform monitoring language and positioning, including 35-platform coverage in the fork description.
Richer MCP-focused analysis workflows, including natural-language trend exploration and multiple analysis tools.
More notification and push integrations emphasized as a core workflow, including WeChat, Feishu, DingTalk, Telegram, email, ntfy, Bark, Slack, and webhooks.
Improved reporting and browser-facing HTML report experience, with dark mode, floating toolbar, copy actions, wide-screen mode, and tab navigation mentioned in recent commits.
More turnkey deployment packaging, especially Docker hardening and Windows/MCP install improvements.
Additional configuration and keyword-priority tuning for more control over ranking and filtering.

Missing features

It appears behind upstream on recent fixes and polish, including upstream AI analysis, Docker, MCP, and notification bugfix work.
Some upstream report, notification, and storage code appears heavily rewritten or removed, which may make certain behaviors less familiar or harder to rely on.
The large divergence and 200-commit lag in both directions suggest upstream compatibility and mergeability are worse than in a lightly patched fork.
Recent upstream convenience and stability improvements may not be present here, especially around MCP Docker health checks, entrypoint behavior, and notification formatting fixes.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Good fit for adopters who want a more complete out-of-the-box trend monitor rather than a minimal upstream clone.
Likely stronger for teams that care about MCP-driven analysis and chat/notification delivery.
More polished end-user reporting and deployment workflows than a raw reference fork.
Clear bias toward practical self-hosting and rapid setup.

Risks

Large divergence raises the cost of pulling upstream fixes.
Reworked core areas like reporting, storage, and notification handling increase regression risk.
The fork may be harder to audit and maintain because it changed hundreds of files across core and docs.
Users who want the latest upstream bugfixes or a close-to-mainline codebase should be cautious.

sansan0/TrendRadar · Discofork