Class too large (too many methods)
− 1 file
🟡 Design / code quality
Duplicate literals − should be constants
− ~7 files
Duplicate / suspicious code blocks
− 1 file
🟢 Minor / low-level issues
Regex improvements
− ~4 files
Redundant / unnecessary code (e.g. temp vars, inherited method)
− ~3 files
🎯 Core systems already work: query planner, buffer cache, storage engine, B-tree indexes, wire protocol (psql connects), JSON/JSONB, window functions, foreign keys, EXPLAIN / EXPLAIN ANALYZE, regex, PL/pgSQL pieces, and standard SQL with transactions, aggregates and joins.
🎯 It acts as a pre-execution firewall: when an agent tries a command, dcg inspects it in sub-millisecond time and either allows it silently or blocks it with a clear explanation safer alternatives
🔧 A three-tier pipeline with SIMD-accelerated quick-reject lets 95% of commands pass in under 10µs — only commands with dangerous keywords hit the expensive regex stage
Replaced article(s) found for cs.FL. https://arxiv.org/list/cs.FL/new
[1/1]:
- Linear Time Subsequence and Supersequence Regex Matching
Antoine Amarilli, Bartlomiej Dudek, Florin Manea, Tina Ringleb, Markus L. Schmid
🧠Bidirectional token-classification — unlike autoregressive LLMs, #PrivacyFilter reads input from both directions simultaneously for deeper context awareness, catching subtle #PII that simple pattern-matching or RegEx rules miss
⚡ 1.5B parameter model with only ~50M active parameters …
âš¡ What triggered it: GitHub rolled out a new token format for GitHub App installation tokens: ghs__. Base64url encoding uses - chars, which Composer's 2021-era regex didn't permit. Any such token would fail validation and leak.
😱 Making it worse: GitHub Actions' secret masker failed to redact the token. Symfony Console wraps error output with ANSI sequences, bypassing masking. Popular actions like shivammathur/setup-php auto-register GITHUB_TOKEN — no special config needed …