Why
Teams running KShield across multiple repos/machines have no shared visibility into what's being caught or suppressed — everything lives in each developer's local SQLite history. A periodic digest posted to Slack/Discord (via webhook) would give a team-level view without standing up shared infrastructure.
Proposed scope
- Small standalone script/cron (or optional backend background task) that:
- Reads recent scans via the existing
GET /api/v1/scans history endpoint.
- Formats a digest (new findings, suppressed count, critical/high highlights) and posts to a configured Slack or Discord webhook URL.
- Config via env var (webhook URL, digest frequency) — no new backend endpoints needed since
/api/v1/scans already returns what's required.
Priority note
Lowest priority of the five — nice-to-have, not a driver of adoption. Reasonable to pick up opportunistically or leave for community contribution.
Why
Teams running KShield across multiple repos/machines have no shared visibility into what's being caught or suppressed — everything lives in each developer's local SQLite history. A periodic digest posted to Slack/Discord (via webhook) would give a team-level view without standing up shared infrastructure.
Proposed scope
GET /api/v1/scanshistory endpoint./api/v1/scansalready returns what's required.Priority note
Lowest priority of the five — nice-to-have, not a driver of adoption. Reasonable to pick up opportunistically or leave for community contribution.