Skip to main content

Nodeprobe

Local CLI security scanner for websites, multi-chain RPC nodes, and EVM smart contracts.

Probe HTTP/TLS, JSON-RPC and GraphQL RPC, and contract posture from your terminal. Local-first for infrastructure you operate or are authorized to assess. No account. No cloud. No telemetry.

pipx install nodeprobe
nodeprobe web https://example.com

Homebrew and Debian/Ubuntu block pip install into system Python. Use pipx or a virtual environment (python3 -m venv .venv && source .venv/bin/activate && pip install nodeprobe). Do not pass --break-system-packages.

Default profile is Standard. Use --profile Quick for a fast pass, or --profile Deep for a larger budget.

What it covers

Surface What Nodeprobe looks at
Web TLS, security headers (presence + HSTS/CSP policy grading), security.txt, robots.txt, server disclosure
RPC Protocol families: EVM, Solana, Substrate/Polkadot, Cosmos, Aptos, Sui, Starknet, NEAR — auto-detect or --family
Contracts EVM code presence, proxies, bytecode heuristics, Sourcify verification (read-only)

EVM networks share one engine. nodeprobe scan <rpc> works for any EVM chain. Chain names come from a bundled Chainlist snapshot; unknown IDs still scan with a generic name.

Quick start

# Website
nodeprobe web https://example.com

# EVM RPC — any EVM chain
nodeprobe scan https://rpc.example.com

# Other protocol families
nodeprobe rpc https://api.mainnet-beta.solana.com
nodeprobe substrate https://rpc.polkadot.io
nodeprobe cosmos https://rpc.cosmos.directory:443
nodeprobe aptos https://fullnode.mainnet.aptoslabs.com/v1
nodeprobe sui https://graphql.mainnet.sui.io/graphql
nodeprobe starknet https://rpc.starknet.lava.build
nodeprobe near https://rpc.mainnet.near.org

# Contract (read-only)
nodeprobe contract 0x… --rpc https://rpc.example.com --chain 1

Human reports are the default. Use --html -o report.html or --json --pretty for other formats.

Safety by design

  • Blocks SSRF paths: private IPs, localhost, cloud metadata
  • Enforces per-profile request, RPS, and duration budgets
  • Kill switch: touch /tmp/nodeprobe-kill or set NODEPROBE_KILL_SWITCH
  • Escalation confirms impact — no exploit payloads, no funded transactions

Authorized use only. Scan systems you own or have permission to assess.

Docs and source

Full examples, screenshots, and development setup: github.com/ehsanhajian/nodeprobe

License

MIT

Release files for nodeprobe 0.1.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for nodeprobe 0.1.4
File Size Uploaded
nodeprobe-0.1.4.tar.gz 129.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for nodeprobe 0.1.4
File Interpreter ABI Platform
nodeprobe-0.1.4-py3-none-any.whl Python 3 none any Details

Total release size: 273.4 kB

Release files / nodeprobe-0.1.4.tar.gz

Download URL nodeprobe-0.1.4.tar.gz
Size 129.5 kB
Tags Source
SHA-256 checksum
How to use checksums
6068b64d8b23f21e595f98ca4da0ca52a93c228b24a45e8c40cfeee8b75d26dd
BLAKE2b-256 checksum
How to use checksums
08f87dd74775349c711c528367b44727c84b263b328ab27d2ab6ac282898e8f0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.

Transparency log

Release files / nodeprobe-0.1.4-py3-none-any.whl

Download URL nodeprobe-0.1.4-py3-none-any.whl
Size 143.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
89905ee61c2b95f61e74c884ce458bfb0020ad819f518e7496d0718067a1b02d
BLAKE2b-256 checksum
How to use checksums
318671b4a763c85f4319e167808012d0f4e41336569183208740ef33a032b282
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.5

2 release files

This release

0.1.4 This release

2 release files

0.1.3

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page