network-scan

Maps how a codebase connects over the network, including endpoints, protocols, TLS, proxies, and offline behavior.

3|1|Updated Aug 26, 2026
One-click install
npx skills add https://github.com/zeljkoobrenovic/sokrates-skills --skill network-scan-zeljkoobrenovic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: network-scan
Source: https://github.com/zeljkoobrenovic/sokrates-skills/tree/main/skills/scanners/network-scan
Command: npx skills add https://github.com/zeljkoobrenovic/sokrates-skills --skill network-scan-zeljkoobrenovic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Understanding what a codebase connects to, which protocols it speaks, and how it behaves when the network is unavailable requires reading scattered client factories, listeners, and configuration code. This Skill automates that review by scanning the source for connectivity code and producing structured, evidence-backed findings about the network posture of a project. ## Core Features & Use Cases - Endpoint and topology inventory: Identifies what the software listens on and connects to, with direction, default hosts and ports, and opt-in versus default-path classification. - Protocol and connection analysis: Documents HTTP/REST, WebSocket, SSE, gRPC, MCP, and raw socket usage, plus client pooling, timeouts, TLS verification, proxy support, and DNS handling. - Offline and data-in-transit review: Captures connectivity checks, cached fallbacks, startup dependencies on the network, and what data crosses the wire per endpoint class. - Use Case: Point the scanner at a repository with a Sokrates analysis to receive a validated JSON report of findings, a synthesized network posture summary, and a rendered interactive explorer page. ## Quick Start Ask the AI to run the network scan on this repository and report what the software connects to by default and what happens when it cannot reach those endpoints.

Frequently Asked Questions about network-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit what a codebase connects to over the network?

Run the network scan against the source root. It counts HTTP client construction, listeners, URL literals, endpoint env vars, and TLS settings with a deterministic script, then reads the key files to build an endpoint inventory with direction, defaults, and configurability per endpoint class.

How to check if code disables TLS certificate verification?

The scanner flags patterns like danger_accept_invalid_certs, rejectUnauthorized false, verify=False, and InsecureSkipVerify as leads, then reads each site to determine whether verification is disabled on a default path. Disabled verification on a default path is reported as a high-severity finding cross-referenced with the security scan.

Does the network scan work without a Sokrates analysis?

Yes, it degrades gracefully without a _sokrates folder. The counting script and source reading still work standalone, though sibling scanner findings from a Sokrates analysis provide useful cross-references for endpoints, protocols, and reliability findings.

What languages does the network connectivity scanner support?

The counting script covers Rust, Java, Kotlin, Scala, C#, JavaScript, TypeScript, Python, and Go, plus config files like TOML, YAML, JSON, and properties. Test code is excluded by path conventions and, for Rust, inside cfg(test) modules.

What are the limitations of static network analysis?

Static scanning cannot observe runtime behavior such as actual proxy negotiation, DNS resolution results, or dynamically constructed endpoints. Findings describe connectivity as written in code, and retry or backoff policy is delegated to the reliability scanner rather than audited here.