EchoTrace: stopped maintaining, two successors, and a repository with no source
EchoTrace is a local, secure tool for exporting, analyzing, and generating annual reports of WeChat chat records.
At a glance
- What is it?
- EchoTrace is a Flutter desktop tool that decrypts WeChat chat records on your own machine, exports them as HTML and builds an annual report from them. The interesting parts are where it stopped: the maintenance notice sits in a callout rather than at the top, the version jumped from 3.1.0 to 5.2.0 in a single week, and the repository root holds a generated report instead of a source directory.
- Who is it for?
- EchoTrace is worth reading as a demonstration of what a local chat-analysis tool can do, and worth installing only if you accept that it will not be fixed. The README says maintenance has stopped and names two successors split by feature, so check whether the one covering the half you want is the successor for the half you use.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Activity is slowing. The repository last received commits 8 months ago.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- ycccccccy/echotrace3,864 ★ · +48
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| ycccccccy/echotrace | 3.8k | 3.9k |
48 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The version jumped from 3.1.0 to 5.2.0 and lost its v prefix
The release titles do not follow one convention. The list reads 5.2.0, then v3.1.0, then v3.0.8, so the newest tag has both a different number and a different shape from the two below it, and the highest minor number is a little over five while the previous one is a little over three. The dates are closer together than the numbers suggest: v3.0.8 on 2026-01-07, v3.1.0 on 2026-01-09, and 5.2.0 on 2026-01-18, three tags in eleven days. And the newest release is not titled with a version description at all, its name is a Chinese phrase roughly meaning some things I wanted to say. So there is a large version gap, a formatting change and a naming change inside a single week, which is what a project looks like when a rewrite or a rename has happened and the release history was not reset to match.
The maintenance notice is a tip block, not the first line
The README opens by describing the tool as fully local, and that is accurate as far as it goes. The fact that matters for anyone deciding whether to install it is further down, in a callout box: the project has stopped being maintained, and two successors are named. WeFlow is pointed at for the realtime functionality, and a second project is pointed at for the backup functionality. So the handover is split by feature rather than offered as one replacement, which tells you the two halves of the original had become separable. A separate callout above it recommends a third project, ChatLab, for the step after exporting, which is a different thing again: not decryption but analysis. Three projects, three jobs, and only the first one is the tool whose README you are reading.
It is a Flutter app whose repository top level has no source directory
The build instructions are the giveaway about the stack:
git clone https://github.com/ycccccccy/echotrace.git
cd echotrace
flutter pub get
flutter run
flutter build windowsSo it is a Flutter application, packaged for desktop, with the Windows target given as the example. What is odd is the repository root, which holds a licence, the README, a `docs/` directory, one image file and one markdown report. There is no `lib/`, no `pubspec.yaml` and no application directory at the top level, which is not a layout `flutter pub get` would work from. The language field on the repository is empty as well, so neither the metadata nor the tree tells you what the code is written in; the build steps do. Documentation is split into three files, a beginner guide, a developer guide covering architecture, file responsibilities, debugging and the command line, and a separate note on how realtime mode is implemented.
Three kinds of decryption, credited to three projects
The acknowledgement section is specific about where the difficult parts came from, and that is the most technically informative part of the file. Decrypting the chat record database itself is credited to chatlog, described as providing the important idea and reference. Decrypting images is credited to a separate project, WxDatDecrypt, for the method. And parsing inline images and voice messages is credited to an individual contributor by handle. So the tool touches three different formats and the author acknowledges a different source for each. The chat database work is where the tool's central capability sits, and the README is explicit that the tool decrypts your records, saves them locally for offline viewing and can export them as HTML to share with friends. That combination is what makes the responsible-use note at the end of the file more than boilerplate.
The roadmap has a stray tick inside an unfinished checkbox
The future plans section is a checklist, and reading it tells you where the project stopped. Three items are ticked: parsing and displaying voice, images and stickers; the two-person report's earliest chat date together with the annual statistics; and word cloud statistics of the words each person sends most. Four are unticked: more visualisation charts, a radar chart of message types per person covering voice, image, video, file, sticker and text, a distribution of the times of day the two of you message most plus a yearly heatmap, and a summary image generated from the report. The first unticked item contains a finished checkbox drawn inside its own text, next to the words for an annual word cloud, which is how a completed sub-item got marked in the middle of an open line. The result is a roadmap where a reader has to work out which parts of a line are done.
A generated report is committed as the only example output
The most interesting file in the repository is not code. There is a `report.md` at the root, next to the README, which is a report produced by the tool and committed as an example of what it generates, and an `echotrace.png` which is a screenshot. Between them they are the entire demonstration surface, since there is no sample database, no fixture and no test in the tree. That has an obvious appeal, because a chat-analysis tool is hard to evaluate from a feature list and easy to evaluate from an output, and one committed report answers the question faster than any paragraph. It also means the repository is small enough to read in full, which is not something you can say about the Flutter projects it hands off to.
The README ends on a request to use it responsibly
The closing section is not a technical note. It tells the reader to use the tool responsibly and to comply with the relevant laws and regulations, and then adds a line suggesting that cherishing the people in front of you may matter more than dwelling in the past. That framing fits a project whose stated purpose is nostalgic rather than analytical, which is also why the roadmap is full of small aesthetic additions, a word cloud and a sticker battle, and why the successor recommendation is phrased as something to try if you want to keep using it. It also puts the responsibility on the user in a place where the decryption capability has already been described, which is the right place for it: the tool reads a database on your own machine, and what you then do with the export, including sharing it as HTML with a friend, is not something the tool can decide for you.
Editorial conclusion
EchoTrace is worth reading as a demonstration of what a local chat-analysis tool can do, and worth installing only if you accept that it will not be fixed. The README says maintenance has stopped and names two successors split by feature, so check whether the one covering the half you want is the successor for the half you use. Version the checkout by commit rather than by tag, since the release numbering changes shape inside one week and the newest release is not described in version terms. Read the acknowledgements before you rely on the decryption paths, because three different formats are handled and each one is credited to a different upstream project whose behaviour may move underneath you. And treat the export step as the sensitive part: the tool stays local, but an HTML export you share with a friend is a copy of someone's messages outside your machine, which is what the responsible-use note at the end of the README is pointing at.
Frequently asked questions
What does EchoTrace do?
It decrypts your WeChat chat records, saves them locally so you can view them offline, exports them as HTML so you can share them with friends, and generates a personalised analysis report from them. The README describes the whole process as fully local. It is a Flutter application, with the Windows packaging target given as the build example.
Is EchoTrace still maintained?
No. A notice in the README says the project has stopped being maintained and points at two successors, one covering the realtime functionality EchoTrace had and one covering its backup functionality. A separate callout recommends ChatLab for analysing chat content after you have exported it.
How do I build EchoTrace from source?
Clone the repository, run `flutter pub get`, then `flutter run` for a debug build and `flutter build windows` as the packaging example. Architecture, file responsibilities, debugging and command line notes are in the developer guide in docs, and the implementation of realtime mode has its own document covering the wcdb integration.
What reports can EchoTrace generate?
Finished items are parsing and showing voice, images and stickers, the two-person report's earliest chat date with annual statistics, and word cloud statistics of the words each person sends most. Still open are more visualisation charts, a radar chart of message types per person, chat time-of-day distribution with a yearly heatmap, and a summary image generated from the report.
What does EchoTrace credit for the decryption work?
Three references. Decrypting the chat records is credited to chatlog for the important idea and reference, decrypting images to WxDatDecrypt for the method, and inline image and voice parsing to a contributor credited by handle. EchoTrace itself is MIT licensed, free to use, modify and distribute at your own risk.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/ycccccccy-echotrace)Star history chart for your README
[](https://hysenlabs.com/projects/ycccccccy-echotrace)Was this useful?