| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| neurosploit-v4.4.2-windows-x64.zip | 2026-11-16 | 6.7 MB | |
| neurosploit-v4.4.2-linux-x64.tar.gz | 2026-11-16 | 7.1 MB | |
| neurosploit-v4.4.2-linux-arm64.tar.gz | 2026-11-16 | 7.0 MB | |
| README.md | 2026-11-16 | 1.8 kB | |
| v4.4.2 -- Managed Neo4j and a populated exploration graph source code.tar.gz | 2026-11-16 | 1.5 MB | |
| v4.4.2 -- Managed Neo4j and a populated exploration graph source code.zip | 2026-11-16 | 2.0 MB | |
| Totals: 6 Items | 24.2 MB | 0 | |
- Managed Neo4j.
neurosploit neo4j up|down|status|info|syncstarts a local Neo4j in Docker (ports bound to127.0.0.1only), generates a password, saves the connection to~/.neurosploit/neo4j.json(mode0600) and hands the password to Docker through the environment, never on a command line. Once up, runs use it automatically; an explicit--neo4jorNEO4J_URIalways wins.downkeeps the data and disables auto-use;down --purgedeletes data and the saved connection.docker-compose.neo4j.ymlis provided for those who prefer compose. - Exploration graph in Neo4j. Assets and the exploration graph (goals, intents, facts, negatives, findings, anchors) are MERGEd with closed-enum labels and relationship types; free text only travels as parameters. A chain query surfaces untested assets sitting next to something already broken and injects them into agent prompts as unverified hypotheses.
- The graph is now actually populated. At every graph checkpoint the pipeline writes
graphs/dual-graph.jsonfrom recon (in-scope hosts, subdomains, endpoints, parameters) and findings (intent -> finding with anchors). Idempotent; validation updates status in place; out-of-scope hosts and URLs never enter. - Operator constraints and cold digests are wired into the pipeline (from 4.4.1's modules): extracted constraints reach every recon/exploit prompt and are enforced on recon commands; settled exploration history is folded into digests in the prompt block.
- Web backend.
GET /api/neo4j/status,POST /api/neo4j/up,POST /api/neo4j/down,POST /api/runs/<id>/neo4j-sync.
Known gap: the intent queue, wrap-up and retest modules from 4.4.1 are library-only; their drivers in the agent loop are not wired yet.