← sources

The paranoid path is the default one, and here are the two leaks we found in our own claim

source: reddit (reddit:selfhosted)published 2026-09-30 15:49ingested 2026-10-01 02:41

retained text

I maintain Veilio. It masks real identifiers in source code before you paste it into an LLM, then puts them back in the answer. `UserAuthService.validateSessionToken` goes out as `__FN__1`, comes home as itself.

I am posting here rather than in a launch sub because the interesting part for this room is the architecture, and because I would rather you find the next hole than a customer does.

**The shape**

* No backend. No database. No account. The web app runs the anonymizer in your browser tab.
* The anonymizer itself is a published npm package with **zero runtime dependencies**. For a tool that reads your source code, the dependency tree is the attack surface, so there isn't one.
* Self-host: `docker run -p 8080:80 ghcr.io/veilio-inc/veilio:latest`, open `localhost:8080`, done. The image is `scratch` plus a static Go server and the built site.
* Every image is published with signed SLSA provenance, so you can check it came from the repo's workflow and not from someone holding a registry token:

​

    gh attestation verify oci://ghcr.io/veilio-inc/veilio:latest --repo veilio-inc/veilio

**The two leaks I found in my own claim**

This is the part I would want to read, so it goes above the feature list.

1. The web app loaded its fonts from Google Fonts. A tool whose entire promise is that nothing leaves your machine was sending every visitor's IP and user-agent to a third party on page load. The fonts are vendored now. Honest cost: 761.5 KB, against the 200 KB I had estimated before measuring.
2. Maps saved from the web app sat in `localStorage` as plain JSON. Your real identifier names, readable in your browser profile, for as long as the profile existed. They are encrypted at rest now, and the plaintext entries older builds left behind are deleted once at startup before the first render. Deliberately no migration: re-encrypting them silently would have needed your key at a moment you had not asked for anything.

Neither of those was reported by a user. Both were found in our own review, which is the only reason I get to tell it this way, and both are why I would rather have this audience than a bigger one.

**What it is not**

Source-available, not OSI open source: free to run, modify and fork inside your own business, not to resell or host as a competing service. If that is a dealbreaker for you, it is a reasonable dealbreaker and I would rather you know now than after you deploy it.

There is a paid hosted edition. It funds this. The anonymizer is the same code in both, and it is the part you can read.

**Ten languages** today: TypeScript/JavaScript, Python, Go, Java, C#, Rust, Ruby, PHP, C and SQL. If yours is missing, that is the contribution that changes who can use the tool, and there is an issue template that asks for a failing case rather than a feature.

Repo and docs in the first comment.

document fetched 2026-10-01 00:33 · canonical https://reddit.com/r/selfhosted/comments/1wu8hbd/the_paranoid_path_is_the_default_one_and_here_are