INFYNON

INFYNON is a Rust CLI for three workflow problems:

• package security
• API flow testing
• repo memory & provenance

If your team installs dependencies fast, tests APIs through real workflows, and keeps losing context across branches, PRs, and machines, INFYNON is built for that exact shape of work.

Website: cli.infynon.com

Claude Code companion: d4rkNinja/code-guardian

Good Fit For

• teams doing AI-assisted or high-speed coding
• backend teams testing stateful API workflows
• repos where package ownership and handoff context matter
• developers who want one CLI instead of three disconnected tools

What INFYNON Includes

| Area | Command | Best For | What It Solves | |---|---|---|---| | Package Security | infynon pkg | scanning, safe installs, remediation, monitoring | risky dependencies, invisible installs, version exposure | | API Flow Testing | infynon weave | multi-step API execution and validation | brittle request scripts, missing flow context, runtime probes | | Repo Memory & Provenance | infynon trace | handoffs, package ownership, branch/PR/file/package notes, knowledge graph, TUI inspection | lost context across people, PRs, branches, and machines; invisible entity relationships |

How the workflow fits together

• pkg checks what is entering the system
• weave tests how the real API path behaves
• trace preserves who changed what, why it changed, and what the team knew at the time

Why I Built INFYNON

Most tooling only covers one slice of the workflow.

• dependency scanners tell you what is risky
• API tools let you hit endpoints
• notes and handoffs live in chat, PR comments, or someone's head

That leaves a gap.

Modern teams need one place to:

• inspect dependency risk before it spreads
• test behavior across real request chains
• keep structured repo context visible and queryable

That is why INFYNON is organized into three product areas instead of one overloaded command set.

Recommended With Trace

If you want Trace to feel native inside Claude Code, use code-guardian as the companion layer:

• retrieve the latest Trace context before work starts
• write back team or package notes after work ends
• connect it with Claude Code hooks so the memory flow becomes automatic

Practical setup:

Claude Code + code-guardian + INFYNON Trace

That gives you:

• infynon trace for storage, retrieval, sync, compact, and TUI inspection
• code-guardian for agent-side retrieval and update behavior

Quick Comparison

| Problem | Without INFYNON | With INFYNON | |---|---|---| | Package installs | you install first, inspect later | pkg lets you scan, audit, and control install-time workflows | | API verification | isolated requests miss full behavior | weave models full flows with context threading | | Repo context | provenance gets lost in chat and PR comments | trace keeps it structured, searchable, and inspectable |

Product Areas

infynon pkg

Use pkg when the question is about dependencies.

What it gives you:

• CVE scanning across 14 ecosystems
• secure install wrapper
• audit / why / outdated / diff / doctor / fix / clean / migrate
• scheduled monitoring with Eagle Eye

infynon pkg scan
infynon pkg audit
infynon pkg npm install express --strict high
infynon pkg fix --auto

infynon weave

Use weave when the question is about real API behavior.

What it gives you:

• node-based API flow testing
• context threading between requests
• OpenAPI import
• runtime prompt inputs
• live execution, run diff, and built-in security probes

infynon weave env set BASE_URL http://localhost:8001
infynon weave node create --ai "POST /auth/login extracts token"
infynon weave flow create "checkout" --ai "login then create order"
infynon weave flow run checkout
infynon weave ai probe checkout

infynon trace

Use trace when the question is about repo memory and provenance.

What it gives you:

• Redis for fast live retrieval and session-style coordination
• SQL for durable notes, structured queries, and long-term canonical memory
• canonical / team / user memory layers
• PR / branch / file / package notes with package ownership history
• compaction and reconciliation
• TUI-based inspection, note browsing, and package risk ownership
• first-class integration with the code-guardian Claude Code companion
• branch-wise knowledge graph with entities, edges, and visual TUI
• auto-build graph from git history, notes, and lockfiles
• graph traversal: path finding, impact analysis, orphan detection
• graph diff across branches
• export to JSON and Graphviz DOT, import from JSON

infynon trace init --owner team --user alien
infynon trace source add-sql team-db --engine sqlite --url sqlite://.infynon/trace/trace.db --user alien --default
infynon trace note add repo-handoff --title "Auth changed" --body "Refresh moved into middleware"
infynon trace sync --direction both
infynon trace tui
infynon trace graph build
infynon trace graph show --branch main
infynon trace graph entity add alice --kind person
infynon trace graph edge add --from alice --to src/auth.rs --relation modified_by
infynon trace graph diff main feature/auth
infynon trace graph path CVE-2025-1234 alice
infynon trace graph export --format dot -o graph.dot
infynon trace graph tui

Claude Code companion: d4rkNinja/code-guardian

Head-to-Head Comparison

infynon pkg vs Alternatives

