Free · Open source

Tools

Every TECHDEV tool in one catalog: free, open-source, inspectable. Clone from GitHub and run it yourself — no accounts, no paywalls.

All tools

21 tools · all free · all on GitHub

Python · CLIFlagshipFree

Before you rent the GPUs, check the map: hardware inventory, memory math, and dated engine-support matrix to pick the right LLM serving engine.

Node · CLIFlagshipFree

The 2-second pre-merge gate for AI-assisted diffs: complexity, duplication and growth checks on changed code only. No model, no account, no network.

Node · CLIFlagshipFree

sessguard: local, read-only, zero-network CLI that inventories AI-assistant session and credential material on your machine and gives you a per-app revocation checklist. Never prints token values.

Node · CLIFlagshipFree

A local, deterministic, read-only behavioral detector for the Gheist planted-workflow attack shape: one command, one verdict per repository, one rotate checklist. No model, no account, no secret values ever printed.

Python · CLIFlagshipFree

Vendor-neutral policy, evidence and credential layer for AI agents: deterministic policy decisions outside the model process, a tamper-evident action ledger, and coverage accounting that fails loudly when an action leaves no record.

Python · CLIFlagshipFree

Open vendor-neutral DevSecOps operating layer: reference architecture, policy-as-code packs, CI security gates and audit-evidence automation for regulated organisations.

Node · CLIFree

Scan a project for things that will break or leak: deprecated deps, EOL runtimes, unpinned CI actions, over-broad permissions, unpinned Docker bases, removed APIs. Zero dependencies.

Python · CLIFree

Map where your API keys actually live — local, read-only auditor for agent-tool configs. Never prints key material, never sends anything anywhere.

Node · CLIFree

Decision memory with provenance: record decisions, facts and constraints as a graph, trace why anything was decided, and catch contradictions and stale dependencies.

How to use a tool

  1. Open the tool on GitHub for install + run + expected output (env-doctor also has a tool page).
  2. Clone from GitHub — code is never gated.
  3. Report bugs on GitHub Issues. For hands-on help, see deployment help.