I built an LLM-powered compliance scanner that points at the actual line of code
Nikolaos Petridis has developed an open-source compliance scanner called Themida that utilizes LLM technology to analyze code for compliance with regulations like GDPR. The scanner identifies specific lines of code that violate legal standards and provides actionable fixes. It is designed to be more effective than traditional regex methods, offering a more nuanced understanding of code context.
- ▪Themida scans code repositories to identify compliance violations with specific legal articles.
- ▪The scanner runs three passes to ensure accuracy and minimize false positives.
- ▪It is provider-agnostic, allowing users to integrate their own LLM keys.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/nikolaospetridhs/i-built-an-llm-powered-compliance-scanner-that-points-at-the-actual-line-of-code-5d7p |
| Publication time | Sat, 16 May 2026 16:02:43 +0000 |
| Retrieval time | 2026-05-16T16:10:18.986Z |
| Last seen | 2026-05-16T16:10:18.986Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | AYBQLU5y-6Ls |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3934812) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Nikolaos Petridis Posted on May 16 I built an LLM-powered compliance scanner that points at the actual line of code #opensource #llm #gdpr #devtools A few weeks ago I went down a rabbit hole. I'd been reading about how every SaaS company eventually has to deal with GDPR / SOC 2 / HIPAA, and how the existing tooling space basically goes like this: "Do you have a password policy document?" "Yes." "Great, you're compliant." That checks the policy.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
