otlite 1.0.0__tar.gz

otlite-1.0.0/.gitignore

@@ -0,0 +1,35 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.coverage
+htmlcov/
+
+# Virtual environment
+.venv/
+.venv-wsl/
+
+# Results
+results/
+
+# Environment
+.env
+
+# Build
+dist/
+build/
+*.egg-info/
+
+# Pipeline verification outputs
+pipeline/verification_log.jsonl
+registry/generated_registry.yaml
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swocommit_msg.txt

otlite-1.0.0/CHANGELOG.md

@@ -0,0 +1,145 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0] - 2026-10-22
+
+### Changed
+- Renamed to otlite: the PyPI distribution, the import package, the command, the Debian package and the man page. otlite is the no-Docker edition of OTInstaller (https://otinstaller.com); `ot` is the containerised one. The source lives in `otlite/` of the OTInstaller/otinstaller repository
+- The home directory is `~/.otlite` (`OTLITE_HOME`). The first run copies `.env`, `accepted.json` and `crash_reports.json` from `~/.otinstaller` when it exists; tools stay there and are installed again with `otlite install`
+- Environment variables are `OTLITE_HOME`, `OTLITE_RESULTS_DIR`, `OTLITE_REGISTRY`, `OTLITE_NO_BANNER`, `OTLITE_CRASH_REPORTS` and `OTLITE_SENTRY_DSN`. The `OTINSTALLER_*` names are still read when the new one is unset, until 2.0
+- Crash reports name the release `otlite@<version>`
+- The package metadata points at otinstaller.com and the OTInstaller/otinstaller repository
+
+### Added
+- The `otinstaller` distribution on PyPI is now a shim (0.2.0) that depends on otlite and keeps an `otinstaller` command, so `pip install -U otinstaller` keeps working. It prints one line saying the name changed
+
+### Removed
+- The end-of-life notice and `OTINSTALLER_NO_DEPRECATION_WARNING`. otlite is supported; there is no end of life
+- The `ot` command alias, and its man page link. `ot` is the registry's CLI
+
+## [0.1.1] - 2026-10-18
+
+### Fixed
+- `run` crashed with a traceback when it couldn't create `./results` (run from a folder without write access, such as `/`). It now says so and how to pick another folder with `OTINSTALLER_RESULTS_DIR`. Found through a Sentry crash report
+- Pressing Ctrl-C during `run` crashed with a `TypeError` instead of stopping. It now stops with exit code 130 and names the folder that holds the partial output. Found through a Sentry crash report
+- `otinstaller <tool> <something>`, such as `otinstaller sherlock johndoe` or `otinstaller sherlock -x`, crashed with a usage-error traceback. That form only shows the tool's information, so it now says so and prints the `otinstaller run <tool> -- ...` command to use. Command line mistakes are never sent as crash reports. Found through Sentry crash reports
+
+## [0.1.0] - 2026-10-17
+
+### Added
+- Opt-in crash reports through Sentry. Off unless you say yes: `otinstaller init` (or the first `install` on a terminal) asks once and Enter means no; `--yes`, scripts and pipes never turn them on. A report is sent only when otinstaller itself crashes, never for a tool's own failure, and holds the error type, a cleaned message, where in otinstaller's code it happened and the otinstaller, Python and OS versions. Targets, arguments, tool output, results, API keys, file paths, host and user names are never sent. `otinstaller crash-reports on|off` changes it, `DO_NOT_TRACK=1` or `OTINSTALLER_CRASH_REPORTS=off` always turns it off, and `doctor` shows the setting
+- `debian/` packaging, for Kali and other Debian-based distributions
+- Python 3.13 and 3.14 support. Every tool was installed and run on 3.10, 3.12, 3.13 and 3.14; the few that need another Python say so before installing. `doctor` now lists those tools as a note instead of a problem
+- `otinstaller crash-reports test` sends a test report, to check the setup
+- MailAccess harvests a domain's email addresses: `otinstaller run mailaccess d:company.com` runs its `harvest-emails --domain company.com`. `e:` still runs an investigation
+- Registry: `playwright_browsers` downloads a tool's Playwright browser into the tool's own folder, and `input_types` can map a typed input to several words, such as a subcommand and its flag
+
+### Changed
+- License changed from MIT to Apache License 2.0, with a NOTICE file that redistributions and derived works must keep, crediting OSINTverse. Releases up to and including 0.0.4 stay under MIT.
+- `otinstaller install` (and `playbook`) on a terminal now shows the responsible-use notice and asks, the same as `init`, instead of stopping with "run 'otinstaller init' first". Scripts, pipes and `--json` runs still need `otinstaller init --yes`; the notice is never accepted for you
+- `update` and `check-updates` follow the versions this registry pins and tested. Before, they compared pinned PyPI tools with PyPI's newest release, offered an "update", and then reinstalled the same pinned version. A tool whose pin or install method changed in the registry is now offered for update
+- Sublist3r installs from its author's GitHub repository (pinned commit) instead of the PyPI upload, which isn't published by the author. `otinstaller update sublist3r` switches an existing install over
+- New tool virtualenvs upgrade pip before installing anything. If that fails (an offline mirror, say), the bundled pip is used as before
+- Playbooks ship with the package. A `playbooks` folder in the current directory still works and overrides a bundled playbook with the same name
+- `auto` gained `--include-credentialed` and `--type phone`
+- MailAccess 0.18.7 (was 0.18.6), installed with its `browser` extra and Chromium's headless shell, so its browser checks run. Without them MailAccess skipped those checks. The install now downloads about 150 MB more and takes about 450 MB more disk
+- MailAccess no longer adds `investigate` to every run, so `otinstaller run mailaccess -- harvest-emails ...` and its other commands work. Plain arguments now need the command: `otinstaller run mailaccess -- investigate you@example.com`
+- Dependencies: typer `>=0.20,<1` instead of exactly 0.27.2, click `>=8.1`, and sentry-sdk `>=2.0,<3`, so the versions Debian and Kali ship work
+
+### Fixed
+- telegram-phone-number-checker: keys from `~/.otinstaller/.env` now reach the tool. It reads `API_ID`, `API_HASH` and `PHONE_NUMBER`, but the registry declared `TELEGRAM_API_ID` and `TELEGRAM_API_HASH`, so the values were never passed. The keys are optional, because the tool asks for them when they are not set
+- telepathy no longer lists `TELEGRAM_API_ID` and `TELEGRAM_API_HASH` as required. It never read them: it asks for its credentials on the first run and stores them itself, so it is now marked `interactive`
+- telepathy's typed inputs `u:` and `p:` mapped to `--username` and `--phone`, which telepathy doesn't have. It now takes `tg:` (a chat or user), passed as `-t`
+- `run --all` leaves out interactive tools, which would wait for input that a captured run can't give, and tools marked `needs_config` unless `--include-credentialed` is passed
+- `auto` and playbooks gave the target to every tool as a bare argument, so tools that need a flag (theHarvester `--domain`, h8mail `-t`, ctfr `--domain` and others) failed, and `default_args` were dropped. They now pass it the same way as a typed input, choose tools by their typed inputs, and skip the same tools as `run --all`
+- `otinstaller playbook` found no playbooks when otinstaller was installed from PyPI, because the playbooks were only in the git checkout
+- `install --verbose` reported a tool as installed even when a step failed (spiderfoot's requirements on Python 3.13, for example). A failed step now stops the install, as it does without `--verbose`
+- On Python 3.10 with the pip that venv bundles, packages without a `pyproject.toml` (ivre) were installed with a `#!python` first line, so their command couldn't start. Upgrading pip first fixes it
+- `run` crashed with a traceback when a tool's command was missing. It now exits 127 and says to reinstall with `--force`
+- Python version limits for tools that can't install or start outside them: GHunt needs 3.13 or older (its pinned Pillow 10 has no wheels for 3.14), theHarvester needs 3.12+ (its current release requires it), whatsapp-osint needs 3.11+ (it imports `datetime.UTC`), spiderfoot needs 3.12 or older (its pinned lxml and cryptography have no wheels for 3.13). otinstaller now says so before installing, instead of failing in pip
+- dnsgen no longer claims a `d:` input. It reads a file of domains, so `d:example.com` failed; run it as `otinstaller run dnsgen -- domains.txt`
+- edgar-tool's `d:` input passed the domain as a subcommand name, which edgar rejects. `q:` (a text search) is unchanged
+- sitedorks asks a question before opening browser tabs, which was invisible in a captured run. It is now marked `interactive`, so it runs on a terminal
+- The installed-tool contract test never ran a tool: it looked for commands in the wrong folder and treated "not found" as a pass. It now builds each command the way `otinstaller run` does
+- Yes/no prompts showed the default twice (`[y/N] [n]`)
+
+## [0.0.4] - 2026-10-13
+
+### Added
+- `interactive` registry flag: single runs on a terminal use a pseudo-terminal, so login prompts, menus and setup wizards are visible and answerable. `--verbose` on a terminal does the same for any tool. Output is still saved and hashed
+- `run_from_source` registry flag for git scripts that read data files by relative path
+
+### Changed
+- instaloader 4.15.4 and mailaccess 0.18.6, re-verified on Ubuntu 24.04 with Python 3.12
+- The results folder is named after the typed input when there is one, otherwise the first argument that is not a flag, so `-- url:https://example.com --headers` no longer saves under `headers/`
+
+### Fixed
+- ghunt: `ot run ghunt -- login` runs `ghunt login` again; `e:` maps to the `email` subcommand instead of a default argument that was added to every run
+- blackbird runs from its checkout, so it finds `data/wmn-data.json` from any directory
+- dnstwist installs with its `[full]` extras (DNS, WHOIS, GeoIP, fuzzy hashing)
+- osint-brazuca-regex requires Python 3.12+, so install stops early on 3.10 and 3.11 instead of failing at run time
+- auto-archiver no longer warns that Google keys are required; they are optional
+- Values of credential flags such as `--cookie`, `--token`, `--password` and `--api-hash` are written as `***` in `.meta.json` and never used to name the results folder
+- `extra_packages` accepts `==`, `>=`, `<=`, `!=` and `~=` version operators
+
+## [0.0.3] - 2026-10-12
+
+### Added
+- Contact email and OSINTverse social links in the README and `otinstaller about`
+- README tool catalogue, generated from the registry, plus a why section, FAQ, docs link and launch video
+
+### Changed
+- user-scanner 1.5.2.2, linkook 1.1.3, aliens-eye 2.7.0 and mailaccess 0.18.5, each re-verified on Ubuntu 24.04 with Python 3.12
+- blackbird now installs from its new home, antoniaci/blackbird; Telepathy points to prose-intelligence-ltd/Telepathy-Community
+
+### Fixed
+- mailaccess runs `mailaccess --no-banner investigate <email>`; the old `--email` flag no longer exists, and 0.18.5 fixes the missing greenlet dependency
+
+## [0.0.2] - 2026-10-11
+
+### Added
+- Startup banner for init, about, and a bare invocation
+- `requires_python` on registry entries, with install failing early when the interpreter is too old
+- `long_running` flag so whatsapp-osint and instagram-monitor are left out of `--all` and auto
+
+### Changed
+- README rewritten for the PyPI page, with absolute links and project URLs
+- pyyaml pinned to 6.0.3 and ruff pinned to 0.16.10
+
+### Fixed
+- Registry input types and entrypoints for ghunt, theharvester, bbot, linkook, spiderfoot, ignorant, aliens-eye, telepathy, and neutrosint
+- Git-installed tools pinned to full commit SHAs
+- Removed the fabricated ghunt example output
+- Interrupted runs print the real output path
+- Result folders use the typed input value when no other target name is available
+
+## [0.0.1] - 2026-09-29
+
+### Added
+- Initial release
+- Basic tool management: install, remove, run, update, list, search, info
+- Parallel tool execution with configurable concurrency
+- Result storage with metadata and SHA256
+- API key management via ~/.otinstaller/.env
+- Responsible use notice on first run
+- Auto-detect target type with the auto command
+- Example output viewer
+- Resume interrupted jobs
+- Doctor diagnostics
+- Typed input prefixes: u: (username), e: (email), p: (phone), d: (domain), url: (URL), q: (query), geo: (coordinates), tg: (Telegram channel)
+- `--all` mode for the run command
+- `--include-credentialed` flag for `--all`
+- check-updates command
+- `--tools` option for update and check-updates
+- `--json` output and `--yes` / `-y` on commands
+- Stable exit codes: 0 success, 1 error, 2 invalid input, 130 interrupted
+- `ot` command alias
+- Tools added for that release: Blackbird, Telegram Phone Number Checker, Auto Archiver, edgar-tool, instagram-location-search, Telepathy
+
+### Fixed
+- Tool name collision between a bare tool name and a subcommand
+- Input type validation for `--all`

otlite-1.0.0/LICENSE

@@ -0,0 +1,176 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

otlite-1.0.0/NOTICE

@@ -0,0 +1,15 @@
+OTinstaller
+Copyright 2026 OSINTverse
+
+Created by Sushant Koul and Dheeraj Yadav at OSINTverse.
+https://github.com/OSINTVerseHQ/OTinstaller
+
+Licensed under the Apache License, Version 2.0 (see LICENSE).
+
+If you redistribute OTinstaller or a work based on it, Section 4(d) of the
+license requires you to keep the attribution notices in this NOTICE file with
+your copy. Please credit it as "OTinstaller by OSINTverse" and link to the
+repository above.
+
+OTinstaller installs and runs third-party open-source tools. Those tools are
+not part of OTinstaller and keep their own licenses.