busker

The project's core functionality involves executing arbitrary commands (`swash run`), which is inherently high-risk, requiring careful input sanitization and execution context control. While WASM components (oxigraph, libvterm) provide sandboxing for those specific libraries, the main Go application itself is not sandboxed. The `systemd` backend leverages robust process management, but relies on correct configuration and the integrity of systemd itself. The custom Go implementation of the journal file format (`pkg/journalfile`), involving low-level binary I/O and hash table management, is complex and could be a source of subtle bugs. The HTTP API (`swash http serve`) and RDF graph service (`swash graph serve`) are potential network attack surfaces if exposed publicly, allowing for unauthorized command execution, SPARQL injection, or resource exhaustion. It is critical to ensure these services are bound to localhost or Unix sockets and secured appropriately for local access only.