otinstaller 0.0.1__tar.gz

otinstaller-0.0.1/.gitattributes

@@ -0,0 +1 @@
+* text=auto eol=lf

otinstaller-0.0.1/.github/workflows/ci.yml

@@ -0,0 +1,71 @@
+name: CI
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-22.04, ubuntu-24.04]
+        python-version: ["3.10", "3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install dependencies
+        run: pip install -e ".[dev,pipeline]"
+      - name: Ruff check
+        run: ruff check .
+      - name: Ruff format check
+        run: ruff format --check .
+      - name: Run tests
+        run: pytest
+
+  test-debian:
+    # Debian 12 (bookworm) - Kali is Debian-based and covered by this
+    runs-on: ubuntu-24.04
+    container: debian:12
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install system dependencies
+        run: |
+          apt-get update && apt-get install -y python3 python3-venv python3-pip git
+      - name: Create virtualenv
+        run: python3 -m venv .venv
+      - name: Install project
+        run: .venv/bin/pip install -e ".[dev,pipeline]"
+      - name: Ruff check
+        run: .venv/bin/ruff check .
+      - name: Ruff format check
+        run: .venv/bin/ruff format --check .
+      - name: Run tests
+        run: .venv/bin/pytest
+        env:
+          RUN_NETWORK_TESTS: "0"
+
+  test-arch:
+    # Arch Linux
+    runs-on: ubuntu-24.04
+    container: archlinux:latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install system dependencies
+        run: |
+          pacman -Sy --noconfirm python python-pip git
+      - name: Create virtualenv
+        run: python -m venv .venv
+      - name: Install project
+        run: .venv/bin/pip install -e ".[dev,pipeline]"
+      - name: Ruff check
+        run: .venv/bin/ruff check .
+      - name: Ruff format check
+        run: .venv/bin/ruff format --check .
+      - name: Run tests
+        run: .venv/bin/pytest
+        env:
+          RUN_NETWORK_TESTS: "0"

otinstaller-0.0.1/.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

otinstaller-0.0.1/AGENTS.md

@@ -0,0 +1,70 @@
+# otinstaller: project rules
+
+## What this is
+otinstaller is a Python CLI, distributed on PyPI, that installs, runs, updates and
+removes open-source command line tools by name, using one standard command interface.
+It is a neutral tool manager, similar in spirit to pdtm, pipx or Kali's tool packages.
+Tool descriptions, docs and messages stay neutral.
+
+## Fixed decisions (do not change without asking)
+- Package and command name: otinstaller.
+- The word "OSINT" must not appear in the package name, command name or CLI help text.
+  It may appear in the README and the PyPI description only.
+- Python 3.10+. Linux only. Tested on Ubuntu 22.04 and 24.04 with Python 3.10, 3.11, 3.12.
+- Managed tools are installed with pip or git only. No Go, Rust, Node or Docker.
+- Every managed tool gets its own virtualenv. Never install tools into system Python.
+- Run command shape: `otinstaller run <tool> -- <args>`. Arguments pass straight through.
+- Results are saved automatically to ./results/<tool>/<target>/ using the filename
+  pattern <YYYYmmdd-HHMMSS>_<tool>_<target>_<runid>.<ext> plus a .meta.json sidecar.
+  The results directory can be overridden with --output or OTINSTALLER_RESULTS_DIR.
+- One env file holds all API keys: ~/.otinstaller/.env, permissions 600. Each tool only
+  receives the keys it declares in its registry entry.
+- Home directory is ~/.otinstaller/ (override with OTINSTALLER_HOME).
+- The registry is generated by a pipeline. A tool is listed only if it passes an
+  automated install test and a smoke test (--help or --version exits cleanly).
+- Resume: job state lives in SQLite. Finished jobs are skipped on resume and partial
+  output is always kept.
+- No telemetry. Network access only to GitHub, PyPI and the registry host.
+
+## Inclusion policy
+- A tool is listed if it passes install and smoke tests and is not in the denylist.
+- The denylist excludes attack or harassment tooling by capability (phishing kits, IP
+  grabbers, message or call bombers, credential brute-forcers, private-account bypass,
+  dox-dump hosting) and non-OSINT active scanners. It lives in registry/denylist.yaml
+  and can be edited without code changes.
+- Registry entries carry a `capabilities` list. Tools tagged `dual-use` require the
+  responsible-use notice to be accepted before install.
+- The generated list gets a human review before each release.
+
+## Code rules
+- Stack: Typer and Rich for the CLI, PyYAML, and the standard library (sqlite3,
+  subprocess, asyncio, pathlib). Keep dependencies minimal. Ask before adding any.
+- Layout: src/otinstaller/, tests/, docs/, registry/, pipeline/.
+- The CLI layer stays thin. Real logic lives in importable modules so a TUI could
+  reuse it later.
+- Type hints on all function signatures. Lint and format with ruff. Test with pytest.
+- Write the test first, then the code. Every feature needs tests, including failure cases.
+- Never use shell=True. Pass argument lists to subprocess. Validate tool names and
+  targets: no path traversal, no shell metacharacters in filenames.
+- Never log or write API key values anywhere (logs, meta.json, error messages).
+- Metadata is neutral: author "otinstaller contributors". No personal names, emails or
+  local paths anywhere in the repo.
+
+## Style rules (the code should read like an experienced developer wrote it)
+- Comments explain why, not what. Skip comments on obvious code. Most functions need
+  no docstring; add a one-line docstring only where the purpose is not clear from
+  the name.
+- No emojis anywhere: code, comments, README, commit messages, CLI output.
+- No decorative banners, ASCII art, section divider comments, or "generated by" notes.
+- Do not mention AI, assistants or prompts in any file.
+- Keep functions short and names plain. Prefer simple code over clever code.
+- README and docs are written in plain, direct English. No marketing filler, no
+  bullet-point overload, no exclamation marks.
+- Commit messages are short and lowercase, imperative mood, for example
+  "add config module" or "fix path handling in results".
+
+## Workflow
+- After every task run: ruff check ., ruff format --check ., pytest. Report the real output.
+- If a check fails, fix it. If it still fails after 3 attempts, stop and report the
+  problem instead of continuing to change things.
+- Make small commits after each working step. Never leave the repo broken.

otinstaller-0.0.1/CHANGELOG.md

@@ -0,0 +1,52 @@
+# 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).
+
+## [Unreleased]
+
+### Added
+- Typed input prefixes: u: (username), e: (email), p: (phone), d: (domain), url: (URL), q: (query), geo: (coordinates), 	g: (Telegram channel)
+- --all mode for 
+un command: run every installed tool supporting the given input types (-a short form)
+- --include-credentialed flag for --all mode to include tools requiring API credentials
+- check-updates command: read-only check for available updates
+- --tools option for update and check-updates commands (comma-separated tool names)
+- --json output support for all commands
+- --yes / -y flag to skip confirmation prompts on all commands
+- Stable exit codes: 0=success, 1=error, 2=invalid input, 130=interrupted
+- Non-interactive mode detection (CI-friendly)
+- ot command alias alongside otinstaller
+- otinstaller <toolname> bare command shows tool info (same as info)
+- New tools: Blackbird, Telegram Phone Number Checker, Auto Archiver, edgar-tool, instagram-location-search, Telepathy
+- 
+eeds_config field in registry for tools requiring configuration
+- 
+equires_credentials concept for tools with mandatory API keys
+
+### Changed
+- All commands now support --json output
+- All commands respect --yes / -y and non-interactive stdin
+- update command refactored to use shared check logic
+- Registry schema extended with input_types, 
+eeds_config
+
+### Fixed
+- Tool name collision handling (bare tool name vs subcommand)
+- Input type validation for --all mode
+
+## [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 uto command
+- Example output viewer
+- Resume interrupted jobs
+- Doctor diagnostics

otinstaller-0.0.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 otinstaller contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

otinstaller-0.0.1/PKG-INFO

@@ -0,0 +1,193 @@
+Metadata-Version: 2.5
+Name: otinstaller
+Version: 0.0.1
+Summary: Install, run and update command line tools by name
+Author: otinstaller contributors
+License: MIT
+License-File: LICENSE
+Keywords: cli,installer,package-manager,tools
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Requires-Python: >=3.10
+Requires-Dist: click>=8.0.0
+Requires-Dist: pyyaml
+Requires-Dist: rich>=13.8.0
+Requires-Dist: typer==0.27.2
+Provides-Extra: dev
+Requires-Dist: pytest; extra == 'dev'
+Requires-Dist: pytest-asyncio; extra == 'dev'
+Requires-Dist: ruff; extra == 'dev'
+Provides-Extra: pipeline
+Requires-Dist: requests; extra == 'pipeline'
+Description-Content-Type: text/markdown
+
+# OTinstaller
+
+Install, run, update, and remove open-source command line tools by name.
+
+You pick a tool from a list. OTinstaller downloads it into its own folder, runs it, and saves the output. You do not learn a different install method for each tool.
+
+Status: early development. Not published to PyPI yet.
+
+## What you need
+
+A Linux machine. Tested on Ubuntu 22.04 and 24.04, Debian 12, and Arch Linux. Kali Linux is checked by hand before a release.
+
+Python 3.10 or newer, git, and the `venv` module. On Debian, Ubuntu and Kali, install that module with:
+
+```bash
+sudo apt install python3-venv git
+```
+
+Note: Some managed tools do not yet support Python 3.13+. The test matrix covers Python 3.10–3.12. If you encounter install failures on newer Python versions, try running otinstaller in a Python 3.12 virtualenv.
+
+## Install otinstaller
+
+These commands install otinstaller itself. Run them in this repository's folder. A virtualenv is a private Python folder, so this install does not change the Python that came with the system.
+
+```bash
+python3 -m venv .venv
+source .venv/bin/activate
+pip install -e .
+```
+
+`otinstaller` should now be on your path. A new terminal does not keep that. Run `source .venv/bin/activate` again from this folder if the next command says `otinstaller: command not found`.
+
+For system-wide installation, use `pipx install otinstaller` (or `pipx install .` from this directory). This provides the `otinstaller` and `ot` commands on your PATH without a virtualenv.
+
+Check the machine with:
+
+```bash
+otinstaller doctor
+```
+
+`doctor` prints `[ok]` or `[problem]` for Linux, Python, git, and venv. Fix any `[problem]` line before you continue. It often tells you the package to install.
+
+## Run your first tool
+
+`init` creates `~/.otinstaller/` and shows a responsible-use notice. It asks `Do you accept? [y/N]`. Type `y` and press Enter. Nothing can be installed until you do.
+
+```bash
+otinstaller init
+```
+
+Sherlock searches for a username. This install asks `Install? [y/N]`. The capital N means Enter alone means no. Type `y` to continue.
+
+```bash
+otinstaller install sherlock
+otinstaller run sherlock -- someexampleuser123
+```
+
+The `--` marks where otinstaller's own options end. Everything after it is passed to Sherlock. When the run finishes, otinstaller prints a path under `results/` in the folder where you ran the command. That file is the tool's output.
+
+To try a different tool, use its name from the guide in place of `sherlock`.
+
+## Typed inputs
+
+Instead of remembering each tool's flags, you can use typed input prefixes:
+
+- `u:` username (e.g., `u:johndoe`)
+- `e:` email (e.g., `e:john@example.com`)
+- `p:` phone (e.g., `p:+15551234567`)
+- `d:` domain (e.g., `d:example.com`)
+- `url:` URL (e.g., `url:https://example.com`)
+- `q:` text query (e.g., `q:search terms`)
+- `geo:` coordinates (e.g., `geo:32.22,-110.97`)
+- `tg:` Telegram channel (e.g., `tg:channelname`)
+- `lat:` latitude (e.g., `lat:37.7749`)
+- `lng:` longitude (e.g., `lng:-122.4194`)
+
+Example:
+
+```bash
+otinstaller run sherlock -- u:johndoe
+otinstaller run ghunt -- u:johndoe e:john@example.com
+```
+
+Each tool declares which input types it supports. Use `otinstaller info <tool>` to see the mapping.
+
+## All mode
+
+Run every installed tool that supports a given input type:
+
+```bash
+otinstaller run --all u:johndoe
+otinstaller run -a u:johndoe e:john@example.com
+```
+
+Only `u`, `e`, `p`, `d`, and `url` work with `--all`. Tools requiring API credentials are skipped unless `--include-credentialed` is passed.
+
+## Agent-friendly usage
+
+Every command supports `--json` for machine-readable output. Commands never prompt when `--yes` or `-y` is given, or when stdin is not a terminal (CI mode). Exit codes are stable: 0 = success, 1 = error, 2 = invalid input, 130 = interrupted.
+
+Command reference:
+
+- `otinstaller init` — Initialize config and directories
+- `otinstaller install <tool>...` — Install tools
+- `otinstaller remove <tool>...` / `--all` — Remove tools
+- `otinstaller run <tool>... -- <args>` — Run tools
+- `otinstaller run --all u:...` — Run all matching tools
+- `otinstaller info <tool>` — Show tool details
+- `otinstaller list` / `--installed` — List tools
+- `otinstaller search <query>` — Search tools
+- `otinstaller update` / `--all` / `--check-only` — Update tools
+- `otinstaller check-updates` — Check for updates (read-only)
+- `otinstaller auto <target>` — Auto-detect type and run tools
+- `otinstaller example <tool>` — Show example output
+- `otinstaller keys check` — Check API keys
+- `otinstaller resume` — Resume interrupted jobs
+- `otinstaller doctor` — Run diagnostics
+
+For AI agents: see `llms.txt` at the repository root.
+
+## Results
+
+Results are saved automatically to `./results/<tool>/<target>/` using the filename pattern `<YYYYmmdd-HHMMSS>_<tool>_<target>_<runid>.<ext>` plus a `.meta.json` sidecar. The results directory can be overridden with `--output` or `OTINSTALLER_RESULTS_DIR`.
+
+Example:
+
+```
+results/sherlock/testuser/20260929-123456_sherlock_testuser_abc123.txt
+results/sherlock/testuser/20260929-123456_sherlock_testuser_abc123.meta.json
+```
+
+## API keys
+
+One env file holds all API keys: `~/.otinstaller/.env`, permissions 600. Each tool only receives the keys it declares in its registry entry. Use `otinstaller keys check` to verify.
+
+## Resume
+
+If a run or install is interrupted (crash, Ctrl+C, kill), otinstaller keeps a job marker in `~/.otinstaller/jobs/`. Run `otinstaller resume` to detect and handle interrupted jobs:
+
+- For installs: cleans up partial state and retries the install.
+- For runs: reports the interrupted run and prints the command to rerun manually.
+
+Use `otinstaller resume --dry-run` to see what would happen without making changes. Use `--json` for machine-readable output.
+
+Finished jobs are skipped on resume (their marker is removed on completion). Partial output from interrupted runs is always kept in the results directory.
+
+## Dual-use tools and responsible use
+
+Some tools are tagged `dual-use` in the registry. They can be used for legitimate research but also for misuse. Installing a dual-use tool prints a notice and requires confirmation unless `--yes` is given.
+
+The global responsible-use notice is accepted on first `otinstaller init`. You can re-read it with `otinstaller init` any time.
+
+## Python version caveats
+
+Some managed tools do not yet support Python 3.13+. The test matrix covers Python 3.10–3.12. Known affected tools:
+
+- `auto-archiver`: requires Python <3.13 (dependency `pdqhash` needs a C++ compiler, no wheel for 3.13+)
+- `telepathy`: requires Python <3.13 (dependency `googletrans`/`httpx` uses removed `cgi` module)
+
+If you encounter install failures on Python 3.13+, run otinstaller in a Python 3.12 virtualenv.
+
+## License
+
+MIT. See [LICENSE](LICENSE).

otinstaller-0.0.1/README.md

@@ -0,0 +1,164 @@
+# OTinstaller
+
+Install, run, update, and remove open-source command line tools by name.
+
+You pick a tool from a list. OTinstaller downloads it into its own folder, runs it, and saves the output. You do not learn a different install method for each tool.
+
+Status: early development. Not published to PyPI yet.
+
+## What you need
+
+A Linux machine. Tested on Ubuntu 22.04 and 24.04, Debian 12, and Arch Linux. Kali Linux is checked by hand before a release.
+
+Python 3.10 or newer, git, and the `venv` module. On Debian, Ubuntu and Kali, install that module with:
+
+```bash
+sudo apt install python3-venv git
+```
+
+Note: Some managed tools do not yet support Python 3.13+. The test matrix covers Python 3.10–3.12. If you encounter install failures on newer Python versions, try running otinstaller in a Python 3.12 virtualenv.
+
+## Install otinstaller
+
+These commands install otinstaller itself. Run them in this repository's folder. A virtualenv is a private Python folder, so this install does not change the Python that came with the system.
+
+```bash
+python3 -m venv .venv
+source .venv/bin/activate
+pip install -e .
+```
+
+`otinstaller` should now be on your path. A new terminal does not keep that. Run `source .venv/bin/activate` again from this folder if the next command says `otinstaller: command not found`.
+
+For system-wide installation, use `pipx install otinstaller` (or `pipx install .` from this directory). This provides the `otinstaller` and `ot` commands on your PATH without a virtualenv.
+
+Check the machine with:
+
+```bash
+otinstaller doctor
+```
+
+`doctor` prints `[ok]` or `[problem]` for Linux, Python, git, and venv. Fix any `[problem]` line before you continue. It often tells you the package to install.
+
+## Run your first tool
+
+`init` creates `~/.otinstaller/` and shows a responsible-use notice. It asks `Do you accept? [y/N]`. Type `y` and press Enter. Nothing can be installed until you do.
+
+```bash
+otinstaller init
+```
+
+Sherlock searches for a username. This install asks `Install? [y/N]`. The capital N means Enter alone means no. Type `y` to continue.
+
+```bash
+otinstaller install sherlock
+otinstaller run sherlock -- someexampleuser123
+```
+
+The `--` marks where otinstaller's own options end. Everything after it is passed to Sherlock. When the run finishes, otinstaller prints a path under `results/` in the folder where you ran the command. That file is the tool's output.
+
+To try a different tool, use its name from the guide in place of `sherlock`.
+
+## Typed inputs
+
+Instead of remembering each tool's flags, you can use typed input prefixes:
+
+- `u:` username (e.g., `u:johndoe`)
+- `e:` email (e.g., `e:john@example.com`)
+- `p:` phone (e.g., `p:+15551234567`)
+- `d:` domain (e.g., `d:example.com`)
+- `url:` URL (e.g., `url:https://example.com`)
+- `q:` text query (e.g., `q:search terms`)
+- `geo:` coordinates (e.g., `geo:32.22,-110.97`)
+- `tg:` Telegram channel (e.g., `tg:channelname`)
+- `lat:` latitude (e.g., `lat:37.7749`)
+- `lng:` longitude (e.g., `lng:-122.4194`)
+
+Example:
+
+```bash
+otinstaller run sherlock -- u:johndoe
+otinstaller run ghunt -- u:johndoe e:john@example.com
+```
+
+Each tool declares which input types it supports. Use `otinstaller info <tool>` to see the mapping.
+
+## All mode
+
+Run every installed tool that supports a given input type:
+
+```bash
+otinstaller run --all u:johndoe
+otinstaller run -a u:johndoe e:john@example.com
+```
+
+Only `u`, `e`, `p`, `d`, and `url` work with `--all`. Tools requiring API credentials are skipped unless `--include-credentialed` is passed.
+
+## Agent-friendly usage
+
+Every command supports `--json` for machine-readable output. Commands never prompt when `--yes` or `-y` is given, or when stdin is not a terminal (CI mode). Exit codes are stable: 0 = success, 1 = error, 2 = invalid input, 130 = interrupted.
+
+Command reference:
+
+- `otinstaller init` — Initialize config and directories
+- `otinstaller install <tool>...` — Install tools
+- `otinstaller remove <tool>...` / `--all` — Remove tools
+- `otinstaller run <tool>... -- <args>` — Run tools
+- `otinstaller run --all u:...` — Run all matching tools
+- `otinstaller info <tool>` — Show tool details
+- `otinstaller list` / `--installed` — List tools
+- `otinstaller search <query>` — Search tools
+- `otinstaller update` / `--all` / `--check-only` — Update tools
+- `otinstaller check-updates` — Check for updates (read-only)
+- `otinstaller auto <target>` — Auto-detect type and run tools
+- `otinstaller example <tool>` — Show example output
+- `otinstaller keys check` — Check API keys
+- `otinstaller resume` — Resume interrupted jobs
+- `otinstaller doctor` — Run diagnostics
+
+For AI agents: see `llms.txt` at the repository root.
+
+## Results
+
+Results are saved automatically to `./results/<tool>/<target>/` using the filename pattern `<YYYYmmdd-HHMMSS>_<tool>_<target>_<runid>.<ext>` plus a `.meta.json` sidecar. The results directory can be overridden with `--output` or `OTINSTALLER_RESULTS_DIR`.
+
+Example:
+
+```
+results/sherlock/testuser/20260929-123456_sherlock_testuser_abc123.txt
+results/sherlock/testuser/20260929-123456_sherlock_testuser_abc123.meta.json
+```
+
+## API keys
+
+One env file holds all API keys: `~/.otinstaller/.env`, permissions 600. Each tool only receives the keys it declares in its registry entry. Use `otinstaller keys check` to verify.
+
+## Resume
+
+If a run or install is interrupted (crash, Ctrl+C, kill), otinstaller keeps a job marker in `~/.otinstaller/jobs/`. Run `otinstaller resume` to detect and handle interrupted jobs:
+
+- For installs: cleans up partial state and retries the install.
+- For runs: reports the interrupted run and prints the command to rerun manually.
+
+Use `otinstaller resume --dry-run` to see what would happen without making changes. Use `--json` for machine-readable output.
+
+Finished jobs are skipped on resume (their marker is removed on completion). Partial output from interrupted runs is always kept in the results directory.
+
+## Dual-use tools and responsible use
+
+Some tools are tagged `dual-use` in the registry. They can be used for legitimate research but also for misuse. Installing a dual-use tool prints a notice and requires confirmation unless `--yes` is given.
+
+The global responsible-use notice is accepted on first `otinstaller init`. You can re-read it with `otinstaller init` any time.
+
+## Python version caveats
+
+Some managed tools do not yet support Python 3.13+. The test matrix covers Python 3.10–3.12. Known affected tools:
+
+- `auto-archiver`: requires Python <3.13 (dependency `pdqhash` needs a C++ compiler, no wheel for 3.13+)
+- `telepathy`: requires Python <3.13 (dependency `googletrans`/`httpx` uses removed `cgi` module)
+
+If you encounter install failures on Python 3.13+, run otinstaller in a Python 3.12 virtualenv.
+
+## License
+
+MIT. See [LICENSE](LICENSE).

otinstaller-0.0.1/cleanup.sh

@@ -0,0 +1,3 @@
+#!/bin/bash
+cd /home/otinstaller
+git ls-files | grep -E "testtool|test_debug"

otinstaller-0.0.1/docs/DECISIONS.md

@@ -0,0 +1,12 @@
+# Decisions
+
+- The CLI does not apply the denylist at runtime; the registry pipeline applies it before publishing.
+- Virtual environments are created in their final location (tools/<name>/venv/) because venv scripts embed absolute paths.
+- The "commit" column in the state database was renamed to "commit_hash" to avoid SQLite reserved word conflicts.
+- The notice acceptance file (accepted.json) stores the version and timestamp; changing the notice version requires re-acceptance.
+- The .env file permissions are fixed to 600 on init if they are looser.
+- The count line in list and search uses singular "tool" for 1, plural "tools" otherwise.
+- Each tool gets its own virtualenv; no shared environments.
+- Tools run on the same Python that runs otinstaller.
+- otinstaller supports Linux only; install, remove, and run commands check sys.platform and exit with an error on other platforms.
+- airecon passed verification but was deferred from launch because it requires Docker and Ollama, which otinstaller cannot check for yet; revisit once a `requires` field / dependency-check exists in the registry schema.