TSG is built with a security-first philosophy:

• The monitor never modifies Copilot session files (events.jsonl, session.db, workspace.yaml)
• All session diagnostics are performed by reading file metadata only
• Monitoring does not modify Copilot session files; installation writes only the documented PowerShell profile, Windows Terminal fragment, and per-user URL handler

• TSG directly references Microsoft.Data.Sqlite 10.0.6 and pins SQLitePCLRaw.lib.e_sqlite3 2.1.12 to avoid the vulnerable transitive 2.1.11 release
• All other functionality uses .NET 10 SDK built-in libraries and COM interop
• Supply-chain attack surface is minimal
• Verified via dotnet list package --vulnerable --include-transitive

• Built with AnalysisLevel=latest-all (.NET Roslyn analyzers at maximum strictness)
• NuGetAudit=true with NuGetAuditLevel=low enabled in CI
• CI runs dotnet format --verify-no-changes to enforce code style

• Published via GitHub Actions with --skip-duplicate to prevent version overwriting
• NuGet API key stored as GitHub encrypted secret (NUGET_TSG_API_KEY)
• Packages are signed by NuGet.org's repository signature
• Source link enabled for debuggable builds

• No network access — TSG never makes HTTP calls (except optional Test-Connection in monitor)
• File access limited to:
  • ~/.tsg/ — scripts, config, and SQLite database (read/write)
  • ~/.copilot/session-state/ — session metadata (read-only)
  • ~/.copilotAccel/terminal-snapshots/ — snapshot files (read/write)
  • PowerShell profile — appends a marked block (write, with clean uninstall)
  • Windows Terminal Fragments dir — drops a JSON file (write, with clean uninstall)
  • HKCU\Software\Classes\tsg — per-user URL protocol for clickable session IDs
• Process operations: reads process list via WMI, optionally kills processes (with user confirmation), optionally sets priority (requires Admin/sudo)
• COM access: Uses IUIAutomation COM interface for live window/tab enumeration (read-only)

• Process kill operations always require explicit user confirmation
• Impact analysis is shown before kill: affected child processes, ports released, directories impacted
• Tree-kill uses taskkill /T for safe hierarchical termination
• System processes are excluded from the process list

• SQLite database is local-only at ~/.tsg/terminal.db
• Named mutex (Global\\TSG_DB_MUTEX) prevents concurrent write corruption
• tsg db command is read-only (rejects INSERT/UPDATE/DELETE/DROP/ALTER/CREATE)
• No sensitive data stored — only window titles, tab names, and process metadata

Vulnerability Scan:     ✅ 0 vulnerable packages
Deprecated Packages:    ✅ 0 deprecated packages
Static Analysis (CA):   ✅ 0 security warnings
NuGet Audit:            ✅ Enabled (level: low, mode: all)
Direct Package References: ✅ 2 (SQLite provider + patched native SQLite pin)

• Session links use tsg://resume/<GUID> and are registered only under the current user
• OSC 8 links target generated local launchers in ~/.tsg/session-links/ because some Windows Terminal versions reject custom URI schemes
• The handler invokes the installed tsg executable; it does not invoke a browser or remote endpoint
• Session IDs are validated and the working directory is read from the local workspace.yaml
• Launcher filenames and arguments are derived only from validated GUIDs
• tsg uninstall removes the HKCU\Software\Classes\tsg protocol registration

If you discover a security vulnerability, please report it responsibly:

1. Do NOT open a public GitHub issue
2. Email: Create a private security advisory
3. Include: description, reproduction steps, and impact assessment

We will respond within 48 hours and issue a patch release if confirmed.

Every release is automatically scanned:

# .github/workflows/release.yml
- dotnet list package --vulnerable --include-transitive
- dotnet build with AnalysisLevel=latest-all
- dotnet format --verify-no-changes

GitHub-hosted reports are available from:

• https://github.com/sbay-dev/TerminalStateGuard/actions/workflows/release.yml
• https://github.com/sbay-dev/TerminalStateGuard/actions/workflows/security.yml

The release workflow summary is the authoritative report location. Source-file integrity hashes are committed in SHA256SUMS.txt.