penpal-enum 1.0.1

Backend-first enumeration assistant for authorized pentesters.

PenPal

PenPal is a local-first assistant for authorized enumeration. It turns services and tool output into stored evidence, clear next checks, and visible command syntax. The Python core is deterministic; PI is the optional conversational cockpit.

PenPal does not execute exploits, hide commands, use credentials automatically, or provide C2 tasking.

Start With PI

Download a release archive or clone the repository. You need Python 3.11 through 3.13, Node.js 22.19 or newer, and npm.

git clone https://github.com/yousifnazhat/penpal.git
cd penpal
./scripts/setup-pi.sh
pi

On Windows PowerShell, run ./scripts/setup-pi.ps1 instead. The setup script installs the tested PI version when it is missing.

Inside PI, approve project-local files if prompted and run /login when a provider is not configured. Create a target by stating that it is authorized:

Create authorized target 10.10.11.42 named new-box.

Run Nmap or another enumeration tool, then paste its output into the same conversation:

This is Nmap evidence for new-box:

PORT    STATE SERVICE
22/tcp  open  ssh
80/tcp  open  http

PenPal stores the pasted text through its deterministic core, recognizes Nmap service lines, masks sensitive evidence, and returns evidence-backed suggestions. Paste each new result the same way. Run /penpal-status for a provider-free connection check.

PenPal presents one primary next step and up to two alternatives. After a complete pass produces no new supporting evidence, tell PI:

Mark that suggestion exhausted.

PenPal suppresses the path until you explicitly reopen it or its supporting inputs change, preventing the same dead end from being recommended repeatedly.

Other Paths

Connect an MCP client

Use this path when your existing agent supports MCP rather than PI. Install the optional local server, then configure the client to start the shown command over stdio:

python3 -m pip install "penpal-enum[mcp]"
penpal --workspace penpal-workspace mcp

The MCP server exposes seven read-only workflows. It masks sensitive values and does not execute commands or modify your workspace.

Use the Python core only

The core works without PI. Install it and create a target:

python3 -m pip install penpal-enum
penpal doctor
penpal init 10.10.10.5 --name demo
penpal parse-nmap demo ./scan.xml
penpal suggest demo

The release wheel and source archive also include the Python core and bundled playbooks. Add the PI cockpit to a registry installation with:

pi install npm:@yousif_nazhat/penpal-pi

Diagnose setup

penpal doctor
penpal doctor --json

Doctor checks the Python version, playbooks, workspace schemas, scope, plaintext sensitive parameters, missing environment variables, and PI status. It does not modify the workspace. Include the redacted JSON output in bug reports.

What PenPal Does

• Stores scoped targets, services, evidence, parameters, notes, and jobs in a local workspace.
• Parses Nmap XML and ingests pasted or saved tool output.
• Masks credential-like evidence and sensitive parameters by default.
• Uses deterministic suggestions, service modules, and reviewed playbooks to explain the next authorized check.
• Remembers exhausted investigation paths and reopens them when their supporting inputs change.
• Uses environment references for secrets so values are not persisted in workspace JSON.
• Provides a loopback-only JSON API for local integrations.

Everyday Commands

penpal doctor
penpal init <host> --name <name>
penpal scope set --include <host-or-cidr> [--exclude <host-or-cidr>]
penpal parse-nmap <name> <nmap.xml>
penpal ingest <name> --file <output.txt> --source <tool-name> --service <proto/port>
penpal services <name>
penpal evidence <name>
penpal suggest <name>
penpal focus <name> <suggestion-id> exhausted|reopened
penpal context <name> --json
penpal mcp
penpal playbooks playbooks
penpal modules list
penpal modules plan <name> <module>

scan prints commands by default. It runs them only with --execute. Use params set-env for passwords, tokens, and keys; params set keeps sensitive values in local plaintext for compatibility.

Safety

Configure engagement scope before a real assessment. Text pasted into PI is sent to the configured model provider; use an approved or local provider for sensitive engagement data. Keep the local API on its default loopback address. Review every suggested command and remain responsible for authorization. Playbooks require authorized use and operator approval.

Help And Contributing

• Support policy
• Security policy
• Contributing
• Changelog
• Playbook template

Run the contributor checks with:

python3 -m pip install ".[dev]"
python3 scripts/check.py