Executive summary
google/langextract falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 69 out of 100 and is rated Adequate, and all 14 of its critical findings are security problems in the build pipeline and in its servers and containers.
Production Readiness, at 60, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 8 points. Recording design decisions comes next, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 73.
Eleven pipeline steps install packages that can change without warning. Two secrets can leak from the build pipeline, and one setting leaves the servers or containers unsafe. Pinning what the pipeline installs, limiting each secret to its own step and correcting the unsafe settings would close these risks.
The product code is 15,187 lines, about €48,000 to rebuild.
If Production Readiness rose from 60 to 70, the lowest score rated Strong, the score would rise from 69 to about 73.
New since the last survey: 4 findings
- Cyclomatic Complexity · OpenAILanguageModel._build_chat_completions_params (cyclomatic 16) langextract/providers/openai.py
- Cognitive Complexity · OpenAILanguageModel._build_chat_completions_params (cognitive 16) langextract/providers/openai.py
- Code Duplication · Edited copy of a member (27 corresponding lines) langextract/providers/schemas/gemini.py
- Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) langextract/_compat/inference.py
Fixed since the last survey: 30 findings
- Cyclomatic Complexity · validate_community_providers.validate (cyclomatic 28) scripts/validate_community_providers.py
- Cognitive Complexity · validate_community_providers.validate (cognitive 39) scripts/validate_community_providers.py
- God Classes · FileTooLong: scripts/create_provider_plugin.py scripts/create_provider_plugin.py
- Code Duplication · Duplicated block (18–31 lines × 2) langextract/_compat/inference.py
- Code Duplication · Duplicated block (21 lines × 2) langextract/providers/schemas/gemini.py
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/auto-update-pr.yaml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/check-infrastructure-changes.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/check-linked-issue.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/check-pr-size.yml
- Static Analysis (SAST) · High: github-script-injection .github/workflows/check-pr-size.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/check-pr-size.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/check-pr-up-to-date.yaml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/check-pr-up-to-date.yaml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/revalidate-pr.yml
- Static Analysis (SAST) · High: github-script-injection .github/workflows/revalidate-pr.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/revalidate-pr.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/revalidate-pr.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/revalidate-pr.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/revalidate-pr.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/validate-community-providers.yaml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/validate-community-providers.yaml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/validate_pr_template.yaml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Supply-chain Provenance & Signing · Unpinned build actions
- Exception handling · Swallowed exception (caught, then discarded) scripts/create_provider_plugin.py
- Exception handling · Swallowed exception (caught, then discarded) scripts/create_provider_plugin.py
Rebuild cost: about €48,000 · Estimate
| Cost to rebuild | €16,000 to €80,000, for 266 to 842 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.0 at a score of 69. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 15,187 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 .github.scripts.pr_security_check | 3 docs._static | 4 langextract._compat | 5 langextract._compat.inference | 6 langextract.core.base_model | 7 langextract.core.exceptions | 8 langextract.core.format_handler | 9 langextract.core.types | 10 langextract.factory | 11 langextract.prompt_validation | 12 langextract.providers.builtin_registry | 13 langextract.providers.gemini_batch | 14 langextract.providers.openai_batch | 15 langextract.providers.router | 16 langextract.providers.schemas | 17 scripts | 18 .github.scripts | 19 langextract.core.schema | 20 langextract.core.tokenizer | 21 langextract.io | 22 langextract.providers | 23 langextract.providers.gemini | 24 langextract.providers.ollama | 25 langextract.providers.openai | 26 langextract.core | 27 langextract.core.data | 28 langextract.providers.schemas.gemini | 29 langextract.providers.schemas.openai | 30 langextract.chunking | 31 langextract.prompting | 32 langextract.resolver | 33 langextract.visualization | 34 langextract | 35 langextract.annotation |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | |||||||||||||||||||||||||||||||||||
| 2 .github.scripts.pr_security_check | |||||||||||||||||||||||||||||||||||
| 3 docs._static | |||||||||||||||||||||||||||||||||||
| 4 langextract._compat | |||||||||||||||||||||||||||||||||||
| 5 langextract._compat.inference | |||||||||||||||||||||||||||||||||||
| 6 langextract.core.base_model | |||||||||||||||||||||||||||||||||||
| 7 langextract.core.exceptions | |||||||||||||||||||||||||||||||||||
| 8 langextract.core.format_handler | |||||||||||||||||||||||||||||||||||
| 9 langextract.core.types | |||||||||||||||||||||||||||||||||||
| 10 langextract.factory | |||||||||||||||||||||||||||||||||||
| 11 langextract.prompt_validation | |||||||||||||||||||||||||||||||||||
| 12 langextract.providers.builtin_registry | |||||||||||||||||||||||||||||||||||
| 13 langextract.providers.gemini_batch | |||||||||||||||||||||||||||||||||||
| 14 langextract.providers.openai_batch | |||||||||||||||||||||||||||||||||||
| 15 langextract.providers.router | |||||||||||||||||||||||||||||||||||
| 16 langextract.providers.schemas | |||||||||||||||||||||||||||||||||||
| 17 scripts | |||||||||||||||||||||||||||||||||||
| 18 .github.scripts | 1 | ||||||||||||||||||||||||||||||||||
| 19 langextract.core.schema | 1 | 1 | |||||||||||||||||||||||||||||||||
| 20 langextract.core.tokenizer | 1 | ||||||||||||||||||||||||||||||||||
| 21 langextract.io | 1 | ||||||||||||||||||||||||||||||||||
| 22 langextract.providers | 1 | 1 | |||||||||||||||||||||||||||||||||
| 23 langextract.providers.gemini | 1 | 1 | |||||||||||||||||||||||||||||||||
| 24 langextract.providers.ollama | 1 | 1 | |||||||||||||||||||||||||||||||||
| 25 langextract.providers.openai | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 26 langextract.core | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||
| 27 langextract.core.data | 2 | ||||||||||||||||||||||||||||||||||
| 28 langextract.providers.schemas.gemini | 1 | 1 | |||||||||||||||||||||||||||||||||
| 29 langextract.providers.schemas.openai | 1 | 1 | |||||||||||||||||||||||||||||||||
| 30 langextract.chunking | 1 | 5 | 1 | ||||||||||||||||||||||||||||||||
| 31 langextract.prompting | 1 | 1 | |||||||||||||||||||||||||||||||||
| 32 langextract.resolver | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 33 langextract.visualization | 1 | ||||||||||||||||||||||||||||||||||
| 34 langextract | 1 | 1 | 1 | 3 | 3 | 3 | 1 | 1 | |||||||||||||||||||||||||||
| 35 langextract.annotation | 1 | 1 | 1 | 1 |
18→2 .github.scripts uses .github.scripts.pr_security_check✕
- Connections
- 1 pair of types, where a type in .github.scripts uses a type in .github.scripts.pr_security_check.
- The types involved
.github.scripts.pr_security_check→.github.scripts.pr_security_check.FileDiff
- Direction
- .github.scripts uses .github.scripts.pr_security_check, so a change to .github.scripts.pr_security_check can break .github.scripts, while a change to .github.scripts can't break .github.scripts.pr_security_check.
- Position
- Below the diagonal: .github.scripts uses a module listed above it, which is the healthy direction.
19→8 langextract.core.schema uses langextract.core.format_handler✕
- Connections
- 1 pair of types, where a type in langextract.core.schema uses a type in langextract.core.format_handler.
- The types involved
langextract.core.schema.BaseSchema→langextract.core.format_handler.FormatHandler
- Direction
- langextract.core.schema uses langextract.core.format_handler, so a change to langextract.core.format_handler can break langextract.core.schema, while a change to langextract.core.schema can't break langextract.core.format_handler.
- Position
- Below the diagonal: langextract.core.schema uses a module listed above it, which is the healthy direction.
19→9 langextract.core.schema uses langextract.core.types✕
- Connections
- 1 pair of types, where a type in langextract.core.schema uses a type in langextract.core.types.
- The types involved
langextract.core.schema.FormatModeSchema→langextract.core.types.FormatType
- Direction
- langextract.core.schema uses langextract.core.types, so a change to langextract.core.types can break langextract.core.schema, while a change to langextract.core.schema can't break langextract.core.types.
- Position
- Below the diagonal: langextract.core.schema uses a module listed above it, which is the healthy direction.
20→7 langextract.core.tokenizer uses langextract.core.exceptions✕
- Connections
- 1 pair of types, where a type in langextract.core.tokenizer uses a type in langextract.core.exceptions.
- The types involved
langextract.core.tokenizer.BaseTokenizerError→langextract.core.exceptions.LangExtractError
- Direction
- langextract.core.tokenizer uses langextract.core.exceptions, so a change to langextract.core.exceptions can break langextract.core.tokenizer, while a change to langextract.core.tokenizer can't break langextract.core.exceptions.
- Position
- Below the diagonal: langextract.core.tokenizer uses a module listed above it, which is the healthy direction.
21→7 langextract.io uses langextract.core.exceptions✕
- Connections
- 1 pair of types, where a type in langextract.io uses a type in langextract.core.exceptions.
- The types involved
langextract.io.InvalidDatasetError→langextract.core.exceptions.LangExtractError
- Direction
- langextract.io uses langextract.core.exceptions, so a change to langextract.core.exceptions can break langextract.io, while a change to langextract.io can't break langextract.core.exceptions.
- Position
- Below the diagonal: langextract.io uses a module listed above it, which is the healthy direction.
22→13 langextract.providers uses langextract.providers.gemini_batch✕
- Connections
- 1 pair of types, where a type in langextract.providers uses a type in langextract.providers.gemini_batch.
- The types involved
langextract.providers.gemini_batch→langextract.providers.gemini_batch.BatchConfig
- Direction
- langextract.providers uses langextract.providers.gemini_batch, so a change to langextract.providers.gemini_batch can break langextract.providers, while a change to langextract.providers can't break langextract.providers.gemini_batch.
- Position
- Below the diagonal: langextract.providers uses a module listed above it, which is the healthy direction.
22→14 langextract.providers uses langextract.providers.openai_batch✕
- Connections
- 1 pair of types, where a type in langextract.providers uses a type in langextract.providers.openai_batch.
- The types involved
langextract.providers.openai_batch→langextract.providers.openai_batch.BatchConfig
- Direction
- langextract.providers uses langextract.providers.openai_batch, so a change to langextract.providers.openai_batch can break langextract.providers, while a change to langextract.providers can't break langextract.providers.openai_batch.
- Position
- Below the diagonal: langextract.providers uses a module listed above it, which is the healthy direction.
23→6 langextract.providers.gemini uses langextract.core.base_model✕
- Connections
- 1 pair of types, where a type in langextract.providers.gemini uses a type in langextract.core.base_model.
- The types involved
langextract.providers.gemini.GeminiLanguageModel→langextract.core.base_model.BaseLanguageModel
- Direction
- langextract.providers.gemini uses langextract.core.base_model, so a change to langextract.core.base_model can break langextract.providers.gemini, while a change to langextract.providers.gemini can't break langextract.core.base_model.
- Position
- Below the diagonal: langextract.providers.gemini uses a module listed above it, which is the healthy direction.
23→9 langextract.providers.gemini uses langextract.core.types✕
- Connections
- 1 pair of types, where a type in langextract.providers.gemini uses a type in langextract.core.types.
- The types involved
langextract.providers.gemini.GeminiLanguageModel→langextract.core.types.ScoredOutput
- Direction
- langextract.providers.gemini uses langextract.core.types, so a change to langextract.core.types can break langextract.providers.gemini, while a change to langextract.providers.gemini can't break langextract.core.types.
- Position
- Below the diagonal: langextract.providers.gemini uses a module listed above it, which is the healthy direction.
24→6 langextract.providers.ollama uses langextract.core.base_model✕
- Connections
- 1 pair of types, where a type in langextract.providers.ollama uses a type in langextract.core.base_model.
- The types involved
langextract.providers.ollama.OllamaLanguageModel→langextract.core.base_model.BaseLanguageModel
- Direction
- langextract.providers.ollama uses langextract.core.base_model, so a change to langextract.core.base_model can break langextract.providers.ollama, while a change to langextract.providers.ollama can't break langextract.core.base_model.
- Position
- Below the diagonal: langextract.providers.ollama uses a module listed above it, which is the healthy direction.
24→9 langextract.providers.ollama uses langextract.core.types✕
- Connections
- 1 pair of types, where a type in langextract.providers.ollama uses a type in langextract.core.types.
- The types involved
langextract.providers.ollama.OllamaLanguageModel→langextract.core.types.FormatType
- Direction
- langextract.providers.ollama uses langextract.core.types, so a change to langextract.core.types can break langextract.providers.ollama, while a change to langextract.providers.ollama can't break langextract.core.types.
- Position
- Below the diagonal: langextract.providers.ollama uses a module listed above it, which is the healthy direction.
25→6 langextract.providers.openai uses langextract.core.base_model✕
- Connections
- 1 pair of types, where a type in langextract.providers.openai uses a type in langextract.core.base_model.
- The types involved
langextract.providers.openai.OpenAILanguageModel→langextract.core.base_model.BaseLanguageModel
- Direction
- langextract.providers.openai uses langextract.core.base_model, so a change to langextract.core.base_model can break langextract.providers.openai, while a change to langextract.providers.openai can't break langextract.core.base_model.
- Position
- Below the diagonal: langextract.providers.openai uses a module listed above it, which is the healthy direction.
25→9 langextract.providers.openai uses langextract.core.types✕
- Connections
- 1 pair of types, where a type in langextract.providers.openai uses a type in langextract.core.types.
- The types involved
langextract.providers.openai.OpenAILanguageModel→langextract.core.types.ScoredOutput
- Direction
- langextract.providers.openai uses langextract.core.types, so a change to langextract.core.types can break langextract.providers.openai, while a change to langextract.providers.openai can't break langextract.core.types.
- Position
- Below the diagonal: langextract.providers.openai uses a module listed above it, which is the healthy direction.
25→14 langextract.providers.openai uses langextract.providers.openai_batch✕
- Connections
- 1 pair of types, where a type in langextract.providers.openai uses a type in langextract.providers.openai_batch.
- The types involved
langextract.providers.openai.OpenAILanguageModel→langextract.providers.openai_batch.BatchConfig
- Direction
- langextract.providers.openai uses langextract.providers.openai_batch, so a change to langextract.providers.openai_batch can break langextract.providers.openai, while a change to langextract.providers.openai can't break langextract.providers.openai_batch.
- Position
- Below the diagonal: langextract.providers.openai uses a module listed above it, which is the healthy direction.
26→7 langextract.core uses langextract.core.exceptions✕
- Connections
- 1 pair of types, where a type in langextract.core uses a type in langextract.core.exceptions.
- The types involved
langextract.core.exceptions→langextract.core.exceptions.InferenceConfigError
- Direction
- langextract.core uses langextract.core.exceptions, so a change to langextract.core.exceptions can break langextract.core, while a change to langextract.core can't break langextract.core.exceptions.
- Position
- Below the diagonal: langextract.core uses a module listed above it, which is the healthy direction.
26→19 langextract.core uses langextract.core.schema✕
- Connections
- 1 pair of types, where a type in langextract.core uses a type in langextract.core.schema.
- The types involved
langextract.core.schema→langextract.core.schema.BaseSchema
- Direction
- langextract.core uses langextract.core.schema, so a change to langextract.core.schema can break langextract.core, while a change to langextract.core can't break langextract.core.schema.
- Position
- Below the diagonal: langextract.core uses a module listed above it, which is the healthy direction.
26→20 langextract.core uses langextract.core.tokenizer✕
- Connections
- 4 pairs of types, where a type in langextract.core uses a type in langextract.core.tokenizer.
- The types involved
langextract.core.tokenizer→langextract.core.tokenizer.TokenIntervallangextract.core.tokenizer→langextract.core.tokenizer.TokenTypelangextract.core.tokenizer→langextract.core.tokenizer.TokenizedTextlangextract.core.tokenizer→langextract.core.tokenizer.Tokenizer
- Direction
- langextract.core uses langextract.core.tokenizer, so a change to langextract.core.tokenizer can break langextract.core, while a change to langextract.core can't break langextract.core.tokenizer.
- Position
- Below the diagonal: langextract.core uses a module listed above it, which is the healthy direction.
27→20 langextract.core.data uses langextract.core.tokenizer✕
- Connections
- 2 pairs of types, where a type in langextract.core.data uses a type in langextract.core.tokenizer.
- The types involved
langextract.core.data.AnnotatedDocument→langextract.core.tokenizer.TokenizedTextlangextract.core.data.Document→langextract.core.tokenizer.TokenizedText
- Direction
- langextract.core.data uses langextract.core.tokenizer, so a change to langextract.core.tokenizer can break langextract.core.data, while a change to langextract.core.data can't break langextract.core.tokenizer.
- Position
- Below the diagonal: langextract.core.data uses a module listed above it, which is the healthy direction.
28→8 langextract.providers.schemas.gemini uses langextract.core.format_handler✕
- Connections
- 1 pair of types, where a type in langextract.providers.schemas.gemini uses a type in langextract.core.format_handler.
- The types involved
langextract.providers.schemas.gemini.GeminiSchema→langextract.core.format_handler.FormatHandler
- Direction
- langextract.providers.schemas.gemini uses langextract.core.format_handler, so a change to langextract.core.format_handler can break langextract.providers.schemas.gemini, while a change to langextract.providers.schemas.gemini can't break langextract.core.format_handler.
- Position
- Below the diagonal: langextract.providers.schemas.gemini uses a module listed above it, which is the healthy direction.
28→19 langextract.providers.schemas.gemini uses langextract.core.schema✕
- Connections
- 1 pair of types, where a type in langextract.providers.schemas.gemini uses a type in langextract.core.schema.
- The types involved
langextract.providers.schemas.gemini.GeminiSchema→langextract.core.schema.BaseSchema
- Direction
- langextract.providers.schemas.gemini uses langextract.core.schema, so a change to langextract.core.schema can break langextract.providers.schemas.gemini, while a change to langextract.providers.schemas.gemini can't break langextract.core.schema.
- Position
- Below the diagonal: langextract.providers.schemas.gemini uses a module listed above it, which is the healthy direction.
29→8 langextract.providers.schemas.openai uses langextract.core.format_handler✕
- Connections
- 1 pair of types, where a type in langextract.providers.schemas.openai uses a type in langextract.core.format_handler.
- The types involved
langextract.providers.schemas.openai.OpenAISchema→langextract.core.format_handler.FormatHandler
- Direction
- langextract.providers.schemas.openai uses langextract.core.format_handler, so a change to langextract.core.format_handler can break langextract.providers.schemas.openai, while a change to langextract.providers.schemas.openai can't break langextract.core.format_handler.
- Position
- Below the diagonal: langextract.providers.schemas.openai uses a module listed above it, which is the healthy direction.
29→19 langextract.providers.schemas.openai uses langextract.core.schema✕
- Connections
- 1 pair of types, where a type in langextract.providers.schemas.openai uses a type in langextract.core.schema.
- The types involved
langextract.providers.schemas.openai.OpenAISchema→langextract.core.schema.BaseSchema
- Direction
- langextract.providers.schemas.openai uses langextract.core.schema, so a change to langextract.core.schema can break langextract.providers.schemas.openai, while a change to langextract.providers.schemas.openai can't break langextract.core.schema.
- Position
- Below the diagonal: langextract.providers.schemas.openai uses a module listed above it, which is the healthy direction.
30→7 langextract.chunking uses langextract.core.exceptions✕
- Connections
- 1 pair of types, where a type in langextract.chunking uses a type in langextract.core.exceptions.
- The types involved
langextract.chunking.TokenUtilError→langextract.core.exceptions.LangExtractError
- Direction
- langextract.chunking uses langextract.core.exceptions, so a change to langextract.core.exceptions can break langextract.chunking, while a change to langextract.chunking can't break langextract.core.exceptions.
- Position
- Below the diagonal: langextract.chunking uses a module listed above it, which is the healthy direction.
30→20 langextract.chunking uses langextract.core.tokenizer✕
- Connections
- 5 pairs of types, where a type in langextract.chunking uses a type in langextract.core.tokenizer.
- The types involved
langextract.chunking.ChunkIterator→langextract.core.tokenizer.TokenIntervallangextract.chunking.ChunkIterator→langextract.core.tokenizer.Tokenizerlangextract.chunking.SentenceIterator→langextract.core.tokenizer.TokenIntervallangextract.chunking.SentenceIterator→langextract.core.tokenizer.TokenizedTextlangextract.chunking.TextChunk→langextract.core.tokenizer.TokenInterval
- Direction
- langextract.chunking uses langextract.core.tokenizer, so a change to langextract.core.tokenizer can break langextract.chunking, while a change to langextract.chunking can't break langextract.core.tokenizer.
- Position
- Below the diagonal: langextract.chunking uses a module listed above it, which is the healthy direction.
30→27 langextract.chunking uses langextract.core.data✕
- Connections
- 1 pair of types, where a type in langextract.chunking uses a type in langextract.core.data.
- The types involved
langextract.chunking.TextChunk→langextract.core.data.CharInterval
- Direction
- langextract.chunking uses langextract.core.data, so a change to langextract.core.data can break langextract.chunking, while a change to langextract.chunking can't break langextract.core.data.
- Position
- Below the diagonal: langextract.chunking uses a module listed above it, which is the healthy direction.
31→7 langextract.prompting uses langextract.core.exceptions✕
- Connections
- 1 pair of types, where a type in langextract.prompting uses a type in langextract.core.exceptions.
- The types involved
langextract.prompting.PromptBuilderError→langextract.core.exceptions.LangExtractError
- Direction
- langextract.prompting uses langextract.core.exceptions, so a change to langextract.core.exceptions can break langextract.prompting, while a change to langextract.prompting can't break langextract.core.exceptions.
- Position
- Below the diagonal: langextract.prompting uses a module listed above it, which is the healthy direction.
31→27 langextract.prompting uses langextract.core.data✕
- Connections
- 1 pair of types, where a type in langextract.prompting uses a type in langextract.core.data.
- The types involved
langextract.prompting.QAPromptGenerator→langextract.core.data.ExampleData
- Direction
- langextract.prompting uses langextract.core.data, so a change to langextract.core.data can break langextract.prompting, while a change to langextract.prompting can't break langextract.core.data.
- Position
- Below the diagonal: langextract.prompting uses a module listed above it, which is the healthy direction.
32→7 langextract.resolver uses langextract.core.exceptions✕
- Connections
- 1 pair of types, where a type in langextract.resolver uses a type in langextract.core.exceptions.
- The types involved
langextract.resolver.ResolverParsingError→langextract.core.exceptions.LangExtractError
- Direction
- langextract.resolver uses langextract.core.exceptions, so a change to langextract.core.exceptions can break langextract.resolver, while a change to langextract.resolver can't break langextract.core.exceptions.
- Position
- Below the diagonal: langextract.resolver uses a module listed above it, which is the healthy direction.
32→20 langextract.resolver uses langextract.core.tokenizer✕
- Connections
- 1 pair of types, where a type in langextract.resolver uses a type in langextract.core.tokenizer.
- The types involved
langextract.resolver.WordAligner→langextract.core.tokenizer.TokenizedText
- Direction
- langextract.resolver uses langextract.core.tokenizer, so a change to langextract.core.tokenizer can break langextract.resolver, while a change to langextract.resolver can't break langextract.core.tokenizer.
- Position
- Below the diagonal: langextract.resolver uses a module listed above it, which is the healthy direction.
32→27 langextract.resolver uses langextract.core.data✕
- Connections
- 1 pair of types, where a type in langextract.resolver uses a type in langextract.core.data.
- The types involved
langextract.resolver.WordAligner→langextract.core.data.Extraction
- Direction
- langextract.resolver uses langextract.core.data, so a change to langextract.core.data can break langextract.resolver, while a change to langextract.resolver can't break langextract.core.data.
- Position
- Below the diagonal: langextract.resolver uses a module listed above it, which is the healthy direction.
33→27 langextract.visualization uses langextract.core.data✕
- Connections
- 1 pair of types, where a type in langextract.visualization uses a type in langextract.core.data.
- The types involved
langextract.visualization.SpanPoint→langextract.core.data.Extraction
- Direction
- langextract.visualization uses langextract.core.data, so a change to langextract.core.data can break langextract.visualization, while a change to langextract.visualization can't break langextract.core.data.
- Position
- Below the diagonal: langextract.visualization uses a module listed above it, which is the healthy direction.
34→6 langextract uses langextract.core.base_model✕
- Connections
- 1 pair of types, where a type in langextract uses a type in langextract.core.base_model.
- The types involved
langextract.factory→langextract.core.base_model.BaseLanguageModel
- Direction
- langextract uses langextract.core.base_model, so a change to langextract.core.base_model can break langextract, while a change to langextract can't break langextract.core.base_model.
- Position
- Below the diagonal: langextract uses a module listed above it, which is the healthy direction.
34→7 langextract uses langextract.core.exceptions✕
- Connections
- 1 pair of types, where a type in langextract uses a type in langextract.core.exceptions.
- The types involved
langextract.factory→langextract.core.exceptions.InferenceConfigError
- Direction
- langextract uses langextract.core.exceptions, so a change to langextract.core.exceptions can break langextract, while a change to langextract can't break langextract.core.exceptions.
- Position
- Below the diagonal: langextract uses a module listed above it, which is the healthy direction.
34→10 langextract uses langextract.factory✕
- Connections
- 1 pair of types, where a type in langextract uses a type in langextract.factory.
- The types involved
langextract.factory→langextract.factory.ModelConfig
- Direction
- langextract uses langextract.factory, so a change to langextract.factory can break langextract, while a change to langextract can't break langextract.factory.
- Position
- Below the diagonal: langextract uses a module listed above it, which is the healthy direction.
34→11 langextract uses langextract.prompt_validation✕
- Connections
- 3 pairs of types, where a type in langextract uses a type in langextract.prompt_validation.
- The types involved
langextract.extraction→langextract.prompt_validation.PromptValidationLevellangextract.prompt_validation→langextract.prompt_validation.PromptValidationLevellangextract.prompt_validation→langextract.prompt_validation.ValidationReport
- Direction
- langextract uses langextract.prompt_validation, so a change to langextract.prompt_validation can break langextract, while a change to langextract can't break langextract.prompt_validation.
- Position
- Below the diagonal: langextract uses a module listed above it, which is the healthy direction.
34→20 langextract uses langextract.core.tokenizer✕
- Connections
- 3 pairs of types, where a type in langextract uses a type in langextract.core.tokenizer.
- The types involved
langextract.chunking→langextract.core.tokenizer.TokenIntervallangextract.chunking→langextract.core.tokenizer.TokenizedTextlangextract.resolver→langextract.core.tokenizer.TokenizedText
- Direction
- langextract uses langextract.core.tokenizer, so a change to langextract.core.tokenizer can break langextract, while a change to langextract can't break langextract.core.tokenizer.
- Position
- Below the diagonal: langextract uses a module listed above it, which is the healthy direction.
34→27 langextract uses langextract.core.data✕
- Connections
- 3 pairs of types, where a type in langextract uses a type in langextract.core.data.
- The types involved
langextract.annotation→langextract.core.data.Extractionlangextract.chunking→langextract.core.data.CharIntervallangextract.data_lib→langextract.core.data.AnnotatedDocument
- Direction
- langextract uses langextract.core.data, so a change to langextract.core.data can break langextract, while a change to langextract can't break langextract.core.data.
- Position
- Below the diagonal: langextract uses a module listed above it, which is the healthy direction.
34→31 langextract uses langextract.prompting✕
- Connections
- 1 pair of types, where a type in langextract uses a type in langextract.prompting.
- The types involved
langextract.prompting→langextract.prompting.PromptTemplateStructured
- Direction
- langextract uses langextract.prompting, so a change to langextract.prompting can break langextract, while a change to langextract can't break langextract.prompting.
- Position
- Below the diagonal: langextract uses a module listed above it, which is the healthy direction.
34→32 langextract uses langextract.resolver✕
- Connections
- 1 pair of types, where a type in langextract uses a type in langextract.resolver.
- The types involved
langextract.resolver→langextract.resolver.LcsSpan
- Direction
- langextract uses langextract.resolver, so a change to langextract.resolver can break langextract, while a change to langextract can't break langextract.resolver.
- Position
- Below the diagonal: langextract uses a module listed above it, which is the healthy direction.
35→6 langextract.annotation uses langextract.core.base_model✕
- Connections
- 1 pair of types, where a type in langextract.annotation uses a type in langextract.core.base_model.
- The types involved
langextract.annotation.Annotator→langextract.core.base_model.BaseLanguageModel
- Direction
- langextract.annotation uses langextract.core.base_model, so a change to langextract.core.base_model can break langextract.annotation, while a change to langextract.annotation can't break langextract.core.base_model.
- Position
- Below the diagonal: langextract.annotation uses a module listed above it, which is the healthy direction.
35→27 langextract.annotation uses langextract.core.data✕
- Connections
- 1 pair of types, where a type in langextract.annotation uses a type in langextract.core.data.
- The types involved
langextract.annotation.Annotator→langextract.core.data.AnnotatedDocument
- Direction
- langextract.annotation uses langextract.core.data, so a change to langextract.core.data can break langextract.annotation, while a change to langextract.annotation can't break langextract.core.data.
- Position
- Below the diagonal: langextract.annotation uses a module listed above it, which is the healthy direction.
35→31 langextract.annotation uses langextract.prompting✕
- Connections
- 1 pair of types, where a type in langextract.annotation uses a type in langextract.prompting.
- The types involved
langextract.annotation.Annotator→langextract.prompting.PromptTemplateStructured
- Direction
- langextract.annotation uses langextract.prompting, so a change to langextract.prompting can break langextract.annotation, while a change to langextract.annotation can't break langextract.prompting.
- Position
- Below the diagonal: langextract.annotation uses a module listed above it, which is the healthy direction.
35→32 langextract.annotation uses langextract.resolver✕
- Connections
- 1 pair of types, where a type in langextract.annotation uses a type in langextract.resolver.
- The types involved
langextract.annotation.Annotator→langextract.resolver.AbstractResolver
- Direction
- langextract.annotation uses langextract.resolver, so a change to langextract.resolver can break langextract.annotation, while a change to langextract.annotation can't break langextract.resolver.
- Position
- Below the diagonal: langextract.annotation uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 16 | High / Critical |
| A02:2025 — Security Misconfiguration | 3 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 3 | Medium |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with pyproject.toml.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing. | +7.8 pts | Medium | Security & performance tooling |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with pyproject.toml. | +2.6 pts | Low | ADR Quality |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +5.1 pts | Medium | Release Hygiene |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.6 pts | Medium | Architecture documentation |
| Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (2), REDACTED (2). | +1.2 pts | Medium | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. | +0.5 pts | Low | IaC & Container Security |
| Swallowed exception (caught, then discarded) | +0.7 pts | Medium | Exception handling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| langextract/extraction.py | 6.0 | Mixed | Explicit Debt: TodoComment |
| langextract/resolver.py | 6.0 | Mixed | Explicit Debt: TodoComment |
| langextract/core/tokenizer.py | 6.0 | Mixed | Explicit Debt: TodoComment |
| langextract/providers/gemini.py | 7.0 | Mixed | Cyclomatic Complexity: GeminiLanguageModel.infer (cyclomatic 23) |
| .github/scripts/pr_security_check.py | 7.1 | Mixed | Cyclomatic Complexity: pr_security_check.parse_diff (cyclomatic 19) |
| langextract/providers/gemini_batch.py | 7.2 | Mixed | Cyclomatic Complexity: gemini_batch.infer_batch (cyclomatic 21) |
| langextract/providers/openai.py | 7.2 | Mixed | Cyclomatic Complexity: OpenAILanguageModel.infer (cyclomatic 20) |
| langextract/providers/ollama.py | 7.2 | Mixed | Cognitive Complexity: OllamaLanguageModel.__init__ (cognitive 17) |
| examples/custom_provider_plugin/langextract_provider_example/provider.py | 7.3 | Mixed | Explicit Debt: TodoComment |
| langextract/core/format_handler.py | 7.4 | Mixed | Cyclomatic Complexity: FormatHandler.parse_output (cyclomatic 25) |
| langextract/providers/openai_batch.py | 7.4 | Mixed | Cyclomatic Complexity: openai_batch._infer_batch_one_job (cyclomatic 25) |
| langextract/factory.py | 7.4 | Mixed | Cyclomatic Complexity: factory._create_model_with_schema (cyclomatic 22) |
| langextract/annotation.py | 7.4 | Mixed | Cognitive Complexity: Annotator._annotate_documents_single_pass (cognitive 31) |
| langextract/providers/schemas/gemini.py | 7.4 | Mixed | Cognitive Complexity: GeminiSchema.from_examples (cognitive 30) |
| REDACTED | 7.8 | Mixed | Code Duplication: Duplicated block (15 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 40 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 106 of 113 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.py) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D12 Dependency Hygiene — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's 17 shipped Python distribution(s) across 1 manifest(s) WERE read; what went unanswered is the currency half, because it grades an EXACT pin against the newest release and every declaration here is a floor or a range — which installs the newest release it admits and so cannot be behind one. So pypi.org was never asked. This is a true statement about the repository, and the healthy one, NOT a gap on our side: no reader we could write would find a currency question here.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (33 contributor(s) across 209 commit(s) sampled, automation and bot accounts excluded). One of them holds 82% of the history; the other 32 hold 0.6% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (14884 LoC, 130 module-visible types across 10 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in langextract/providers/router.py, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (examples/ollama/docker-compose.yml). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — langextract Built Container ollama-ollama-1 Error dependency failed to start: container ollama-ollama-1 is unhealthy; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
16 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was extraction.extract at 49.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with extraction.extract (cyclomatic 49). — Refactoring it lifts Cyclomatic Complexity from 6.4 to about 7.4/10.
D2 · Cognitive Complexity
36 method(s) exceeded the cognitive complexity threshold of 15; the worst was extraction.extract at 75.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with extraction.extract (cognitive 75). — Refactoring it lifts Cognitive Complexity from 2.4 to about 3.2/10.
D3 · God Classes
3 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 3 FileTooLong finding(s) in God Classes — start with resolver.py, pr_security_check.py, gemini_batch.py. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
7 duplicated block group(s) detected. 2.5 % of the production lines (386 of 15,187) are in a reported copy. A further 3 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 2 of the 10 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with REDACTED, create_provider_plugin.py. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (40 corresponding lines) finding(s) in Code Duplication — start with ollama.py. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (27 corresponding lines) finding(s) in Code Duplication — start with gemini.py. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 14 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with base_model.py. — One of this dimension's main actionable groups (1 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Python (2 distributions): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 58 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 17 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (41 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 2 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: langextract/extraction.py (3×49=147); langextract/providers/gemini.py (5×23=115); langextract/providers/gemini_batch.py (5×21=105)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with extraction.py, gemini.py, gemini_batch.py. — One of this dimension's main actionable groups (3 warning-level).
D17 · Explicit Debt
6 deducted task-comment markers across 15187 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 6 TodoComment finding(s) in Explicit Debt — start with provider.py (2), REDACTED, extraction.py. — One of this dimension's main actionable groups (6 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with pyproject.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
84 % of calls cross a namespace and 0 % go through an interface, but 52 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
16 finding(s): 0 critical, 13 high, 1 medium, 2 low. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
3 finding(s): 0 critical, 1 high, 2 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 38 of the 53 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 17 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 12 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/check-infrastructure-changes.yml:13
What to do
- Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X12 · Unreachable branch
X23 · Unguarded diagnostic materialisation
- `debug` at line 81 is called with an argument built by `list(discovered.keys())` (line 82), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — langextract/plugins.py:81
- `debug` at line 421 is called with an argument built by `sum(len(group) for group in aligned_yaml_extractions)` (line 423), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — langextract/resolver.py:421
- `debug` at line 65 is called with an argument built by `[p.pattern for p in patterns]` (line 69), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — langextract/providers/router.py:65
- `debug` at line 75 is called with an argument built by `[p.pattern for p in patterns]` (line 78), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — langextract/providers/router.py:75
What to do
- In Python, put the construction behind the logger's own check (`if logger.isEnabledFor(logging.DEBUG):`), or pass the collection itself with a `%s` placeholder (`logger.debug("Items %s", items)`) so the logging module renders it only when the record is emitted. The placeholder alone is not the fix when the argument is still built first: it defers the formatting, not a `json.dumps`, a `join` or a comprehension in the argument, and an f-string defers nothing at all.
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — langextract/visualization.py:59
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — langextract/providers/gemini_batch.py:202, langextract/core/debug_utils.py:184
What to do
- Swallowed exception (caught, then discarded)
X4 · Structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 79% | Adequate — gated by D2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 95% | Exemplary | Strongest area. |
| Maturity | 73% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 60% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 76% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — langextract Built Container ollama-ollama-1 Error dependency failed to start: container ollama-ollama-1 is unhealthy; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~22382 lines of test source are present (.py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D12 Dependency Hygiene — Dependency currency not established — no declaration carries an exact pin to grade
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency does not read html yet; not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Python surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry) — not scanned yet).
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry) — not scanned yet).
- D5 Coupling — Not applicable — this Python build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (30 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's Python source (1 module(s), 46 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 14 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 82 finding(s)
- TodoComment REDACTED:415
- TodoComment langextract/extraction.py:345
- TodoComment langextract/resolver.py:111
- TodoComment langextract/core/tokenizer.py:160
- TodoComment examples/custom_provider_plugin/langextract_provider_example/provider.py:77
- TodoComment examples/custom_provider_plugin/langextract_provider_example/provider.py:174
- Hotspot: langextract/extraction.py langextract/extraction.py:45
- Hotspot: langextract/providers/gemini.py langextract/providers/gemini.py:507
- Hotspot: langextract/providers/gemini_batch.py langextract/providers/gemini_batch.py:867
- FileTooLong: langextract/resolver.py langextract/resolver.py
- FileTooLong: scripts/pr_security_check.py .github/scripts/pr_security_check.py
- FileTooLong: providers/gemini_batch.py langextract/providers/gemini_batch.py
- REDACTED
- REDACTED
- Duplicated block (15 lines × 2) REDACTED:212
- Duplicated block (15 lines × 2) scripts/create_provider_plugin.py:395
- Swallowed exception (empty catch) langextract/providers/gemini_batch.py:202
- Swallowed exception (empty catch) langextract/core/debug_utils.py:184
- extraction.extract (cyclomatic 49) langextract/extraction.py:45
- WordAligner.align_extractions (cyclomatic 30) langextract/resolver.py:828
- FormatHandler.parse_output (cyclomatic 25) langextract/core/format_handler.py:169
- openai_batch._infer_batch_one_job (cyclomatic 25) langextract/providers/openai_batch.py:425
- UnicodeTokenizer.tokenize (cyclomatic 23) langextract/core/tokenizer.py:336
- GeminiLanguageModel.infer (cyclomatic 23) langextract/providers/gemini.py:507
- factory._create_model_with_schema (cyclomatic 22) langextract/factory.py:235
- gemini_batch.infer_batch (cyclomatic 21) langextract/providers/gemini_batch.py:867
- OpenAILanguageModel.infer (cyclomatic 20) langextract/providers/openai.py:354
- pr_security_check.parse_diff (cyclomatic 19) .github/scripts/pr_security_check.py:299
- GeminiLanguageModel.__init__ (cyclomatic 19) langextract/providers/gemini.py:245
- gemini._no_text_diagnostic (cyclomatic 17) langextract/providers/gemini.py:115
- resolver._best_lcs_spans (cyclomatic 17) langextract/resolver.py:1326
- pr_security_check._check_credential_egress (cyclomatic 16) .github/scripts/pr_security_check.py:400
- OpenAILanguageModel._build_chat_completions_params (cyclomatic 16) langextract/providers/openai.py:194
- Resolver.extract_ordered_extractions (cyclomatic 16) langextract/resolver.py:467
- extraction.extract (cognitive 75) langextract/extraction.py:45
- UnicodeTokenizer.tokenize (cognitive 52) langextract/core/tokenizer.py:336
- WordAligner.align_extractions (cognitive 49) langextract/resolver.py:828
- GeminiLanguageModel.infer (cognitive 48) langextract/providers/gemini.py:507
- Resolver.extract_ordered_extractions (cognitive 40) langextract/resolver.py:467
- OpenAILanguageModel.infer (cognitive 39) langextract/providers/openai.py:354
- resolver._best_lcs_spans (cognitive 38) langextract/resolver.py:1326
- FormatHandler.parse_output (cognitive 35) langextract/core/format_handler.py:169
- openai_batch._infer_batch_one_job (cognitive 34) langextract/providers/openai_batch.py:425
- gemini_batch.infer_batch (cognitive 33) langextract/providers/gemini_batch.py:867
- factory._create_model_with_schema (cognitive 32) langextract/factory.py:235
- Annotator._annotate_documents_single_pass (cognitive 31) langextract/annotation.py:285
- GeminiSchema.from_examples (cognitive 30) langextract/providers/schemas/gemini.py:121
- WordAligner._fuzzy_align_extraction (cognitive 29) langextract/resolver.py:630
- factory._kwargs_with_environment_defaults (cognitive 27) langextract/factory.py:58
- annotation._merge_non_overlapping_extractions (cognitive 26) langextract/annotation.py:46
- tokenizer.find_sentence_range (cognitive 22) langextract/core/tokenizer.py:580
- GeminiLanguageModel._process_single_prompt (cognitive 22) langextract/providers/gemini.py:433
- io.download_text_from_url (cognitive 20) langextract/io.py:275
- ChunkIterator.__next__ (cognitive 19) REDACTED:441
- GeminiLanguageModel.__init__ (cognitive 19) langextract/providers/gemini.py:245
- pr_security_check.parse_diff (cognitive 18) .github/scripts/pr_security_check.py:299
- gemini._no_text_diagnostic (cognitive 18) langextract/providers/gemini.py:115
- router.resolve_provider (cognitive 18) langextract/providers/router.py:170
- openai._collect_extraction_categories (cognitive 18) langextract/providers/schemas/openai.py:85
- FormatHandler.from_resolver_params (cognitive 17) langextract/core/format_handler.py:366
- prompt_validation.validate_prompt_alignment (cognitive 17) langextract/prompt_validation.py:130
- gemini_batch._build_request (cognitive 17) langextract/providers/gemini_batch.py:325
- OllamaLanguageModel.__init__ (cognitive 17) langextract/providers/ollama.py:191
- OllamaLanguageModel._build_request_options (cognitive 17) langextract/providers/ollama.py:379
- openai_batch._collect_outputs_from_jsonl (cognitive 17) langextract/providers/openai_batch.py:314
- pr_security_check._check_credential_egress (cognitive 16) .github/scripts/pr_security_check.py:400
- Annotator._annotate_documents_sequential_passes (cognitive 16) langextract/annotation.py:449
- OpenAILanguageModel._build_chat_completions_params (cognitive 16) langextract/providers/openai.py:194
- resolver._select_monotonic_matches (cognitive 16) langextract/resolver.py:1152
- visualization.visualize (cognitive 16) langextract/visualization.py:571
- REDACTED
- REDACTED
- Edited copy of a member (40 corresponding lines) langextract/providers/ollama.py:495
- Edited copy of a member (27 corresponding lines) langextract/providers/schemas/gemini.py:92
- Edited copies of one member (3 members, 18+ corresponding lines) langextract/_compat/inference.py:31
- Duplicated block (32–35 lines × 2) langextract/providers/ollama.py:499
- Duplicated block (21–27 lines × 2) langextract/providers/schemas/gemini.py:126
- Duplicated block (21–22 lines × 2) langextract/providers/gemini.py:591
- Duplicated block (17–18 lines × 2) langextract/providers/gemini.py:613
- Duplicated block (10–11 lines × 2) langextract/resolver.py:734
- Low cohesion: BaseLanguageModel (LCOM4 5) langextract/core/base_model.py:32
- Swallowed exception (caught, then discarded) langextract/visualization.py:59
Minor — 16 finding(s)
- Diagnostic log message is built whether or not it is wanted langextract/plugins.py:81
- Diagnostic log message is built whether or not it is wanted langextract/resolver.py:421
- Diagnostic log message is built whether or not it is wanted langextract/providers/router.py:65
- Diagnostic log message is built whether or not it is wanted langextract/providers/router.py:75
- Duplicated predicate langextract/data_lib.py:51
- Duplicated predicate langextract/providers/gemini.py:595
- Duplicated predicate langextract/providers/schemas/gemini.py:108
- REDACTED
- REDACTED
- No ADRs found pyproject.toml:94
- Scattered collaborators
- REDACTED
- REDACTED
- No ADRs
- No SAST .github/workflows/check-infrastructure-changes.yml:13
- No changelog
Minor — 1 finding(s)
- Dependency hygiene PARTLY measured — Python dependencies read, no exact pin to grade for currency
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-41fb2d0bdd024e078cad66ef6275d4e2/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-41fb2d0bdd024e078cad66ef6275d4e2/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 16 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 3 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry) — not scanned yet). | 0 | — |