Support

Report a problem with the CLI

Email hello@fathohm.dev. There is no public issue tracker yet — the repository is private — so this address is the whole of it, and it is read by the person who wrote the tool.

What to include

One line does most of the work. Both versions matter: the same repository read by two scorer versions is two different readings, so a number without a scorer version cannot be checked.

npx fathohm --version
# fathohm <cli version> (scorer <scorer version>)

Then the command you ran, what it printed, and what you expected instead. If a number looks wrong rather than the tool looking broken, say which number and what you believe it should be — that is the more useful kind of report, and the one hardest to reconstruct without you.

Sending us output cannot leak your code

Worth knowing before you paste anything. The CLI reads git metadata — commit authorship, dates, paths and byte counts — and one file on disk: the .fathohm.toml you wrote yourself. It never opens a file in your source tree, and it makes no network requests, so nothing about your repository leaves your machine unless you send it yourself. Its output contains file paths and author names, and nothing from inside a file.

You do not have to take that on trust: the published README lists every filesystem call in the bundle — six of them, with what each one touches — and it is on the npm page where you can check it against the source in the same tarball.

If a path or a name is itself sensitive, redact it — the arithmetic is reproducible without them.

Reading the source

The published package is not minified, so the tarball is the source. You can read every line of the scoring code without a clone and without an account:

npm pack fathohm
tar -xzf fathohm-*.tgz
less package/dist/fathohm.cjs

The CLI is MIT-licensed. The formula it implements is published in full on the methodology page, constant by constant, so a number you disagree with can be argued with at a specific step rather than in general.

Security

Report anything security-related to the same address with “security” in the subject line, and please do not open it up publicly until it is fixed.