| Feature | infynon pkg | npm audit | Snyk CLI | Socket CLI | OSV-scanner | |---|:---:|:---:|:---:|:---:|:---:| | Secure install wrapper | ✓ | — | — | ~ npm only | — | | 14 ecosystems in one scan | ✓ | — | ~ | ~ | ~ | | Block installs via strict mode | ✓ | — | — | ~ npm only | — | | Scheduled CLI monitoring | ✓ | — | ~ server-side | — | — | | PDF + Markdown report export | ✓ | — | — | — | — | | Package version diff | ✓ | — | — | — | — | | Per-package install decisions | ✓ | — | — | — | — | | Auto-fix / remediation | ✓ | ~ basic | ✓ | ✓ | — | | No SaaS account required | ✓ | ✓ | — | ~ | ✓ |

infynon weave vs Alternatives

| Feature | infynon weave | Postman | Hoppscotch | Bruno | Insomnia | |---|:---:|:---:|:---:|:---:|:---:| | Terminal TUI | ✓ | — | — | — | — | | Runtime prompts (OTP / 2FA) | ✓ | — | ~ | — | — | | Built-in AI security probes | ✓ | — | — | — | — | | AI-assisted flow creation (CLI) | ✓ | ~ GUI only | ~ GUI / alpha | — | — | | Visual flow graph in terminal | ✓ | — | — | — | — | | Run diff (side-by-side) | ✓ | — | — | ~ paid | — | | Context threading between nodes | ✓ | ✓ | ✓ | ✓ | ✓ | | OpenAPI / Swagger import | ✓ | ✓ | ✓ | ✓ | ✓ | | Offline, no account required | ✓ | — | ✓ | ✓ | ~ |

infynon trace vs Alternatives

| Feature | infynon trace | GitHub Wiki | Notion | Confluence | Obsidian | |---|:---:|:---:|:---:|:---:|:---:| | Native CLI | ✓ | — | ~ 3rd party | ~ ACLI | ✓ | | Branch / file / package scoping | ✓ | — | — | — | — | | Package ownership tracking | ✓ | — | — | — | — | | Redis + SQL backend choice | ✓ | — | — | — | — | | Multi-layer memory (team / user / canonical) | ✓ | — | — | — | — | | Terminal TUI inspection | ✓ | — | — | — | — | | Claude Code native integration | ✓ | — | ~ MCP | — | ~ | | Structured retrieval by scope | ✓ | — | — | — | — | | Bidirectional sync via CLI | ✓ | — | ~ | ~ | ✓ | | Branch-wise knowledge graph | ✓ | — | — | — | — | | Auto-build graph from git | ✓ | — | — | — | — | | Graph export (DOT / JSON) | ✓ | — | — | — | — |

✓ = supported · ~ = partial or limited · — = not supported

Knowledge Graph

infynon trace graph adds a branch-wise knowledge graph to Trace.

Entities represent things in your repo (files, packages, people, decisions, vulnerabilities, endpoints). Edges represent relationships between them (depends_on, modified_by, exposes, decided_by, and more).

Each entity and edge is scoped to a branch. You can diff knowledge across branches the same way you diff code.

Auto-Build

infynon trace graph build

Scans git history and existing trace notes to automatically populate the graph with file, person, and note entities and their relationships.

Queries

infynon trace graph show --branch main
infynon trace graph path CVE-2025-1234 alice
infynon trace graph impact src/auth.rs
infynon trace graph orphans
infynon trace graph diff main feature/auth

TUI

infynon trace graph tui

Interactive terminal UI with three views: Entities, Edges, and Visual graph. Supports creating, editing, and deleting entities and edges, switching branches, and auto-building — all from the TUI.

Export / Import

infynon trace graph export --format dot -o graph.dot
infynon trace graph export --format json -o graph.json
infynon trace graph import graph.json --branch imported

Command Style

INFYNON keeps the root command simple:

infynon pkg <subcommand>
infynon weave <subcommand>
infynon trace <subcommand>

Install

npm

npm install -g infynon

Rust (crates.io)

cargo install infynon

Go

go install github.com/d4rkNinja/infynon-cli/go@latest

Linux / macOS

curl -fsSL https://raw.githubusercontent.com/d4rkNinja/infynon-cli/main/scripts/install.sh | bash

Windows

irm https://raw.githubusercontent.com/d4rkNinja/infynon-cli/main/scripts/install.ps1 | iex

Source

cargo install --git https://github.com/d4rkNinja/infynon-cli

Docs

• docs home: cli.infynon.com/docs
• command reference: docs/commands.md
• Trace guide: docs/trace.md
• Weave guide: docs/weave.md
• scan guide: docs/scan.md
• install guide: docs/install.md

Claude Code companion:

• code-guardian

Comparison Blogs

• One CLI vs fragmented tooling
• pkg vs npm audit
• pkg vs Snyk CLI
• pkg vs Socket.dev
• Why Trace exists
• Why repo memory matters

Claude Code companion:

• code-guardian — gives Claude Code a practical Trace bridge