How dotnetdork/labyrinth works
Labyrinth is a cross-platform host-hardening and incident-response runner. An operator invokes its plan, apply, keep, rollback, runs, or probe commands; the documented core supplies logging, run manifests, safety gates, and scoring-style probes. The README describes a Lock out → Observe → Deceive → Sustain strategy, but says no hardening modules exist yet, and the phase directories contain only placeholders. No source excerpts were provided, so internal call paths are not verified; dashed edges mark the documented-but-unsampled command-to-core relationships.
Main entry points: labyrinth.sh CLI commands · labyrinth.ps1 PowerShell CLI · log.sh Logging · manifest.sh Run manifest
Components 9
Command interface
- CLI commands
labyrinth.sh - PowerShell CLI
labyrinth.ps1
Cross-platform core
- Logging
core/log/log.sh - Run manifest
core/manifest/manifest.sh - Safety gates
core/safety/safety.sh - Scoring probes
core/probe/probe.sh - Configuration
core/config/config.sh
Other components
- Operator
- Managed host
Connections 12
- Operator → CLI commands: runs commands
README.md - Operator → PowerShell CLI: runs commands
README.md - CLI commands → Logging: uses core
- CLI commands → Run manifest: uses core
- CLI commands → Safety gates: uses core
- CLI commands → Scoring probes: runs probes
- PowerShell CLI → Logging: uses core
- PowerShell CLI → Run manifest: uses core
- PowerShell CLI → Safety gates: uses core
- PowerShell CLI → Scoring probes: runs probes
- CLI commands → Managed host: deploys posture
README.md - PowerShell CLI → Managed host: deploys posture
README.md