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.5

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.5
File Size Uploaded
nodeprobe-0.1.5.tar.gz 129.6 kB Details

Built distribution (wheel)

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

Total release size: 273.6 kB

Release files / nodeprobe-0.1.5.tar.gz

Download URL nodeprobe-0.1.5.tar.gz
Size 129.6 kB
Tags Source
SHA-256 checksum
How to use checksums
5580037afdbad5ba36712b00e6e0f6b0e2b60eeaa4792d58ce8d9f94e9f9574b
BLAKE2b-256 checksum
How to use checksums
1255b2ce65e2128ba113288759df784610306c5450ab7e1959a5f16b26093692
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.5-py3-none-any.whl

Download URL nodeprobe-0.1.5-py3-none-any.whl
Size 144.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9283b048ccb60031fe693e361e81a94187b42d293b476d41a451c70a8d84384f
BLAKE2b-256 checksum
How to use checksums
14e35b2a15303286ece1be77be17de747066ec0607d4bb8216911928e26591ca
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

This release

0.1.5 This release

2 release files

0.1.4

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