Skip to main content

Insights

The Insights page provides behavioral analytics derived from the team's scan history — patterns that are difficult to see scan-by-scan but become clear over time.

Navigate here via Insights in the navbar.

Knowledge gaps​

Knowledge gaps identify security rules that consistently appear across the team. A rule that triggers repeatedly across multiple developers and repositories is a pattern — not just individual mistakes.

Use knowledge gaps to prioritize security training. A targeted session on SQL injection is more effective than a generic "write secure code" message.

Scanning activity​

Shows how frequently developers are scanning — daily, weekly, or sporadically. Consistent scanning is a positive behaviour indicator. Long gaps between scans may indicate the git hooks have been bypassed or removed.

Developer breakdown​

Per-developer finding counts, exception rates, and scan frequency. Useful for identifying developers who may benefit from additional support or training — not for blame, but for targeted help.

Filters​

Filter insights by time period (last 30/60/90 days), repository, or individual developer.