otlite · Username
Install Linkook on Linux or macOS in one command
Linkook starts from a username, finds profiles, then follows the links those profiles publish to discover further accounts and emails. It draws the connections rather than listing flat hits.
Linkook in three lines
pipx install otlite
otlite install linkook
otlite run linkook -- u:jane_doeRuns JackJuly/linkook (MIT, ★ 1k, 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 Linkook is for
- Turning one handle into the set of accounts that link to each other.
- Finding an email published on a profile page.
- Exporting the link graph for a case.
Typed inputs for Linkook
otlite translates these prefixes into Linkook's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- u:
- Username ·
otlite run linkook -- u:jane_doe
Run every installed tool that takes the same input at once: otlite run --all u:jane_doe
Where the results go
Every run lands under ./results/linkook/<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 linkook <target>, and pull indicators out with otlite extract linkook.
Before you run it
- Crawling linked profiles takes longer than a plain username check.
Update, remove, inspect
otlite info linkook # inputs, keys, an example command
otlite example linkook # sample output, where there is one
otlite update linkook # move to the next tested version
otlite remove linkook # delete its virtualenvFull reference: the otlite docs, and the tool's own README on GitHub.
Pairs with
When open-source isn't enough
Linkook follows public links. SearchIn's identity providers add the connections that are not published on the profiles themselves.
FAQ
Linkook with otlite, answered
How do I install Linkook 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 linkook. 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 Linkook take through otlite?
u: (username). otlite maps each prefix to Linkook'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 Linkook results?
Under ./results/linkook/<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 linkook <target> to compare the last two.
Does Linkook 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 Linkook together with other tools?
Yes. otlite run --all u:jane_doe runs every installed tool that takes username input, in parallel, including Linkook. Save the combination as a playbook to repeat it.