otlite · Username
Install Aliens Eye on Linux or macOS in one command
Aliens Eye searches a username across several hundred social sites and reports the matches. Its site list overlaps Sherlock's, so it mostly serves as a cross-check.
Aliens Eye in three lines
pipx install otlite
otlite install aliens-eye
otlite run aliens-eye -- u:jane_doeRuns arxhr007/Aliens_eye (MIT, ★ 4.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 Aliens Eye is for
- A cross-check on Sherlock and Nexfil output.
- Handles on smaller regional sites.
Typed inputs for Aliens Eye
otlite translates these prefixes into Aliens Eye's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- u:
- Username ·
otlite run aliens-eye -- 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/aliens-eye/<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 aliens-eye <target>, and pull indicators out with otlite extract aliens-eye.
Before you run it
- Treat results as leads; the detection rules are community maintained.
Update, remove, inspect
otlite info aliens-eye # inputs, keys, an example command
otlite example aliens-eye # sample output, where there is one
otlite update aliens-eye # move to the next tested version
otlite remove aliens-eye # delete its virtualenvFull reference: the otlite docs, and the tool's own README on GitHub.
Pairs with
FAQ
Aliens Eye with otlite, answered
How do I install Aliens Eye 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 aliens-eye. 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 Aliens Eye take through otlite?
u: (username). otlite maps each prefix to Aliens Eye'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 Aliens Eye results?
Under ./results/aliens-eye/<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 aliens-eye <target> to compare the last two.
Does Aliens Eye 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 Aliens Eye together with other tools?
Yes. otlite run --all u:jane_doe runs every installed tool that takes username input, in parallel, including Aliens Eye. Save the combination as a playbook to repeat it.