TreeMap
A free, open-source disk-space visualizer. Squarified treemap, duplicate hunting, disk-full forecasting, and cleanup that only ever moves files to the Trash.
Meet Yap. He sits in your menubar and turns red when someone else is talking, and green when it’s your turn. A clock keeps track of how long you’ve yapped.
ProductivityHTML · CSSGitHub @kaeganOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
The marketing site at yapmeter.com. Static Vite site, deploys to Vercel on push to main. The download button links to https://github.com/kaegan/yapmeter/releases/latest/download/Yapmeter.dmg, which GitHub always resolves to the newest release, so the link itself never needs updating.Read the full README ↗
The marketing site at yapmeter.com. Static Vite site, deploys to Vercel on
push to main.
npm install
npm run dev
The download button links to
https://github.com/kaegan/yapmeter/releases/latest/download/Yapmeter.dmg,
which GitHub always resolves to the newest release, so the link itself never
needs updating.
The version shown next to the button (CURRENT_VERSION in src/main.js) is
a string in the source rather than fetched at build time — there's no
build-time dependency on the GitHub API to keep working, and releases are
infrequent enough that a one-line edit is cheaper than the machinery. It is
not updated by hand, though: the release skill in the yapmeter repo
(.claude/skills/release/) bumps it and opens the PR as the last step of
every release, after the GitHub release exists. Four releases shipped with
the site still saying v0.1.2 before that step was made part of the
procedure.