| Version | Supported |
|---|---|
| latest | Yes |
If you discover a security vulnerability in gig, please report it responsibly:
- Do not open a public GitHub issue for security vulnerabilities.
- Open a private security advisory on GitHub with:
- A description of the vulnerability
- Steps to reproduce
- Impact assessment
- You should receive a response within 72 hours.
- Once confirmed, a fix will be developed and released as a patch version.
gig is a local-first task management tool. The primary attack surface is:
- SQLite database: Stored locally at
~/.gig/gig.db. No network exposure by default. - Web UI (
gig ui): Binds tolocalhost:9741by default. No authentication — do not expose on untrusted networks without a reverse proxy with auth. - Shell hooks: Commands in
gig.yamlare executed as the current user. Treatgig.yamlas executable configuration — do not accept untrusted config files. - JSONL import:
gig importperforms upserts. Malformed JSONL could corrupt task data but cannot execute code.
- No CGO: Pure Go binary with no native dependencies reduces supply chain risk.
- No network by default: The CLI operates entirely on local files. Only
gig uiandgig syncinvolve network activity. - Parameterized SQL: All database queries use parameterized statements (no string interpolation).
- FK constraints: Foreign key enforcement prevents orphaned data.