From bd8a7f86c3b5b16d3068edc240e8df49f0572e93 Mon Sep 17 00:00:00 2001 From: styayur Date: Fri, 2 Oct 2026 01:48:18 +0800 Subject: [PATCH] docs: add status badge and roadmap --- README.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/README.md b/README.md index 0770ed3..503b4cf 100644 --- a/README.md +++ b/README.md @@ -6,6 +6,8 @@ **Local-first security investigation for SARIF and scanner findings.** +**Status:** 🟢 Production + [Download](https://github.com/styayur/developer-security-workspace/releases/latest) · [Documentation](docs/architecture.md) · [Demo](docs/demo-workspace.md) · [Discussions](https://github.com/styayur/developer-security-workspace/discussions) [![release](https://img.shields.io/github/v/release/styayur/developer-security-workspace)](https://github.com/styayur/developer-security-workspace/releases/latest) @@ -113,6 +115,29 @@ DSW has no account, telemetry, analytics or cloud storage. External scanners may - Full CodeQL database analysis and Authenticode signing are outside this Preview. - 100k synthetic imports pass locally (about 1.32 GiB peak in a debug test); low-memory profiling and real desktop screenshots remain separate validation work. +## Roadmap + +### Current + +- Stable SARIF 2.1.0 import and the Finding Debugger workflow on Windows. +- Scanner adapters with per-scanner provenance and licensing notes. +- Signed Windows releases with `SHA256SUMS.txt`. + +### Next + +- Broaden scanner-adapter coverage and triage/export formats. +- Resolve the remaining upstream GTK/glib advisory when the Tauri dependency chain allows. + +### Future + +- A documented plugin contract for custom scanners and report converters. +- Linux/macOS packaging for the same investigation workflow. + +### Not planned + +- Cloud or telemetry backends; findings stay local by design. +- Bundling third-party scanners under incompatible licenses. + ## Community - **GitHub Issues** for reproducible bugs and scoped engineering tasks.