Garry Tan 2d10797849 feat(supabase): community-pulse aggregates attack telemetry ...

Adds a `security` section to the community-pulse response:

  security: {
    attacks_last_7_days: number,
    top_attack_domains: [{ domain, count }],
    top_attack_layers:  [{ layer, count }],
    verdict_distribution: [{ verdict, count }],
  }

Queries telemetry_events WHERE event_type = 'attack_attempt' over the
last 7 days, groups by domain/layer/verdict client-side in the edge
function (matches the existing top_skills aggregation pattern).

Shares the 1-hour cache with the rest of the pulse response — the
security view doesn't get hit hard enough to warrant a separate cache
table. Attack data updates once an hour for read-path consumers.

Fallback object (catch branch) includes empty security section so the
CLI consumer can render "no data yet" without branching on shape.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-20 04:58:08 +08:00

..

functions

feat(supabase): community-pulse aggregates attack telemetry

2026-04-20 04:58:08 +08:00

migrations

feat(supabase): schema migration for attack_attempt telemetry fields

2026-04-20 04:58:08 +08:00

config.sh

fix: Supabase telemetry security lockdown (v0.11.16.0) (#460)

2026-03-24 15:01:31 -07:00

verify-rls.sh

fix: verify-rls.sh matches deployed policy (inserts allowed, HTTP parsing) (#461)

2026-03-24 15:10:50 -07:00