Repository Analysis

chrisryugj/korean-law-mcp

법제처 국가법령정보 MCP — 법령·판례·조례 조회부터 인용 환각 검증까지 · Korean law MCP for LLMs

9.9 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of chrisryugj/korean-law-mcp, a TypeScript project with 2,204 GitHub stars. SynthScan v2.0 examined 32,098 lines of code across 135 source files, recording 144 pattern matches distributed across 6 syntactic categories. The overall adjusted score of 9.9 places this repository in the Low AI signal band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

9.9
Adjusted Score
9.9
Raw Score
100%
Time Factor
2026-07-13
Last Push
2.2K
Stars
TypeScript
Language
32.1K
Lines of Code
135
Files
144
Pattern Hits
2026-07-14
Scan Date
0.04
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 6MEDIUM 55LOW 83

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 144 distinct pattern matches across 6 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Decorative Section Separators52 hits · 162 pts
SeverityFileLineSnippetContext
MEDIUMsrc/cli.ts34// ────────────────────────────────────────COMMENT
MEDIUMsrc/cli.ts36// ────────────────────────────────────────COMMENT
MEDIUMsrc/cli.ts184// ────────────────────────────────────────COMMENT
MEDIUMsrc/cli.ts186// ────────────────────────────────────────COMMENT
MEDIUMsrc/cli.ts387// ────────────────────────────────────────COMMENT
MEDIUMsrc/cli.ts389// ────────────────────────────────────────COMMENT
MEDIUMsrc/tools/document-analysis.ts19// ────────────────────────────────────────COMMENT
MEDIUMsrc/tools/document-analysis.ts21// ────────────────────────────────────────COMMENT
MEDIUMsrc/tools/document-analysis.ts30// ────────────────────────────────────────COMMENT
MEDIUMsrc/tools/document-analysis.ts32// ────────────────────────────────────────COMMENT
MEDIUMsrc/tools/annex.ts167// ─── 별표 텍스트 추출 ─────────────────────────────────COMMENT
MEDIUMsrc/tools/annex.ts253// ─── 목록 포맷 (기존 동작) ────────────────────────────COMMENT
MEDIUMsrc/lib/cli-executor.ts14// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-executor.ts16// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-executor.ts28// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-executor.ts30// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-executor.ts60// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-executor.ts62// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-executor.ts182// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-executor.ts184// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/risk-rules.ts7// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/risk-rules.ts9// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/risk-rules.ts109// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/risk-rules.ts111// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/risk-rules.ts136// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/risk-rules.ts138// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/risk-rules.ts320// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/risk-rules.ts322// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/risk-rules.ts351// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/risk-rules.ts353// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/risk-rules.ts424// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/risk-rules.ts426// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/risk-rules.ts507// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/risk-rules.ts509// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/query-router.ts41// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/query-router.ts43// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/query-router.ts80// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/query-router.ts82// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/query-router.ts93// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/query-router.ts95// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/query-router.ts825// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/query-router.ts827// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-format.ts11// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-format.ts13// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-format.ts36// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-format.ts38// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-format.ts69// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-format.ts71// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-format.ts118// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/cli-format.ts120// ────────────────────────────────────────COMMENT
MEDIUMsrc/lib/annex-file-parser.ts14// ─── 기존 인터페이스 호환 ────────────────────────────COMMENT
MEDIUMsrc/lib/annex-file-parser.ts27// ─── 메인 엔트리 ─────────────────────────────────────COMMENT
Structural Annotation Overuse25 hits · 42 pts
SeverityFileLineSnippetContext
LOWdocs/DEVELOPMENT.md118### Step 2: tool-registry.ts???깅줉COMMENT
LOWdocs/DEVELOPMENT.md134### Step 3: 鍮뚮뱶 & ?뚯뒪??COMMENT
LOWsrc/setup.ts262 // Step 1: API 키COMMENT
LOWsrc/setup.ts275 // Step 2: 클라이언트 선택COMMENT
LOWsrc/setup.ts304 // Step 3: 설정 파일 업데이트COMMENT
LOWsrc/tools/chains.ts375 // Step 1: 3단 비교 (요건 체계)COMMENT
LOWsrc/tools/chains.ts379 // Step 2: 해석례 + 판례 + 행정심판 (병렬)COMMENT
LOWsrc/tools/chains.ts441 // Step 1: 판례 + 행정심판 (병렬). 판례는 구조화 hit 기반 상세조회까지 같은 경로에서 처리한다.COMMENT
LOWsrc/tools/chains.ts451 // Step 2: 도메인별 전문 결정례 추가COMMENT
LOWsrc/tools/chains.ts548 // Step 1: 신구대조표COMMENT
LOWsrc/tools/chains.ts552 // Step 2: 조문별 개정 이력 (lawId 필요)COMMENT
LOWsrc/tools/chains.ts609 // Step 2: 조례 검색 — "조례"/"규칙" 제거 (이미 조례 DB에서 검색하므로)COMMENT
LOWsrc/tools/chains.ts614 // Step 3: 상위 1건 전문 자동 조회COMMENT
LOWsrc/tools/chains.ts748 // Step 1: 법령 검색COMMENT
LOWsrc/tools/chains.ts755 // Step 2: 3단 비교 (절차 체계 파악)COMMENT
LOWsrc/tools/chains.ts759 // Step 3: 별표(수수료/과태료) + 서식(신청서) 병렬COMMENT
LOWsrc/tools/chains.ts596 // Step 1: 상위 법령 확인 (조례/지역명은 법령 검색에서 제거)COMMENT
LOWsrc/tools/chains.ts665 // Step 1: AI 검색 + 법령 검색 + 해석례를 병렬 실행하고, 판례는 AI 구조화 신호를 받은 뒤 공통 core로 검색한다.COMMENT
LOWsrc/tools/chains.ts781 // Step 4: AI 검색으로 보완 (절차 상세)COMMENT
LOWsrc/tools/chains.ts817 // Step 1: analyze_document 로 리스크 분석COMMENT
LOWsrc/tools/chains.ts829 // Step 2: 분석 결과에서 searchHints 추출 → 병렬로 법령+판례 검색COMMENT
LOWsrc/tools/scenarios/time-travel.ts149 // Step 1: 연혁 목록 → 두 시점 MST 결정 (페이징으로 전체 회수)COMMENT
LOWsrc/tools/scenarios/time-travel.ts202 // Step 2: 두 시점 본문 raw 조회COMMENT
LOWsrc/tools/scenarios/time-travel.ts234 // Step 3: diffCOMMENT
LOWsrc/tools/scenarios/time-travel.ts237 // Step 4: 출력COMMENT
Verbosity Indicators23 hits · 39 pts
SeverityFileLineSnippetContext
LOWsrc/setup.ts262 // Step 1: API 키COMMENT
LOWsrc/setup.ts275 // Step 2: 클라이언트 선택COMMENT
LOWsrc/setup.ts304 // Step 3: 설정 파일 업데이트COMMENT
LOWsrc/tools/chains.ts375 // Step 1: 3단 비교 (요건 체계)COMMENT
LOWsrc/tools/chains.ts379 // Step 2: 해석례 + 판례 + 행정심판 (병렬)COMMENT
LOWsrc/tools/chains.ts441 // Step 1: 판례 + 행정심판 (병렬). 판례는 구조화 hit 기반 상세조회까지 같은 경로에서 처리한다.COMMENT
LOWsrc/tools/chains.ts451 // Step 2: 도메인별 전문 결정례 추가COMMENT
LOWsrc/tools/chains.ts548 // Step 1: 신구대조표COMMENT
LOWsrc/tools/chains.ts552 // Step 2: 조문별 개정 이력 (lawId 필요)COMMENT
LOWsrc/tools/chains.ts609 // Step 2: 조례 검색 — "조례"/"규칙" 제거 (이미 조례 DB에서 검색하므로)COMMENT
LOWsrc/tools/chains.ts614 // Step 3: 상위 1건 전문 자동 조회COMMENT
LOWsrc/tools/chains.ts748 // Step 1: 법령 검색COMMENT
LOWsrc/tools/chains.ts755 // Step 2: 3단 비교 (절차 체계 파악)COMMENT
LOWsrc/tools/chains.ts759 // Step 3: 별표(수수료/과태료) + 서식(신청서) 병렬COMMENT
LOWsrc/tools/chains.ts596 // Step 1: 상위 법령 확인 (조례/지역명은 법령 검색에서 제거)COMMENT
LOWsrc/tools/chains.ts665 // Step 1: AI 검색 + 법령 검색 + 해석례를 병렬 실행하고, 판례는 AI 구조화 신호를 받은 뒤 공통 core로 검색한다.COMMENT
LOWsrc/tools/chains.ts781 // Step 4: AI 검색으로 보완 (절차 상세)COMMENT
LOWsrc/tools/chains.ts817 // Step 1: analyze_document 로 리스크 분석COMMENT
LOWsrc/tools/chains.ts829 // Step 2: 분석 결과에서 searchHints 추출 → 병렬로 법령+판례 검색COMMENT
LOWsrc/tools/scenarios/time-travel.ts149 // Step 1: 연혁 목록 → 두 시점 MST 결정 (페이징으로 전체 회수)COMMENT
LOWsrc/tools/scenarios/time-travel.ts202 // Step 2: 두 시점 본문 raw 조회COMMENT
LOWsrc/tools/scenarios/time-travel.ts234 // Step 3: diffCOMMENT
LOWsrc/tools/scenarios/time-travel.ts237 // Step 4: 출력COMMENT
Hyper-Verbose Identifiers35 hits · 34 pts
SeverityFileLineSnippetContext
LOWsrc/tools/constitutional-decisions.ts26export async function searchConstitutionalDecisions(CODE
LOWsrc/tools/constitutional-decisions.ts91export async function getConstitutionalDecisionText(CODE
LOWsrc/tools/external-links.ts195function generateInterpretationLinks(interpretationId: string): string {CODE
LOWsrc/tools/impact-map.ts59async function searchPrecedentsWithoutFallback(CODE
LOWsrc/tools/unified-decisions.ts159async function searchPrecedentDecisionsWithText(CODE
LOWsrc/tools/tax-tribunal-decisions.ts23export async function searchTaxTribunalDecisions(CODE
LOWsrc/tools/tax-tribunal-decisions.ts93export async function getTaxTribunalDecisionText(CODE
LOWsrc/tools/applicable-law.ts96function extractTransitionExcerpts(CODE
LOWsrc/tools/precedents.ts61export function renderPrecedentSearchResult(result: StructuredPrecedentSearchResult): string {CODE
LOWsrc/tools/precedents.ts212function normalizeTaxlawBodyCandidate(value: unknown): string {CODE
LOWsrc/tools/precedents.ts363async function fetchHtmlFallbackPrecedent(CODE
LOWsrc/tools/search-detail-chain.ts149export async function fetchCombinedSearchDetailChain(CODE
LOWsrc/tools/institutional-rules.ts178export async function searchPublicInstitutionRules(apiClient: LawApiClient, args: SearchPublicInstitutionRulesInput) {CODE
LOWsrc/tools/institutional-rules.ts184export async function getPublicInstitutionRuleText(apiClient: LawApiClient, args: GetPublicInstitutionRuleTextInput) {CODE
LOWsrc/tools/precedent-evidence.ts132export async function validatePrecedentSearchResult(CODE
LOWsrc/tools/precedent-search-core.ts262export async function searchPrecedentsStructured(CODE
LOWsrc/tools/compact-query-planner.ts165function normalizeOriginalPrecedentQuery(query: string): string {CODE
LOWsrc/tools/compact-query-planner.ts217function extractedOriginalKeywords(originalQuery: string): string[] {CODE
LOWsrc/tools/compact-query-planner.ts373function scoreAiLawArticleCandidate(CODE
LOWsrc/tools/compact-query-planner.ts533function addOriginalQueryCandidate(CODE
LOWsrc/tools/compact-query-planner.ts561function addOriginalKeywordCandidates(CODE
LOWsrc/tools/compact-query-planner.ts666function addDocumentHintCandidates(CODE
LOWsrc/tools/compact-query-planner.ts689function addStructuredAiLawArticleCandidates(CODE
LOWsrc/tools/special-admin-appeals.ts132export async function searchAppealReviewDecisions(apiClient: LawApiClient, args: SearchAppealReviewDecisionsInput) {CODE
LOWsrc/tools/special-admin-appeals.ts139export async function getAppealReviewDecisionText(apiClient: LawApiClient, args: GetAppealReviewDecisionTextInput) {CODE
LOWsrc/tools/chains.ts64function emptyStructuredPrecedentResult(args: SearchPrecedentsInput): StructuredPrecedentSearchResult {CODE
LOWsrc/tools/chains.ts83async function safeSearchPrecedentsStructured(CODE
LOWsrc/tools/chains.ts254function combineStructuredPrecedentResults(CODE
LOWsrc/tools/customs-interpretations.ts30export async function searchCustomsInterpretations(CODE
LOWsrc/tools/customs-interpretations.ts126export async function getCustomsInterpretationText(CODE
LOWsrc/lib/citation-content-matcher.ts86function longestCommonSubstringLen(a: string, b: string): number {CODE
LOWsrc/lib/external-https-proxy.ts28export function getExternalHttpsProxyConfig(): ExternalHttpsProxyConfig | null {CODE
LOWsrc/lib/historical-utils.ts70export async function fetchHistoricalVersionsFull(CODE
LOWsrc/lib/historical-utils.ts125export async function fetchHistoricalVersionsRaw(CODE
LOWsrc/lib/three-tier-parser.ts39function stripLeadingJoHeaderFromContent(content: string): string {CODE
Magic Placeholder Names6 hits · 30 pts
SeverityFileLineSnippetContext
HIGHREADME-EN.md236 "LAW_OC": "your-api-key"CODE
HIGHREADME-EN.md265 "https://korean-law-mcp.fly.dev/mcp?oc=your-api-key"CODE
HIGHREADME-EN.md278 "url": "https://korean-law-mcp.fly.dev/mcp?oc=your-api-key"CODE
HIGHREADME-EN.md302export LAW_OC=your-api-keyCODE
HIGHREADME-EN.md316docker run -e LAW_OC=your-api-key -p 3000:3000 korean-law-mcpCODE
HIGHdocs/DEVELOPMENT.md22LAW_OC=your-api-key node build/index.jsCODE
Modern AI Meta-Vocabulary3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMdocs/FTC-RAG-INTEGRATION.md1# 공정위 결정문 — 로컬 LLM RAG 결합 가이드COMMENT
MEDIUMdocs/FTC-RAG-INTEGRATION.md9### 경로 A: 구조화 텍스트 (`get_decision_text`) ← RAG 메인COMMENT
MEDIUMdocs/FTC-RAG-INTEGRATION.md81## 3. RAG 인덱싱 — 청킹 전략COMMENT