Project Graph: a node canvas shipped as a Tauri desktop app
A node-based visual tool for organizing thoughts and notes in a non-linear way.
At a glance
- What is it?
- graphif/project-graph is a TypeScript node-based visual tool for organizing thoughts and notes in a non-linear way. The repository tells you more about how it builds than its root README, which only points to ./app/README.md, does, and what sits at the root is worth reading before you install anything.
- Who is it for?
- Adopt Project Graph if you want a node-based visual tool that builds as a Tauri desktop app, and if you can accept a codebase whose permissions are unstated. Skip it if your diagrams must be regenerated by a script or reviewed as text, or if legal will not sign off on code with no stated terms.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly TypeScript, 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
- graphif/project-graph4,536 ★ · +104
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| graphif/project-graph | 4.4k | 4.5k |
104 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
A node canvas for people who outline badly
Project Graph describes itself as a node-based visual tool for organizing thoughts and notes in a non-linear way, and package.json calls it an open-source project that aims to provide a next-generation node diagram tool for visual thinking.
The root README is a single line pointing to ./app/README.md, so features, platforms and audience are not described at the repository root.
nx fans out over a pnpm workspace of app and packages
The repository layout says more than the feature list does. Root entries include app/, packages/, benchmarks/, utils/, docs/, docs-pg/ and pnpm-workspace.yaml, alongside nx.json, a pnpm-lock.yaml and tsconfig.json. This is a monorepo where the editor lives under app/ and shared code sits in packages/, coordinated by nx task targets rather than one monolithic build script.
The npm scripts show the runtime split plainly. The dev script runs the Tauri dev target of the @graphif/project-graph package:
pnpm --filter @graphif/project-graph tauri:devProduction packaging runs the build and tauri:build targets across the workspace:
nx run-many -t build tauri:buildA third target exists for publishing without the Tauri shell, and prepublish runs it before the nx publish fan-out. Desktop and browser bundle are separable at build time, which is what lets the same source produce an npm artifact that is not the app itself.
From clone to running editor, with no install command anywhere
The root README is only a pointer to ./app/README.md, so it carries no install command itself. The project homepage is graphif.dev, and the repository has a CONTRIBUTING.md.
The repository does expose the target surface. With Node and pnpm in place, the lint, format and test entry points are the package scripts, and the test target is unusually specific about ordering:
vitest run --exclude app/src/cli/ProjectGraphCliProduction.test.ts && vitest run app/src/cli/ProjectGraphCliProduction.test.tsIt runs the whole suite with the production CLI test excluded, then runs that one file alone. A second cold-start benchmark target points at the same cli directory, which is a hint that Project Graph ships a command-line surface alongside the canvas rather than only a desktop window.
engines pins Node >=26.0.0 and the gate never opens
package.json requires Node >=26.0.0. This is a floor, not a preference, and it is the first thing to check on a locked-down corporate image or an older CI runner.
The surrounding toolchain moves just as fast. The root package is declared as an ES module and sits at version 1.0.0, while devDependencies reach ESLint 10 and pull TypeScript through a catalog reference. A contributor needs a current Node, not the version many build guides still assume.
The root README itself documents no features, shortcuts or export formats; it only points to ./app/README.md.
The manifest says 1.0.0 while the desktop builds say 4.2.4
Here is the detail a skim misses. The root package.json is version 1.0.0. The desktop builds the project publishes are numbered v4.3.2 and v4.3.1, plus a nightly build cut after both. The npm artifact and the shipped app are plainly on different counters, and nothing in the manifest maps one to the other.
That matters the moment you pin a dependency. Install the npm package expecting the behaviour of the 4.x desktop build and the manifest will tell you 1.0.0, with no hint of which desktop build it corresponds to.
Hand-placed on a canvas versus declared in a text file
The nearest well-known alternative is Graphviz, and the difference is where the diagram lives. Graphviz consumes a declarative text document, the DOT language, and renders it. The graph is reproducible from version control, diffable in review, and regenerated on every build. Project Graph inverts that: the graph lives on a node-based visual canvas rather than in a declarative text file.
That makes them poor substitutes rather than competitors. Graphviz fits when the diagram must be regenerated whenever the underlying model changes, or when a reviewer needs the change as text. Project Graph fits when layout carries meaning, when structure is still being explored, and when the deliverable is a picture someone will look at.
Canvas-based note tools share the second half of the trade. Project Graph's own file layout points elsewhere: the workspace keeps packages/ and benchmarks/ beside the app, and the cold-start benchmark target exists because a local binary has to start fast.
What the repository root does not contain
The top-level entries are .agents/, .cef-build/, .github/, .prettierrc, eslint.config.js, tsconfig.json, AGENTS.md, CONTRIBUTING.md, TODO.md and the workspace directories listed above. There is no LICENSE file among them and no licence identifier is recorded. That is a statement about the repository, not a legal conclusion, but it does mean a company cannot assume the right to modify and redistribute the code, nor the right to withhold it.
Code of conduct and contributing guides exist, which tells you the project wants outside contributors. Permissions are a different document, and that one is absent. Until it appears, treat the code as unavailable for commercial reuse.
Development has not stopped: the last push was on 2026-11-02, and the repository is not archived. Whether that pace suits your roadmap is your call to make from the dates.
Editorial conclusion
Adopt Project Graph if you want a node-based visual tool that builds as a Tauri desktop app, and if you can accept a codebase whose permissions are unstated. Skip it if your diagrams must be regenerated by a script or reviewed as text, or if legal will not sign off on code with no stated terms. Verify two things first: whether the canvas exports anything another tool can read, since the README documents no export format, and who owns the code. Building from source needs Node 26 or newer, so check your own toolchain before promising a date.
Frequently asked questions
Can I use Project Graph in a commercial product?
No LICENSE file exists at the repository root, so the terms are unstated. Treat the code as unavailable until the maintainers publish one.
How do you install Project Graph, and is there an npm command?
The root README only points to ./app/README.md and gives no install command itself. The project homepage is graphif.dev, and the repository has a CONTRIBUTING.md.
What Node version does Project Graph need to build from source?
package.json requires Node >=26.0.0 and the root scripts run through pnpm and nx.
Does Project Graph run on Linux and macOS as well as Windows?
The repository's root README does not list supported platforms; it only points to ./app/README.md. The desktop path is Tauri, driven by the tauri:dev and tauri:build targets in the root package scripts.
What does Project Graph let you draw, and does it have undo?
The repository describes Project Graph as a node-based visual tool for organizing thoughts and notes in a non-linear way; the root README lists no features, so undo support is not documented there.
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/graphif-project-graph)Star history chart for your README
[](https://hysenlabs.com/projects/graphif-project-graph)Was this useful?