Skip to content
Back to search

treesheets

MarketplaceWorks with Claude CodeGitHub

Claude Code plugins for TreeSheets

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/aardappel/treesheets with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/aardappel/treesheets'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/aardappel--treesheets/badge.svg)](/listings/aardappel--treesheets)

HTML

<a href="/listings/aardappel--treesheets"><img src="/api/listings/aardappel--treesheets/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Pre-built binaries for Windows, macOS and Linux are available at the [Release section](https://github.com/aardappel/treesheets/releases).

On macOS, drag TreeSheets from the disk image into your Applications folder. The app is not signed with an Apple Developer ID, so macOS blocks it when you first open it. On macOS 15 and later, try to open it once, then go to System Settings > Privacy & Security and click "Open Anyway". On older versions, right-click the app, choose Open, and confirm. Alternatively, run `xattr -dr com.apple.quarantine /Applications/TreeSheets.app` in Terminal. You only need to do this once.

For Linux, there are packages for Debian-based distributions and AppImages (x86_64 and aarch64) that run on most other distributions. To use an AppImage, download it, make it executable (`chmod +x TreeSheets-*.AppImage`) and start it.

Both are built on Ubuntu 22.04, so they need a distribution of about the same age or newer. The Debian packages could also be installed on other Debian-based distributions, depending on whether the required dependency packages are available.

If you use Flatpak, you can install [TreeSheets from Flathub](https://flathub.org/apps/com.strlen.TreeSheets).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  3. "name": "treesheets",
  4. "description": "Claude Code plugins for TreeSheets",
  5. "owner": {
  6. "name": "Wouter van Oortmerssen"
  7. },
  8. "plugins": [
  9. {
  10. "name": "treesheets",
  11. "description": "Drive a running TreeSheets instance over its local agent socket: run Lobster script against the open document and get results back.",
  12. "category": "productivity",
  13. "source": "./"
  14. }
  15. ]
  16. }
