otlite · Username
Install user-scanner on Linux or macOS in one command
user-scanner takes a username or email and checks platforms that reveal whether an account exists. It groups results by category and ships an MCP server, so agents can call it too.
user-scanner in three lines
pipx install otlite
otlite install user-scanner
otlite run user-scanner -- u:jane_doeRuns kaifcodec/user-scanner (MIT, ★ 5k, otlite 1.2.1, catalog updated Oct 23, 2026). otlite installs and runs it at a tested version; it does not change or verify the tool itself.
What user-scanner is for
- One run for both a handle and the email behind it.
- Agent workflows: the same checks over MCP.
- A second source next to Sherlock and Holehe.
Typed inputs for user-scanner
otlite translates these prefixes into user-scanner's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- u:
- Username ·
otlite run user-scanner -- u:jane_doe - e:
- Email ·
otlite run user-scanner -- e:jane@example.com
Run every installed tool that takes the same input at once: otlite run --all u:jane_doe
otlite marks it dual-use, so it asks you to accept a responsible-use notice before it installs.
Where the results go
Every run lands under ./results/user-scanner/<target>/ as a timestamped output file, a .meta.json sidecar (the exact command, start and end time, exit code, and the SHA-256 of the output), and a .envelope.json with the entities found, in the same shape for every tool. List runs with otlite results, group them with --case, compare the last two with otlite diff user-scanner <target>, and pull indicators out with otlite extract user-scanner.
Before you run it
- otlite never runs it with --allow-loud, which would notify the target.
Update, remove, inspect
otlite info user-scanner # inputs, keys, an example command
otlite example user-scanner # sample output, where there is one
otlite update user-scanner # move to the next tested version
otlite remove user-scanner # delete its virtualenvFull reference: the otlite docs, and the tool's own README on GitHub.
Pairs with
When open-source isn't enough
user-scanner says which accounts exist. SearchIn's identity and leak providers return what those accounts reveal.
FAQ
user-scanner with otlite, answered
How do I install user-scanner on Kali, Ubuntu, or macOS?
Install otlite once with pipx install otlite (or the one-line installer on the otlite page), run otlite init, then otlite install user-scanner. The tool lands in its own virtualenv under ~/.otlite/, pinned to a version that was tested, so nothing touches your system Python. otlite doctor prints the command that fixes a missing git or venv module.
Which inputs does user-scanner take through otlite?
u: (username), e: (email). otlite maps each prefix to user-scanner's own flag. Everything after -- that is not a typed input is passed through unchanged, so the original flags still work.
Where does otlite save user-scanner results?
Under ./results/user-scanner/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar (the exact command, timing, exit code, and SHA-256) and a .envelope.json with the entities found. Add --case <name> to group runs, otlite results to list them, and otlite diff user-scanner <target> to compare the last two.
Does user-scanner need an API key or a login?
No key is required for the basic run. Optional keys, where the project supports them, go in with otlite keys set NAME and are passed only to tools that declare them.
Can I run user-scanner together with other tools?
Yes. otlite run --all u:jane_doe runs every installed tool that takes username input, in parallel, including user-scanner. Save the combination as a playbook to repeat it.