mind-map: what the open library covers and what the closed client holds back
SimpleMindMap (Sixu Mind Map in Chinese) - a powerful mind map tool.
At a glance
- What is it?
- This repository is the MIT-licensed half of Simple mind map, a framework-independent JavaScript mind map library plus a Vue2 web app. The desktop client, the Obsidian plugin and the uTools plugin that carry most of the advertised features are not in the tree, and the library itself is described as being in a low-maintenance state.
- Who is it for?
- Use this repository if you are building a web mind map product and want a library with no framework dependency, or if you intend to self-host the Vue2 app behind your own nginx. Do not read the client feature list as a library capability list, since that list describes the client, whose source is not published.
- 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?
- Yes. The repository last received commits 105 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
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
- wanglin2/mind-map12,943 ★ · +201
| Repository | 2026-09-22 | 2026-11-15 |
|---|---|---|
| wanglin2/mind-map | 12.7k | 12.9k |
201 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The repository holds the library, the feature list describes something else
The project is split in two, and the README is explicit about the seam. One half is an open source JavaScript mind map library with no framework dependency, built for putting a mind map product together quickly, and that library is the code in this repository. The other half is the desktop client and its plugins, which are not open source. Everything a reader would call impressive about the product belongs to the second half: unlimited files and nodes, mind map, logic structure, directory, org chart, timeline, fishbone and table structures, hundreds of themes, history versions, presentation mode, outline editing, minimap, rainbow lines and bidirectional node links. The consequence for an engineer is immediate. Reading this README to learn what the library can render gets you a list of things that ship as a binary, so capability questions have to be answered against the docs site rather than this file.
The open half is marked low maintenance, and the tags keep moving anyway
The library and web section carries a notice that the code in this repository has entered a low-maintenance state, and the client section says its code is under active development. Both statements sit in the same document, so read them as applying to different codebases. The version numbers on the release tags do not slow down: 0.18.4 on 2026-03-19, 0.19.0 on 2026-05-18 and 0.20.0 on 2026-08-03, with the last push to this repository on 2026-08-02. That cadence reflects the client, which downloads from this repository's releases page and from two file-hosting services and the Microsoft app store. For anyone pinning the npm package, the practical question is whether the library's own fixes are moving at all, because the repository's version number alone does not answer that.
The web app is Vue2 with ElementUI and touches local files
The second open piece is a web mind map application, built on the library with Vue2.x and ElementUI, living in the `web/` directory. It is described as usable as an online mind map app, as something you can self-host and develop further, and as able to operate files on the local computer. There is a hosted instance at web.sxmind.cn for trying it without deploying anything. Two consequences follow from the stated stack. Self-hosting means carrying a Vue2 and ElementUI dependency tree, which is a dated pair, so you inherit the maintenance burden of that choice rather than choosing your own framework. And local file access is a browser permission boundary: what it can read and write depends on what the browser grants.
The Dockerfile copies a finished bundle and never builds one
Self-hosting is wired to a five-line image:
FROM nginx
RUN mkdir /app
COPY ./index.html /app/
COPY ./dist /app/dist/
COPY nginx.conf /etc/nginx/nginx.confThere is no Node stage, no dependency install and no build command. The image serves whatever is already sitting in `dist/` at the repository root, together with the top-level `index.html`, and it replaces the server's own configuration with the checked-in `nginx.conf`. That is a fast path for shipping the prebuilt web app and a dead end for anyone who changed the library, since editing source in `simple-mind-map/` changes nothing until someone rebuilds `dist/` and copies it in again. There is also a `copy.js` at the root that the image never invokes, so whatever it does is a manual step. Read the Dockerfile as a distribution file, not a reproducible build.
The import list is shorter than the export list, and the gap is one way
File handling is stated as two lists that do not mirror each other. Import covers XMind, FreeMind, Markdown, Txt and Xlsx. Export covers PNG, XMind, SVG, PDF, Markdown, Txt, Xlsx, FreeMind, Mermaid and Html. Five of the export targets, PNG, SVG, PDF, Mermaid and Html, appear nowhere on the import side, so those formats are exits and not entrances. That matters for a workflow where a diagram is exported to Mermaid for a repository README and later needs to come back, because there is no documented re-import path for it, and a round trip through PNG or PDF is not the same thing as the structured original. XMind, FreeMind, Markdown, Txt and Xlsx are the formats listed in both directions.
macOS blocks the download until you strip the quarantine attribute
The README carries one explicit failure case, and it is a macOS one. After installing the client, the app may refuse to open with an untrusted warning or a prompt to move it to the trash. The documented fix strips the quarantine attribute:
sudo xattr -d com.apple.quarantine /Applications/思绪思维导图.appNote what this is: a manual step with administrator privileges, applied to the installed application bundle, that the user has to find in the documentation and type. Anyone deploying the client to a fleet of Macs has to build that step into the rollout, because an app that will not launch produces a support ticket rather than a feature request. The cause is the signing and notarisation state of the build rather than anything in the code, and nothing in the README indicates whether a future release fixes it. Treat this as a permanent part of the macOS install path until a build ships that opens without it.
The Obsidian and uTools plugins are versioned somewhere else entirely
Two integrations sit outside this repository. The Obsidian plugin downloads from a separate repository, wanglin2/obsidian-simplemindmap, with its own release list. The uTools plugin is listed in the uTools plugin market, searchable by its Chinese name, and installs from the market's launch button rather than from any archive. Neither ships in this tree, so neither shares a version number with the library or the client. The consequence shows up at upgrade time: pulling a new client release tells you nothing about whether the matching Obsidian plugin build exists. If you run the plugin, treat the two repositories as one release train and check both.
The settings surface reaches image hosts, AI services and WebDAV
The headline for the client is local storage, privacy first, data safety, and no need for a network connection. The settings list under that headline is where the tension shows: beyond basic settings, custom fonts, keyboard shortcuts, the context menu and icons, there is an image hosting configuration, an AI configuration and a WebDAV cloud sync configuration. Offline operation and remote services are not contradictory, since a user can leave all three empty and never open the app online. But the behaviour of those three integrations cannot be checked here, because the client source is not published and this README does not describe what the image host uploads, what the AI configuration sends, or how WebDAV handles conflicts. A team evaluating this for documents that must not leave the machine has to treat the local storage claim as the only claim this repository supports.
Editorial conclusion
Use this repository if you are building a web mind map product and want a library with no framework dependency, or if you intend to self-host the Vue2 app behind your own nginx. Do not read the client feature list as a library capability list, since that list describes the client, whose source is not published. Before depending on it, check two things: the simple-mind-map package on npm for the version you would actually install, and the low-maintenance notice, which means the open half is where bugs will accumulate.
Frequently asked questions
how to use mind map in obsidian
An Obsidian plugin is published separately, from wanglin2/obsidian-simplemindmap, and its builds are on that repository's releases page. The plugin is not part of the mind-map repository, so its version does not track the library or the desktop client.
how to use mind map plugin in obsidian
Download the plugin from the releases of the wanglin2/obsidian-simplemindmap repository, which is separate from this one. A uTools version is also listed in the uTools plugin market and installs from there.
How do I self-host the mind-map web app?
The repository ships a Dockerfile that runs nginx, copies index.html and the existing dist directory into /app, and installs the checked-in nginx.conf. It contains no build stage, so the bundle has to exist before you build the image.
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/wanglin2-mind-map)Star history chart for your README
[](https://hysenlabs.com/projects/wanglin2-mind-map)Was this useful?