README.md · README · 185 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. Welcome to the TreeSheets productivity tool!
  2. ============================================
  3. <p align="center">
  4. <img width="890" alt="TreeSheets on macOS showing a calendar, todo list, projects and research notes as nested grids" src=".github/screenshot-macos.png" />
  5. </p>
  6. [TreeSheets](https://strlen.com/treesheets/) is a "hierarchical spreadsheet" that is a great replacement for spreadsheets, mind mappers, outliners, PIMs, text editors and small databases.
  7. Suitable for any kind of data organization, such as todo lists, calendars, project management, brainstorming, organizing ideas, planning, requirements gathering, presentation of information, etc.
  8. It's like a spreadsheet, immediately familiar, but much more suitable for complex data because it's hierarchical.
  9. It's like a mind mapper, but more organized and compact.
  10. It's like an outliner, but in more than one dimension.
  11. It's like a text editor, but with structure.
  12. Community
  13. ---------
  14. If you like, you are kindly invited to join the [Discord channel](https://discord.gg/HAfKkJz) and
  15. the [Google group](https://groups.google.com/group/treesheets) for discussion. The community maintains a wiki on this [GitHub page](https://github.com/aardappel/treesheets/wiki).
  16. Installation
  17. ------------
  18. Pre-built binaries for Windows, macOS and Linux are available at the
  19. [Release section](https://github.com/aardappel/treesheets/releases).
  20. On macOS, drag TreeSheets from the disk image into your Applications folder. The app is not signed
  21. with an Apple Developer ID, so macOS blocks it when you first open it. On macOS 15 and later,
  22. try to open it once, then go to System Settings > Privacy & Security and click "Open Anyway". On older
  23. versions, right-click the app, choose Open, and confirm. Alternatively, run
  24. `xattr -dr com.apple.quarantine /Applications/TreeSheets.app` in Terminal. You only need to do this once.
  25. For Linux, there are packages for Debian-based distributions and AppImages (x86_64 and aarch64) that run on
  26. most other distributions. To use an AppImage, download it, make it executable
  27. (`chmod +x TreeSheets-*.AppImage`) and start it.
  28. Both are built on Ubuntu 22.04, so they need a distribution of about the same age or newer. The Debian packages could also be
  29. installed on other Debian-based distributions, depending on whether the required dependency packages are available.
  30. If you use Flatpak, you can install [TreeSheets from Flathub](https://flathub.org/apps/com.strlen.TreeSheets).
  31. Source Code
  32. -----------
  33. This repository contains all the files needed to build TreeSheets for various platforms.
  34. ### License
  35. TreeSheets has been licensed under the ZLIB license (see ZLIB_LICENSE.txt).
  36. ![Workflow status](https://github.com/aardappel/treesheets/actions/workflows/build.yml/badge.svg)
  37. ### Structure
  38. `src` contains all source code. The code is dense, terse, and with few comments, typical for a codebase that was never
  39. intended to be used by more than one person (me). On the positive side, you'll find the code very small and simple,
  40. with all functionality easy to find and only in one place (no copy pasting or over-engineering). Enjoy.
  41. `TS` is the folder that contains all user-facing files, typically the build process results in an executable to be put
  42. in the root of this folder, and distributing to users is then a matter of giving them this folder.
  43. `.claude/skills/treesheets-agent` is a skill that lets Claude Code inspect and script the document open in a
  44. running TreeSheets, see `TS/docs/AGENT_SOCKET.md`. Outside this repository, you can install it as a plugin:
  45. ```
  46. /plugin marketplace add aardappel/treesheets
  47. /plugin install treesheets@treesheets
  48. ```
  49. Claude Code doesn't auto-update plugins from third-party marketplaces by default. To get new versions of the
  50. skill automatically, enable it under `/plugin` → Marketplaces → treesheets → Enable auto-update.
  51. Ideas for future features and known bugs are tracked in the [issues](https://github.com/aardappel/treesheets/issues).
  52. Building
  53. --------
  54. This project uses CMake to enable compilation on various platforms and CPack on top of it to package the produced binaries. The build, installation and packaging instructions are within `CMakeLists.txt`.
  55. If you're comfortable with a C++ compiler and CMake, these steps will get you a working build of TreeSheets:
  56. 1. Clone this repository
  57. ```sh
  58. git clone https://github.com/aardappel/treesheets
  59. ```
  60. 2. Change the working directory to the working tree
  61. ```sh
  62. cd treesheets
  63. ```
  64. 3. Configure the build system
  65. ```sh
  66. cmake -S . -B _build -DCMAKE_BUILD_TYPE=Release
  67. ```
  68. On Windows ARM this needs the Visual Studio C++ compiler.
  69. With a Visual Studio generator, open `_build/TreeSheets.sln` after configuring and select
  70. Debug or Release in the IDE. Accept project reloads when CMake regenerates the solution.
  71. 4. Build and package for binary distribution
  72. ```sh
  73. cmake --build _build --target package -j
  74. ```
  75. | Platform | Result |
  76. | -------- | ------ |
  77. | Windows | A ZIP archive for portable usage and an installer |
  78. | macOS | A disk image for Drag and Drop installation |
  79. | Linux | A binary Debian package |
  80. Alternatively, to only build without packaging:
  81. ```sh
  82. cmake --build _build -j
  83. ```
  84. On Windows, append `--config Release`.
  85. 5. Install (optional)
  86. ```sh
  87. cmake --install _build
  88. ```
  89. - **macOS:** append `--prefix <directory>` to specify another installation root for the bundle.
  90. - **Linux:** usually requires root privileges, e.g. run this command with `sudo`.
  91. If you do not have `wxWidgets` installed separately (e.g. as shared library on your distribution or operating system) or want to build it within the TreeSheets CMake project as a static library anyway, add `-DTREESHEETS_BUNDLE_WXWIDGETS=ON` to the build configuration. This builds wxWidgets from source with `wxBUILD_SHARED` and `wxBUILD_INSTALL` set to off, even if an installed wxWidgets is found, so that the wxWidgets libraries are statically linked into TreeSheets and no additional wxWidgets files get installed.
  92. CMake downloads dependencies as needed and reuses them on subsequent builds. Leave
  93. [`FETCHCONTENT_FULLY_DISCONNECTED`](https://cmake.org/cmake/help/latest/module/FetchContent.html#variable:FETCHCONTENT_FULLY_DISCONNECTED)
  94. at its default `OFF`. Setting it to `ON` skips downloads and updates, so adding or changing a dependency
  95. can break an existing build. If CMake reports that a dependency's source directory is missing while
  96. this option is enabled, reset the saved setting (on Windows or any other platform):
  97. ```sh
  98. cmake -S . -B _build -DFETCHCONTENT_FULLY_DISCONNECTED=OFF
  99. ```
  100. This persists in `_build/CMakeCache.txt`; you do not need to repeat it for each build. Use `ON` only
  101. when intentionally reusing already populated dependencies whose versions have not changed.
  102. Translating
  103. -----------
  104. The user interface is translated with [gettext](https://www.gnu.org/software/gettext/). The translations live in
  105. `TS/translations/<language>/ts.po`, and the template they are derived from is `TS/translations/ts.pot`. You need the
  106. gettext tools (`xgettext`, `msgmerge`, `msgfmt`, and `msginit` for new languages), which are usually already present
  107. on Linux and macOS, or see [here](https://mlocati.github.io/articles/gettext-iconv-windows.html) for Windows. After
  108. configuring the build as described above (step 3), the workflow is driven by three CMake targets:
  109. | Step | Command | What it does |
  110. | ---- | ------- | ------------ |
  111. | 1 | `cmake --build _build --target update-pot` | Extracts the translatable strings from the source code into `ts.pot` |
  112. | 2 | `cmake --build _build --target update-po` | Merges the new strings from `ts.pot` into all `ts.po` files |
  113. | 3 | Translate the new (empty or fuzzy) entries in your language's `ts.po`, e.g. with [Poedit](https://poedit.net/) or a text editor | |
  114. | 4 | `cmake --build _build --target update-mo` | Compiles all `ts.po` files into the binary `ts.mo` files the program loads |
  115. Step 1 is normally done by the developer after changing strings in the source code. To add a new language, run this
  116. inside `TS/translations` (replace `lang` with a code like `it`, or `pt_BR`), then continue with step 3:
  117. ```sh
  118. msginit --input ts.pot --locale=lang --output=lang/ts.po
  119. ```
  120. More details can be found in `TS/translations/readme_translations.txt`.
  121. Contributing
  122. ------------
  123. I welcome contributions, especially in the form of neatly prepared pull requests. The main thing to keep in mind when
  124. contributing is to keep as close as you can to both the format and the spirit of the existing code, even if it goes
  125. against the grain of how you program normally. That means not only using the same formatting and naming conventions
  126. (which should be easy), but the same non-redundant style of code (no under-engineering, e.g. copy pasting,
  127. and no over engineering, e.g. needless abstractions).
  128. Also be economic in terms of features: treesheets tries to accomplish a lot with few features, additional user
  129. interface elements (even menu items) have a cost, and features that are only useful for very few people should
  130. probably not be in the master branch. Needless to say, performance is important too. When in doubt, ask me :)
  131. Try to keep your pull requests small (don't bundle unrelated changes) and make sure you've done extensive testing
  132. before you submit, preferrably on multiple platforms.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.