Executive summary
xberg-io/tree-sitter-language-pack falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 56.9 out of 100 and is rated Adequate, and all 763 of its critical findings are security problems.
Production Readiness, at 44.9, is the weakest lens and counts most in the score. The best first step is adding type checking, worth about 5.0 points. Adding tests for the code no test reaches would lift Production Readiness itself, worth about 4.2 points. Raising Production Readiness to 70 would lift the score to about 64.1.
731 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen secrets can leak from the build pipeline, and nine pipeline steps install packages that can change without warning. Pinning each tool to an exact version, limiting each secret to its own step and pinning what the pipeline installs would close these risks. Fixing the weaknesses the scanner points to would fix the three security weaknesses in the code, and updating the vulnerable packages would deal with the two packages with a known security hole.
The product code is 26,213 lines, about €32,000 to rebuild.
If Production Readiness rose from 44.9 to 70, the lowest score rated Strong, the score would rise from 56.9 to about 64.1.
Rebuild cost: about €32,000 · Estimate
| Cost to rebuild | €11,000 to €54,000, for 179 to 566 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, 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 | ×0.8 at a score of 57. 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 | Medium: 26,213 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 io.xberg.tslp.android | 2 packages.python.tree_sitter_language_pack.options | 3 packages~swift~RustBridge | 4 scripts.build_grammar_notices | 5 scripts.check_grammar_updates | 6 tree_sitter_language_pack.error | 7 tree_sitter_language_pack.intel.types | 8 tree_sitter_language_pack.pack_config | 9 tree_sitter_language_pack.parsing | 10 tree_sitter_language_pack.process_config | 11 io.xberg.tslp.android.CommentKind | 12 io.xberg.tslp.android.DataNodeKind | 13 io.xberg.tslp.android.DiagnosticSeverity | 14 io.xberg.tslp.android.DocstringFormat | 15 io.xberg.tslp.android.Error | 16 io.xberg.tslp.android.ExportKind | 17 io.xberg.tslp.android.StructureKind | 18 io.xberg.tslp.android.SymbolKind | 19 packages.python.tree_sitter_language_pack | 20 packages~swift~TreeSitterLanguagePack | 21 scripts | 22 tree_sitter_language_pack.intel.c | 23 tree_sitter_language_pack.intel.cedar | 24 tree_sitter_language_pack.intel.chunking | 25 tree_sitter_language_pack.intel.data_extraction | 26 tree_sitter_language_pack.intel.data_extraction.configuration | 27 tree_sitter_language_pack.intel.data_extraction.xml | 28 tree_sitter_language_pack.intel.dockerfile | 29 tree_sitter_language_pack.intel.elixir | 30 tree_sitter_language_pack.intel.intelligence | 31 tree_sitter_language_pack.intel.just | 32 tree_sitter_language_pack.intel.sql | 33 tree_sitter_language_pack.intel.walk | 34 tree_sitter_language_pack.registry | 35 tree_sitter_language_pack_dart.alef_bridge_error | 36 ts_pack_cli | 37 tree_sitter_language_pack | 38 tree_sitter_language_pack.intel | 39 tree_sitter_language_pack.intel.extract | 40 tree_sitter_language_pack_dart |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 io.xberg.tslp.android | ||||||||||||||||||||||||||||||||||||||||
| 2 packages.python.tree_sitter_language_pack.options | ||||||||||||||||||||||||||||||||||||||||
| 3 packages~swift~RustBridge | ||||||||||||||||||||||||||||||||||||||||
| 4 scripts.build_grammar_notices | ||||||||||||||||||||||||||||||||||||||||
| 5 scripts.check_grammar_updates | ||||||||||||||||||||||||||||||||||||||||
| 6 tree_sitter_language_pack.error | ||||||||||||||||||||||||||||||||||||||||
| 7 tree_sitter_language_pack.intel.types | ||||||||||||||||||||||||||||||||||||||||
| 8 tree_sitter_language_pack.pack_config | ||||||||||||||||||||||||||||||||||||||||
| 9 tree_sitter_language_pack.parsing | ||||||||||||||||||||||||||||||||||||||||
| 10 tree_sitter_language_pack.process_config | ||||||||||||||||||||||||||||||||||||||||
| 11 io.xberg.tslp.android.CommentKind | 4 | |||||||||||||||||||||||||||||||||||||||
| 12 io.xberg.tslp.android.DataNodeKind | 4 | |||||||||||||||||||||||||||||||||||||||
| 13 io.xberg.tslp.android.DiagnosticSeverity | 4 | |||||||||||||||||||||||||||||||||||||||
| 14 io.xberg.tslp.android.DocstringFormat | 6 | |||||||||||||||||||||||||||||||||||||||
| 15 io.xberg.tslp.android.Error | 13 | |||||||||||||||||||||||||||||||||||||||
| 16 io.xberg.tslp.android.ExportKind | 4 | |||||||||||||||||||||||||||||||||||||||
| 17 io.xberg.tslp.android.StructureKind | 11 | |||||||||||||||||||||||||||||||||||||||
| 18 io.xberg.tslp.android.SymbolKind | 9 | |||||||||||||||||||||||||||||||||||||||
| 19 packages.python.tree_sitter_language_pack | 19 | |||||||||||||||||||||||||||||||||||||||
| 20 packages~swift~TreeSitterLanguagePack | 45 | |||||||||||||||||||||||||||||||||||||||
| 21 scripts | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 tree_sitter_language_pack.intel.c | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 tree_sitter_language_pack.intel.cedar | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 tree_sitter_language_pack.intel.chunking | 5 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 tree_sitter_language_pack.intel.data_extraction | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 tree_sitter_language_pack.intel.data_extraction.configuration | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 tree_sitter_language_pack.intel.data_extraction.xml | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 tree_sitter_language_pack.intel.dockerfile | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 tree_sitter_language_pack.intel.elixir | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 tree_sitter_language_pack.intel.intelligence | 12 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 tree_sitter_language_pack.intel.just | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 tree_sitter_language_pack.intel.sql | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 tree_sitter_language_pack.intel.walk | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 tree_sitter_language_pack.registry | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 tree_sitter_language_pack_dart.alef_bridge_error | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 ts_pack_cli | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 tree_sitter_language_pack | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 tree_sitter_language_pack.intel | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 tree_sitter_language_pack.intel.extract | 11 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 tree_sitter_language_pack_dart | 1 |
11→1 io.xberg.tslp.android.CommentKind uses io.xberg.tslp.android✕
- Connections
- 4 pairs of types, where a type in io.xberg.tslp.android.CommentKind uses a type in io.xberg.tslp.android.
- The types involved
io.xberg.tslp.android.CommentKind.BLOCK→io.xberg.tslp.android.CommentKindio.xberg.tslp.android.CommentKind.Companion→io.xberg.tslp.android.CommentKindio.xberg.tslp.android.CommentKind.DOC→io.xberg.tslp.android.CommentKindio.xberg.tslp.android.CommentKind.LINE→io.xberg.tslp.android.CommentKind
- Direction
- io.xberg.tslp.android.CommentKind uses io.xberg.tslp.android, so a change to io.xberg.tslp.android can break io.xberg.tslp.android.CommentKind, while a change to io.xberg.tslp.android.CommentKind can't break io.xberg.tslp.android.
- Position
- Below the diagonal: io.xberg.tslp.android.CommentKind uses a module listed above it, which is the healthy direction.
12→1 io.xberg.tslp.android.DataNodeKind uses io.xberg.tslp.android✕
- Connections
- 4 pairs of types, where a type in io.xberg.tslp.android.DataNodeKind uses a type in io.xberg.tslp.android.
- The types involved
io.xberg.tslp.android.DataNodeKind.Companion→io.xberg.tslp.android.DataNodeKindio.xberg.tslp.android.DataNodeKind.ELEMENT→io.xberg.tslp.android.DataNodeKindio.xberg.tslp.android.DataNodeKind.KEY_VALUE→io.xberg.tslp.android.DataNodeKindio.xberg.tslp.android.DataNodeKind.SEQUENCE→io.xberg.tslp.android.DataNodeKind
- Direction
- io.xberg.tslp.android.DataNodeKind uses io.xberg.tslp.android, so a change to io.xberg.tslp.android can break io.xberg.tslp.android.DataNodeKind, while a change to io.xberg.tslp.android.DataNodeKind can't break io.xberg.tslp.android.
- Position
- Below the diagonal: io.xberg.tslp.android.DataNodeKind uses a module listed above it, which is the healthy direction.
13→1 io.xberg.tslp.android.DiagnosticSeverity uses io.xberg.tslp.android✕
- Connections
- 4 pairs of types, where a type in io.xberg.tslp.android.DiagnosticSeverity uses a type in io.xberg.tslp.android.
- The types involved
io.xberg.tslp.android.DiagnosticSeverity.Companion→io.xberg.tslp.android.DiagnosticSeverityio.xberg.tslp.android.DiagnosticSeverity.ERROR→io.xberg.tslp.android.DiagnosticSeverityio.xberg.tslp.android.DiagnosticSeverity.INFO→io.xberg.tslp.android.DiagnosticSeverityio.xberg.tslp.android.DiagnosticSeverity.WARNING→io.xberg.tslp.android.DiagnosticSeverity
- Direction
- io.xberg.tslp.android.DiagnosticSeverity uses io.xberg.tslp.android, so a change to io.xberg.tslp.android can break io.xberg.tslp.android.DiagnosticSeverity, while a change to io.xberg.tslp.android.DiagnosticSeverity can't break io.xberg.tslp.android.
- Position
- Below the diagonal: io.xberg.tslp.android.DiagnosticSeverity uses a module listed above it, which is the healthy direction.
14→1 io.xberg.tslp.android.DocstringFormat uses io.xberg.tslp.android✕
- Connections
- 6 pairs of types, where a type in io.xberg.tslp.android.DocstringFormat uses a type in io.xberg.tslp.android.
- The types involved
io.xberg.tslp.android.DocstringFormat.GoDoc→io.xberg.tslp.android.DocstringFormatio.xberg.tslp.android.DocstringFormat.JSDoc→io.xberg.tslp.android.DocstringFormatio.xberg.tslp.android.DocstringFormat.JavaDoc→io.xberg.tslp.android.DocstringFormatio.xberg.tslp.android.DocstringFormat.Other→io.xberg.tslp.android.DocstringFormatio.xberg.tslp.android.DocstringFormat.PythonTripleQuote→io.xberg.tslp.android.DocstringFormatio.xberg.tslp.android.DocstringFormat.Rustdoc→io.xberg.tslp.android.DocstringFormat
- Direction
- io.xberg.tslp.android.DocstringFormat uses io.xberg.tslp.android, so a change to io.xberg.tslp.android can break io.xberg.tslp.android.DocstringFormat, while a change to io.xberg.tslp.android.DocstringFormat can't break io.xberg.tslp.android.
- Position
- Below the diagonal: io.xberg.tslp.android.DocstringFormat uses a module listed above it, which is the healthy direction.
15→1 io.xberg.tslp.android.Error uses io.xberg.tslp.android✕
- Connections
- 13 pairs of types, where a type in io.xberg.tslp.android.Error uses a type in io.xberg.tslp.android.
- The types involved
io.xberg.tslp.android.Error.CacheLock→io.xberg.tslp.android.Errorio.xberg.tslp.android.Error.ChecksumMismatch→io.xberg.tslp.android.Errorio.xberg.tslp.android.Error.Config→io.xberg.tslp.android.Errorio.xberg.tslp.android.Error.Download→io.xberg.tslp.android.Errorio.xberg.tslp.android.Error.DynamicLoad→io.xberg.tslp.android.Errorio.xberg.tslp.android.Error.InvalidRange→io.xberg.tslp.android.Errorio.xberg.tslp.android.Error.LanguageNotFound→io.xberg.tslp.android.Errorio.xberg.tslp.android.Error.LockPoisoned→io.xberg.tslp.android.Errorio.xberg.tslp.android.Error.NullLanguagePointer→io.xberg.tslp.android.Errorio.xberg.tslp.android.Error.ParseFailed→io.xberg.tslp.android.Errorio.xberg.tslp.android.Error.ParseTimeout→io.xberg.tslp.android.Errorio.xberg.tslp.android.Error.ParserSetup→io.xberg.tslp.android.Errorio.xberg.tslp.android.Error.QueryError→io.xberg.tslp.android.Error
- Direction
- io.xberg.tslp.android.Error uses io.xberg.tslp.android, so a change to io.xberg.tslp.android can break io.xberg.tslp.android.Error, while a change to io.xberg.tslp.android.Error can't break io.xberg.tslp.android.
- Position
- Below the diagonal: io.xberg.tslp.android.Error uses a module listed above it, which is the healthy direction.
16→1 io.xberg.tslp.android.ExportKind uses io.xberg.tslp.android✕
- Connections
- 4 pairs of types, where a type in io.xberg.tslp.android.ExportKind uses a type in io.xberg.tslp.android.
- The types involved
io.xberg.tslp.android.ExportKind.Companion→io.xberg.tslp.android.ExportKindio.xberg.tslp.android.ExportKind.DEFAULT→io.xberg.tslp.android.ExportKindio.xberg.tslp.android.ExportKind.NAMED→io.xberg.tslp.android.ExportKindio.xberg.tslp.android.ExportKind.RE_EXPORT→io.xberg.tslp.android.ExportKind
- Direction
- io.xberg.tslp.android.ExportKind uses io.xberg.tslp.android, so a change to io.xberg.tslp.android can break io.xberg.tslp.android.ExportKind, while a change to io.xberg.tslp.android.ExportKind can't break io.xberg.tslp.android.
- Position
- Below the diagonal: io.xberg.tslp.android.ExportKind uses a module listed above it, which is the healthy direction.
17→1 io.xberg.tslp.android.StructureKind uses io.xberg.tslp.android✕
- Connections
- 11 pairs of types, where a type in io.xberg.tslp.android.StructureKind uses a type in io.xberg.tslp.android.
- The types involved
io.xberg.tslp.android.StructureKind.Class→io.xberg.tslp.android.StructureKindio.xberg.tslp.android.StructureKind.Enum→io.xberg.tslp.android.StructureKindio.xberg.tslp.android.StructureKind.Function→io.xberg.tslp.android.StructureKindio.xberg.tslp.android.StructureKind.Impl→io.xberg.tslp.android.StructureKindio.xberg.tslp.android.StructureKind.Interface→io.xberg.tslp.android.StructureKindio.xberg.tslp.android.StructureKind.Method→io.xberg.tslp.android.StructureKindio.xberg.tslp.android.StructureKind.Module→io.xberg.tslp.android.StructureKindio.xberg.tslp.android.StructureKind.Namespace→io.xberg.tslp.android.StructureKindio.xberg.tslp.android.StructureKind.Other→io.xberg.tslp.android.StructureKindio.xberg.tslp.android.StructureKind.Struct→io.xberg.tslp.android.StructureKindio.xberg.tslp.android.StructureKind.Trait→io.xberg.tslp.android.StructureKind
- Direction
- io.xberg.tslp.android.StructureKind uses io.xberg.tslp.android, so a change to io.xberg.tslp.android can break io.xberg.tslp.android.StructureKind, while a change to io.xberg.tslp.android.StructureKind can't break io.xberg.tslp.android.
- Position
- Below the diagonal: io.xberg.tslp.android.StructureKind uses a module listed above it, which is the healthy direction.
18→1 io.xberg.tslp.android.SymbolKind uses io.xberg.tslp.android✕
- Connections
- 9 pairs of types, where a type in io.xberg.tslp.android.SymbolKind uses a type in io.xberg.tslp.android.
- The types involved
io.xberg.tslp.android.SymbolKind.Class→io.xberg.tslp.android.SymbolKindio.xberg.tslp.android.SymbolKind.Constant→io.xberg.tslp.android.SymbolKindio.xberg.tslp.android.SymbolKind.Enum→io.xberg.tslp.android.SymbolKindio.xberg.tslp.android.SymbolKind.Function→io.xberg.tslp.android.SymbolKindio.xberg.tslp.android.SymbolKind.Interface→io.xberg.tslp.android.SymbolKindio.xberg.tslp.android.SymbolKind.Module→io.xberg.tslp.android.SymbolKindio.xberg.tslp.android.SymbolKind.Other→io.xberg.tslp.android.SymbolKindio.xberg.tslp.android.SymbolKind.Type→io.xberg.tslp.android.SymbolKindio.xberg.tslp.android.SymbolKind.Variable→io.xberg.tslp.android.SymbolKind
- Direction
- io.xberg.tslp.android.SymbolKind uses io.xberg.tslp.android, so a change to io.xberg.tslp.android can break io.xberg.tslp.android.SymbolKind, while a change to io.xberg.tslp.android.SymbolKind can't break io.xberg.tslp.android.
- Position
- Below the diagonal: io.xberg.tslp.android.SymbolKind uses a module listed above it, which is the healthy direction.
19→2 packages.python.tree_sitter_language_pack uses packages.python.tree_sitter_language_pack.options✕
- Connections
- 19 pairs of types, where a type in packages.python.tree_sitter_language_pack uses a type in packages.python.tree_sitter_language_pack.options.
- The types involved
packages.python.tree_sitter_language_pack.api→packages.python.tree_sitter_language_pack.options.ProcessResultpackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.ChunkContextpackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.CodeChunkpackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.CommentInfopackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.DataAttributepackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.DataNodepackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.Diagnosticpackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.DocSectionpackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.DocstringInfopackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.ExportInfopackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.FileMetricspackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.ImportInfopackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.LanguageRegistrypackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.PackConfigpackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.ProcessConfigpackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.ProcessResultpackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.Spanpackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.StructureItempackages.python.tree_sitter_language_pack.options→packages.python.tree_sitter_language_pack.options.SymbolInfo
- Direction
- packages.python.tree_sitter_language_pack uses packages.python.tree_sitter_language_pack.options, so a change to packages.python.tree_sitter_language_pack.options can break packages.python.tree_sitter_language_pack, while a change to packages.python.tree_sitter_language_pack can't break packages.python.tree_sitter_language_pack.options.
- Position
- Below the diagonal: packages.python.tree_sitter_language_pack uses a module listed above it, which is the healthy direction.
20→3 packages~swift~TreeSitterLanguagePack uses packages~swift~RustBridge✕
- Connections
- 45 pairs of types, where a type in packages~swift~TreeSitterLanguagePack uses a type in packages~swift~RustBridge. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
packages~swift~TreeSitterLanguagePack.AlefErrorPayloadKey→packages~swift~RustBridge.Intpackages~swift~TreeSitterLanguagePack.AlefErrorPayloadKey→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.ByteRange→packages~swift~RustBridge.UIntpackages~swift~TreeSitterLanguagePack.ChunkContext→packages~swift~RustBridge.Boolpackages~swift~TreeSitterLanguagePack.ChunkContext→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.ChunkContext→packages~swift~RustBridge.UIntpackages~swift~TreeSitterLanguagePack.CodeChunk→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.CodeChunk→packages~swift~RustBridge.UIntpackages~swift~TreeSitterLanguagePack.CodingKeys→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.CommentInfo→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.CommentKind→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.DataAttribute→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.DataNode→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.DataNodeKind→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.Diagnostic→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.DiagnosticSeverity→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.DocSection→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.DocstringInfo→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.ExportInfo→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.ExportKind→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.FileMetrics→packages~swift~RustBridge.UIntpackages~swift~TreeSitterLanguagePack.ImportInfo→packages~swift~RustBridge.Boolpackages~swift~TreeSitterLanguagePack.ImportInfo→packages~swift~RustBridge.Stringpackages~swift~TreeSitterLanguagePack.InputEdit→packages~swift~RustBridge.UIntpackages~swift~TreeSitterLanguagePack.Point→packages~swift~RustBridge.UInt
- Direction
- packages~swift~TreeSitterLanguagePack uses packages~swift~RustBridge, so a change to packages~swift~RustBridge can break packages~swift~TreeSitterLanguagePack, while a change to packages~swift~TreeSitterLanguagePack can't break packages~swift~RustBridge.
- Position
- Below the diagonal: packages~swift~TreeSitterLanguagePack uses a module listed above it, which is the healthy direction.
21→4 scripts uses scripts.build_grammar_notices✕
- Connections
- 1 pair of types, where a type in scripts uses a type in scripts.build_grammar_notices.
- The types involved
scripts.build_grammar_notices→scripts.build_grammar_notices.LanguageResult
- Direction
- scripts uses scripts.build_grammar_notices, so a change to scripts.build_grammar_notices can break scripts, while a change to scripts can't break scripts.build_grammar_notices.
- Position
- Below the diagonal: scripts uses a module listed above it, which is the healthy direction.
21→5 scripts uses scripts.check_grammar_updates✕
- Connections
- 1 pair of types, where a type in scripts uses a type in scripts.check_grammar_updates.
- The types involved
scripts.check_grammar_updates→scripts.check_grammar_updates.CheckReport
- Direction
- scripts uses scripts.check_grammar_updates, so a change to scripts.check_grammar_updates can break scripts, while a change to scripts can't break scripts.check_grammar_updates.
- Position
- Below the diagonal: scripts uses a module listed above it, which is the healthy direction.
22→7 tree_sitter_language_pack.intel.c uses tree_sitter_language_pack.intel.types✕
- Connections
- 2 pairs of types, where a type in tree_sitter_language_pack.intel.c uses a type in tree_sitter_language_pack.intel.types.
- The types involved
tree_sitter_language_pack.intel.c.c$module→tree_sitter_language_pack.intel.types.StructureItemtree_sitter_language_pack.intel.c.c$module→tree_sitter_language_pack.intel.types.StructureKind
- Direction
- tree_sitter_language_pack.intel.c uses tree_sitter_language_pack.intel.types, so a change to tree_sitter_language_pack.intel.types can break tree_sitter_language_pack.intel.c, while a change to tree_sitter_language_pack.intel.c can't break tree_sitter_language_pack.intel.types.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.c uses a module listed above it, which is the healthy direction.
22→9 tree_sitter_language_pack.intel.c uses tree_sitter_language_pack.parsing✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel.c uses a type in tree_sitter_language_pack.parsing.
- The types involved
tree_sitter_language_pack.intel.c.c$module→tree_sitter_language_pack.parsing.Node
- Direction
- tree_sitter_language_pack.intel.c uses tree_sitter_language_pack.parsing, so a change to tree_sitter_language_pack.parsing can break tree_sitter_language_pack.intel.c, while a change to tree_sitter_language_pack.intel.c can't break tree_sitter_language_pack.parsing.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.c uses a module listed above it, which is the healthy direction.
23→7 tree_sitter_language_pack.intel.cedar uses tree_sitter_language_pack.intel.types✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel.cedar uses a type in tree_sitter_language_pack.intel.types.
- The types involved
tree_sitter_language_pack.intel.cedar.cedar$module→tree_sitter_language_pack.intel.types.StructureItem
- Direction
- tree_sitter_language_pack.intel.cedar uses tree_sitter_language_pack.intel.types, so a change to tree_sitter_language_pack.intel.types can break tree_sitter_language_pack.intel.cedar, while a change to tree_sitter_language_pack.intel.cedar can't break tree_sitter_language_pack.intel.types.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.cedar uses a module listed above it, which is the healthy direction.
23→9 tree_sitter_language_pack.intel.cedar uses tree_sitter_language_pack.parsing✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel.cedar uses a type in tree_sitter_language_pack.parsing.
- The types involved
tree_sitter_language_pack.intel.cedar.cedar$module→tree_sitter_language_pack.parsing.Node
- Direction
- tree_sitter_language_pack.intel.cedar uses tree_sitter_language_pack.parsing, so a change to tree_sitter_language_pack.parsing can break tree_sitter_language_pack.intel.cedar, while a change to tree_sitter_language_pack.intel.cedar can't break tree_sitter_language_pack.parsing.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.cedar uses a module listed above it, which is the healthy direction.
24→7 tree_sitter_language_pack.intel.chunking uses tree_sitter_language_pack.intel.types✕
- Connections
- 5 pairs of types, where a type in tree_sitter_language_pack.intel.chunking uses a type in tree_sitter_language_pack.intel.types.
- The types involved
tree_sitter_language_pack.intel.chunking.ChunkMetadata→tree_sitter_language_pack.intel.types.CommentInfotree_sitter_language_pack.intel.chunking.ChunkMetadata→tree_sitter_language_pack.intel.types.DocstringInfotree_sitter_language_pack.intel.chunking.MetadataCollector→tree_sitter_language_pack.intel.types.CommentInfotree_sitter_language_pack.intel.chunking.MetadataCollector→tree_sitter_language_pack.intel.types.DocstringInfotree_sitter_language_pack.intel.chunking.chunking$module→tree_sitter_language_pack.intel.types.CodeChunk
- Direction
- tree_sitter_language_pack.intel.chunking uses tree_sitter_language_pack.intel.types, so a change to tree_sitter_language_pack.intel.types can break tree_sitter_language_pack.intel.chunking, while a change to tree_sitter_language_pack.intel.chunking can't break tree_sitter_language_pack.intel.types.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.chunking uses a module listed above it, which is the healthy direction.
24→9 tree_sitter_language_pack.intel.chunking uses tree_sitter_language_pack.parsing✕
- Connections
- 2 pairs of types, where a type in tree_sitter_language_pack.intel.chunking uses a type in tree_sitter_language_pack.parsing.
- The types involved
tree_sitter_language_pack.intel.chunking.chunking$module→tree_sitter_language_pack.parsing.Nodetree_sitter_language_pack.intel.chunking.chunking$module→tree_sitter_language_pack.parsing.Tree
- Direction
- tree_sitter_language_pack.intel.chunking uses tree_sitter_language_pack.parsing, so a change to tree_sitter_language_pack.parsing can break tree_sitter_language_pack.intel.chunking, while a change to tree_sitter_language_pack.intel.chunking can't break tree_sitter_language_pack.parsing.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.chunking uses a module listed above it, which is the healthy direction.
25→7 tree_sitter_language_pack.intel.data_extraction uses tree_sitter_language_pack.intel.types✕
- Connections
- 2 pairs of types, where a type in tree_sitter_language_pack.intel.data_extraction uses a type in tree_sitter_language_pack.intel.types.
- The types involved
tree_sitter_language_pack.intel.data_extraction.data_extraction$module→tree_sitter_language_pack.intel.types.DataNodetree_sitter_language_pack.intel.data_extraction.data_extraction$module→tree_sitter_language_pack.intel.types.Span
- Direction
- tree_sitter_language_pack.intel.data_extraction uses tree_sitter_language_pack.intel.types, so a change to tree_sitter_language_pack.intel.types can break tree_sitter_language_pack.intel.data_extraction, while a change to tree_sitter_language_pack.intel.data_extraction can't break tree_sitter_language_pack.intel.types.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.data_extraction uses a module listed above it, which is the healthy direction.
25→9 tree_sitter_language_pack.intel.data_extraction uses tree_sitter_language_pack.parsing✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel.data_extraction uses a type in tree_sitter_language_pack.parsing.
- The types involved
tree_sitter_language_pack.intel.data_extraction.data_extraction$module→tree_sitter_language_pack.parsing.Node
- Direction
- tree_sitter_language_pack.intel.data_extraction uses tree_sitter_language_pack.parsing, so a change to tree_sitter_language_pack.parsing can break tree_sitter_language_pack.intel.data_extraction, while a change to tree_sitter_language_pack.intel.data_extraction can't break tree_sitter_language_pack.parsing.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.data_extraction uses a module listed above it, which is the healthy direction.
26→7 tree_sitter_language_pack.intel.data_extraction.configuration uses tree_sitter_language_pack.intel.types✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel.data_extraction.configuration uses a type in tree_sitter_language_pack.intel.types.
- The types involved
tree_sitter_language_pack.intel.data_extraction.configuration.configuration$module→tree_sitter_language_pack.intel.types.DataNode
- Direction
- tree_sitter_language_pack.intel.data_extraction.configuration uses tree_sitter_language_pack.intel.types, so a change to tree_sitter_language_pack.intel.types can break tree_sitter_language_pack.intel.data_extraction.configuration, while a change to tree_sitter_language_pack.intel.data_extraction.configuration can't break tree_sitter_language_pack.intel.types.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.data_extraction.configuration uses a module listed above it, which is the healthy direction.
26→9 tree_sitter_language_pack.intel.data_extraction.configuration uses tree_sitter_language_pack.parsing✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel.data_extraction.configuration uses a type in tree_sitter_language_pack.parsing.
- The types involved
tree_sitter_language_pack.intel.data_extraction.configuration.configuration$module→tree_sitter_language_pack.parsing.Node
- Direction
- tree_sitter_language_pack.intel.data_extraction.configuration uses tree_sitter_language_pack.parsing, so a change to tree_sitter_language_pack.parsing can break tree_sitter_language_pack.intel.data_extraction.configuration, while a change to tree_sitter_language_pack.intel.data_extraction.configuration can't break tree_sitter_language_pack.parsing.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.data_extraction.configuration uses a module listed above it, which is the healthy direction.
27→7 tree_sitter_language_pack.intel.data_extraction.xml uses tree_sitter_language_pack.intel.types✕
- Connections
- 3 pairs of types, where a type in tree_sitter_language_pack.intel.data_extraction.xml uses a type in tree_sitter_language_pack.intel.types.
- The types involved
tree_sitter_language_pack.intel.data_extraction.xml.xml$module→tree_sitter_language_pack.intel.types.DataAttributetree_sitter_language_pack.intel.data_extraction.xml.xml$module→tree_sitter_language_pack.intel.types.DataNodetree_sitter_language_pack.intel.data_extraction.xml.xml$module→tree_sitter_language_pack.intel.types.DataNodeKind
- Direction
- tree_sitter_language_pack.intel.data_extraction.xml uses tree_sitter_language_pack.intel.types, so a change to tree_sitter_language_pack.intel.types can break tree_sitter_language_pack.intel.data_extraction.xml, while a change to tree_sitter_language_pack.intel.data_extraction.xml can't break tree_sitter_language_pack.intel.types.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.data_extraction.xml uses a module listed above it, which is the healthy direction.
27→9 tree_sitter_language_pack.intel.data_extraction.xml uses tree_sitter_language_pack.parsing✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel.data_extraction.xml uses a type in tree_sitter_language_pack.parsing.
- The types involved
tree_sitter_language_pack.intel.data_extraction.xml.xml$module→tree_sitter_language_pack.parsing.Node
- Direction
- tree_sitter_language_pack.intel.data_extraction.xml uses tree_sitter_language_pack.parsing, so a change to tree_sitter_language_pack.parsing can break tree_sitter_language_pack.intel.data_extraction.xml, while a change to tree_sitter_language_pack.intel.data_extraction.xml can't break tree_sitter_language_pack.parsing.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.data_extraction.xml uses a module listed above it, which is the healthy direction.
28→7 tree_sitter_language_pack.intel.dockerfile uses tree_sitter_language_pack.intel.types✕
- Connections
- 2 pairs of types, where a type in tree_sitter_language_pack.intel.dockerfile uses a type in tree_sitter_language_pack.intel.types.
- The types involved
tree_sitter_language_pack.intel.dockerfile.Stage→tree_sitter_language_pack.intel.types.StructureItemtree_sitter_language_pack.intel.dockerfile.dockerfile$module→tree_sitter_language_pack.intel.types.StructureItem
- Direction
- tree_sitter_language_pack.intel.dockerfile uses tree_sitter_language_pack.intel.types, so a change to tree_sitter_language_pack.intel.types can break tree_sitter_language_pack.intel.dockerfile, while a change to tree_sitter_language_pack.intel.dockerfile can't break tree_sitter_language_pack.intel.types.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.dockerfile uses a module listed above it, which is the healthy direction.
28→9 tree_sitter_language_pack.intel.dockerfile uses tree_sitter_language_pack.parsing✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel.dockerfile uses a type in tree_sitter_language_pack.parsing.
- The types involved
tree_sitter_language_pack.intel.dockerfile.dockerfile$module→tree_sitter_language_pack.parsing.Node
- Direction
- tree_sitter_language_pack.intel.dockerfile uses tree_sitter_language_pack.parsing, so a change to tree_sitter_language_pack.parsing can break tree_sitter_language_pack.intel.dockerfile, while a change to tree_sitter_language_pack.intel.dockerfile can't break tree_sitter_language_pack.parsing.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.dockerfile uses a module listed above it, which is the healthy direction.
29→7 tree_sitter_language_pack.intel.elixir uses tree_sitter_language_pack.intel.types✕
- Connections
- 2 pairs of types, where a type in tree_sitter_language_pack.intel.elixir uses a type in tree_sitter_language_pack.intel.types.
- The types involved
tree_sitter_language_pack.intel.elixir.ElixirDefinition→tree_sitter_language_pack.intel.types.StructureKindtree_sitter_language_pack.intel.elixir.elixir$module→tree_sitter_language_pack.intel.types.ImportInfo
- Direction
- tree_sitter_language_pack.intel.elixir uses tree_sitter_language_pack.intel.types, so a change to tree_sitter_language_pack.intel.types can break tree_sitter_language_pack.intel.elixir, while a change to tree_sitter_language_pack.intel.elixir can't break tree_sitter_language_pack.intel.types.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.elixir uses a module listed above it, which is the healthy direction.
29→9 tree_sitter_language_pack.intel.elixir uses tree_sitter_language_pack.parsing✕
- Connections
- 2 pairs of types, where a type in tree_sitter_language_pack.intel.elixir uses a type in tree_sitter_language_pack.parsing.
- The types involved
tree_sitter_language_pack.intel.elixir.ElixirDefinition→tree_sitter_language_pack.parsing.Nodetree_sitter_language_pack.intel.elixir.elixir$module→tree_sitter_language_pack.parsing.Node
- Direction
- tree_sitter_language_pack.intel.elixir uses tree_sitter_language_pack.parsing, so a change to tree_sitter_language_pack.parsing can break tree_sitter_language_pack.intel.elixir, while a change to tree_sitter_language_pack.intel.elixir can't break tree_sitter_language_pack.parsing.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.elixir uses a module listed above it, which is the healthy direction.
30→7 tree_sitter_language_pack.intel.intelligence uses tree_sitter_language_pack.intel.types✕
- Connections
- 12 pairs of types, where a type in tree_sitter_language_pack.intel.intelligence uses a type in tree_sitter_language_pack.intel.types.
- The types involved
tree_sitter_language_pack.intel.intelligence.intelligence$module→tree_sitter_language_pack.intel.types.CommentInfotree_sitter_language_pack.intel.intelligence.intelligence$module→tree_sitter_language_pack.intel.types.Diagnostictree_sitter_language_pack.intel.intelligence.intelligence$module→tree_sitter_language_pack.intel.types.DocstringFormattree_sitter_language_pack.intel.intelligence.intelligence$module→tree_sitter_language_pack.intel.types.DocstringInfotree_sitter_language_pack.intel.intelligence.intelligence$module→tree_sitter_language_pack.intel.types.ExportInfotree_sitter_language_pack.intel.intelligence.intelligence$module→tree_sitter_language_pack.intel.types.FileMetricstree_sitter_language_pack.intel.intelligence.intelligence$module→tree_sitter_language_pack.intel.types.ImportInfotree_sitter_language_pack.intel.intelligence.intelligence$module→tree_sitter_language_pack.intel.types.ProcessResulttree_sitter_language_pack.intel.intelligence.intelligence$module→tree_sitter_language_pack.intel.types.Spantree_sitter_language_pack.intel.intelligence.intelligence$module→tree_sitter_language_pack.intel.types.StructureKindtree_sitter_language_pack.intel.intelligence.intelligence$module→tree_sitter_language_pack.intel.types.SymbolInfotree_sitter_language_pack.intel.intelligence.intelligence$module→tree_sitter_language_pack.intel.types.SymbolKind
- Direction
- tree_sitter_language_pack.intel.intelligence uses tree_sitter_language_pack.intel.types, so a change to tree_sitter_language_pack.intel.types can break tree_sitter_language_pack.intel.intelligence, while a change to tree_sitter_language_pack.intel.intelligence can't break tree_sitter_language_pack.intel.types.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.intelligence uses a module listed above it, which is the healthy direction.
30→9 tree_sitter_language_pack.intel.intelligence uses tree_sitter_language_pack.parsing✕
- Connections
- 2 pairs of types, where a type in tree_sitter_language_pack.intel.intelligence uses a type in tree_sitter_language_pack.parsing.
- The types involved
tree_sitter_language_pack.intel.intelligence.intelligence$module→tree_sitter_language_pack.parsing.Nodetree_sitter_language_pack.intel.intelligence.intelligence$module→tree_sitter_language_pack.parsing.Tree
- Direction
- tree_sitter_language_pack.intel.intelligence uses tree_sitter_language_pack.parsing, so a change to tree_sitter_language_pack.parsing can break tree_sitter_language_pack.intel.intelligence, while a change to tree_sitter_language_pack.intel.intelligence can't break tree_sitter_language_pack.parsing.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.intelligence uses a module listed above it, which is the healthy direction.
31→7 tree_sitter_language_pack.intel.just uses tree_sitter_language_pack.intel.types✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel.just uses a type in tree_sitter_language_pack.intel.types.
- The types involved
tree_sitter_language_pack.intel.just.just$module→tree_sitter_language_pack.intel.types.StructureItem
- Direction
- tree_sitter_language_pack.intel.just uses tree_sitter_language_pack.intel.types, so a change to tree_sitter_language_pack.intel.types can break tree_sitter_language_pack.intel.just, while a change to tree_sitter_language_pack.intel.just can't break tree_sitter_language_pack.intel.types.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.just uses a module listed above it, which is the healthy direction.
31→9 tree_sitter_language_pack.intel.just uses tree_sitter_language_pack.parsing✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel.just uses a type in tree_sitter_language_pack.parsing.
- The types involved
tree_sitter_language_pack.intel.just.just$module→tree_sitter_language_pack.parsing.Node
- Direction
- tree_sitter_language_pack.intel.just uses tree_sitter_language_pack.parsing, so a change to tree_sitter_language_pack.parsing can break tree_sitter_language_pack.intel.just, while a change to tree_sitter_language_pack.intel.just can't break tree_sitter_language_pack.parsing.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.just uses a module listed above it, which is the healthy direction.
32→7 tree_sitter_language_pack.intel.sql uses tree_sitter_language_pack.intel.types✕
- Connections
- 2 pairs of types, where a type in tree_sitter_language_pack.intel.sql uses a type in tree_sitter_language_pack.intel.types.
- The types involved
tree_sitter_language_pack.intel.sql.Head→tree_sitter_language_pack.intel.types.StructureKindtree_sitter_language_pack.intel.sql.sql$module→tree_sitter_language_pack.intel.types.StructureItem
- Direction
- tree_sitter_language_pack.intel.sql uses tree_sitter_language_pack.intel.types, so a change to tree_sitter_language_pack.intel.types can break tree_sitter_language_pack.intel.sql, while a change to tree_sitter_language_pack.intel.sql can't break tree_sitter_language_pack.intel.types.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.sql uses a module listed above it, which is the healthy direction.
32→9 tree_sitter_language_pack.intel.sql uses tree_sitter_language_pack.parsing✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel.sql uses a type in tree_sitter_language_pack.parsing.
- The types involved
tree_sitter_language_pack.intel.sql.sql$module→tree_sitter_language_pack.parsing.Node
- Direction
- tree_sitter_language_pack.intel.sql uses tree_sitter_language_pack.parsing, so a change to tree_sitter_language_pack.parsing can break tree_sitter_language_pack.intel.sql, while a change to tree_sitter_language_pack.intel.sql can't break tree_sitter_language_pack.parsing.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.sql uses a module listed above it, which is the healthy direction.
33→9 tree_sitter_language_pack.intel.walk uses tree_sitter_language_pack.parsing✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel.walk uses a type in tree_sitter_language_pack.parsing.
- The types involved
tree_sitter_language_pack.intel.walk.walk$module→tree_sitter_language_pack.parsing.Node
- Direction
- tree_sitter_language_pack.intel.walk uses tree_sitter_language_pack.parsing, so a change to tree_sitter_language_pack.parsing can break tree_sitter_language_pack.intel.walk, while a change to tree_sitter_language_pack.intel.walk can't break tree_sitter_language_pack.parsing.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.walk uses a module listed above it, which is the healthy direction.
34→10 tree_sitter_language_pack.registry uses tree_sitter_language_pack.process_config✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.registry uses a type in tree_sitter_language_pack.process_config.
- The types involved
tree_sitter_language_pack.registry.LanguageRegistry→tree_sitter_language_pack.process_config.ProcessConfig
- Direction
- tree_sitter_language_pack.registry uses tree_sitter_language_pack.process_config, so a change to tree_sitter_language_pack.process_config can break tree_sitter_language_pack.registry, while a change to tree_sitter_language_pack.registry can't break tree_sitter_language_pack.process_config.
- Position
- Below the diagonal: tree_sitter_language_pack.registry uses a module listed above it, which is the healthy direction.
35→40 tree_sitter_language_pack_dart.alef_bridge_error uses tree_sitter_language_pack_dart part of a loop✕
- Connections
- 2 pairs of types, where a type in tree_sitter_language_pack_dart.alef_bridge_error uses a type in tree_sitter_language_pack_dart.
- The types involved
tree_sitter_language_pack_dart.alef_bridge_error.AlefBridgeError→tree_sitter_language_pack_dart.AlefBridgeErrorWiretree_sitter_language_pack_dart.alef_bridge_error.AlefBridgeError→tree_sitter_language_pack_dart.Error
- Direction
- tree_sitter_language_pack_dart.alef_bridge_error uses tree_sitter_language_pack_dart, so a change to tree_sitter_language_pack_dart can break tree_sitter_language_pack_dart.alef_bridge_error, while a change to tree_sitter_language_pack_dart.alef_bridge_error can't break tree_sitter_language_pack_dart.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→8 ts_pack_cli uses tree_sitter_language_pack.pack_config✕
- Connections
- 1 pair of types, where a type in ts_pack_cli uses a type in tree_sitter_language_pack.pack_config.
- The types involved
ts_pack_cli.ts_pack_cli$module→tree_sitter_language_pack.pack_config.PackConfig
- Direction
- ts_pack_cli uses tree_sitter_language_pack.pack_config, so a change to tree_sitter_language_pack.pack_config can break ts_pack_cli, while a change to ts_pack_cli can't break tree_sitter_language_pack.pack_config.
- Position
- Below the diagonal: ts_pack_cli uses a module listed above it, which is the healthy direction.
36→10 ts_pack_cli uses tree_sitter_language_pack.process_config✕
- Connections
- 1 pair of types, where a type in ts_pack_cli uses a type in tree_sitter_language_pack.process_config.
- The types involved
ts_pack_cli.ProcessFlags→tree_sitter_language_pack.process_config.ProcessConfig
- Direction
- ts_pack_cli uses tree_sitter_language_pack.process_config, so a change to tree_sitter_language_pack.process_config can break ts_pack_cli, while a change to ts_pack_cli can't break tree_sitter_language_pack.process_config.
- Position
- Below the diagonal: ts_pack_cli uses a module listed above it, which is the healthy direction.
37→8 tree_sitter_language_pack uses tree_sitter_language_pack.pack_config✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack uses a type in tree_sitter_language_pack.pack_config.
- The types involved
tree_sitter_language_pack.tree_sitter_language_pack$module→tree_sitter_language_pack.pack_config.PackConfig
- Direction
- tree_sitter_language_pack uses tree_sitter_language_pack.pack_config, so a change to tree_sitter_language_pack.pack_config can break tree_sitter_language_pack, while a change to tree_sitter_language_pack can't break tree_sitter_language_pack.pack_config.
- Position
- Below the diagonal: tree_sitter_language_pack uses a module listed above it, which is the healthy direction.
37→10 tree_sitter_language_pack uses tree_sitter_language_pack.process_config✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack uses a type in tree_sitter_language_pack.process_config.
- The types involved
tree_sitter_language_pack.tree_sitter_language_pack$module→tree_sitter_language_pack.process_config.ProcessConfig
- Direction
- tree_sitter_language_pack uses tree_sitter_language_pack.process_config, so a change to tree_sitter_language_pack.process_config can break tree_sitter_language_pack, while a change to tree_sitter_language_pack can't break tree_sitter_language_pack.process_config.
- Position
- Below the diagonal: tree_sitter_language_pack uses a module listed above it, which is the healthy direction.
37→34 tree_sitter_language_pack uses tree_sitter_language_pack.registry✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack uses a type in tree_sitter_language_pack.registry.
- The types involved
tree_sitter_language_pack.tree_sitter_language_pack$module→tree_sitter_language_pack.registry.LanguageRegistry
- Direction
- tree_sitter_language_pack uses tree_sitter_language_pack.registry, so a change to tree_sitter_language_pack.registry can break tree_sitter_language_pack, while a change to tree_sitter_language_pack can't break tree_sitter_language_pack.registry.
- Position
- Below the diagonal: tree_sitter_language_pack uses a module listed above it, which is the healthy direction.
38→10 tree_sitter_language_pack.intel uses tree_sitter_language_pack.process_config✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel uses a type in tree_sitter_language_pack.process_config.
- The types involved
tree_sitter_language_pack.intel.intel$module→tree_sitter_language_pack.process_config.ProcessConfig
- Direction
- tree_sitter_language_pack.intel uses tree_sitter_language_pack.process_config, so a change to tree_sitter_language_pack.process_config can break tree_sitter_language_pack.intel, while a change to tree_sitter_language_pack.intel can't break tree_sitter_language_pack.process_config.
- Position
- Below the diagonal: tree_sitter_language_pack.intel uses a module listed above it, which is the healthy direction.
38→34 tree_sitter_language_pack.intel uses tree_sitter_language_pack.registry✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel uses a type in tree_sitter_language_pack.registry.
- The types involved
tree_sitter_language_pack.intel.intel$module→tree_sitter_language_pack.registry.LanguageRegistry
- Direction
- tree_sitter_language_pack.intel uses tree_sitter_language_pack.registry, so a change to tree_sitter_language_pack.registry can break tree_sitter_language_pack.intel, while a change to tree_sitter_language_pack.intel can't break tree_sitter_language_pack.registry.
- Position
- Below the diagonal: tree_sitter_language_pack.intel uses a module listed above it, which is the healthy direction.
39→7 tree_sitter_language_pack.intel.extract uses tree_sitter_language_pack.intel.types✕
- Connections
- 11 pairs of types, where a type in tree_sitter_language_pack.intel.extract uses a type in tree_sitter_language_pack.intel.types.
- The types involved
tree_sitter_language_pack.intel.extract.Collector→tree_sitter_language_pack.intel.types.CommentInfotree_sitter_language_pack.intel.extract.Collector→tree_sitter_language_pack.intel.types.Diagnostictree_sitter_language_pack.intel.extract.Collector→tree_sitter_language_pack.intel.types.DocstringInfotree_sitter_language_pack.intel.extract.Collector→tree_sitter_language_pack.intel.types.ExportInfotree_sitter_language_pack.intel.extract.Collector→tree_sitter_language_pack.intel.types.ProcessResulttree_sitter_language_pack.intel.extract.Collector→tree_sitter_language_pack.intel.types.SymbolInfotree_sitter_language_pack.intel.extract.ImportScope→tree_sitter_language_pack.intel.types.ImportInfotree_sitter_language_pack.intel.extract.OpenItem→tree_sitter_language_pack.intel.types.StructureItemtree_sitter_language_pack.intel.extract.Opening→tree_sitter_language_pack.intel.types.StructureKindtree_sitter_language_pack.intel.extract.StructureScope→tree_sitter_language_pack.intel.types.StructureItemtree_sitter_language_pack.intel.extract.extract$module→tree_sitter_language_pack.intel.types.ProcessResult
- Direction
- tree_sitter_language_pack.intel.extract uses tree_sitter_language_pack.intel.types, so a change to tree_sitter_language_pack.intel.types can break tree_sitter_language_pack.intel.extract, while a change to tree_sitter_language_pack.intel.extract can't break tree_sitter_language_pack.intel.types.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.extract uses a module listed above it, which is the healthy direction.
39→9 tree_sitter_language_pack.intel.extract uses tree_sitter_language_pack.parsing✕
- Connections
- 5 pairs of types, where a type in tree_sitter_language_pack.intel.extract uses a type in tree_sitter_language_pack.parsing.
- The types involved
tree_sitter_language_pack.intel.extract.Collector→tree_sitter_language_pack.parsing.Nodetree_sitter_language_pack.intel.extract.ImportScope→tree_sitter_language_pack.parsing.Nodetree_sitter_language_pack.intel.extract.Opening→tree_sitter_language_pack.parsing.Nodetree_sitter_language_pack.intel.extract.StructureScope→tree_sitter_language_pack.parsing.Nodetree_sitter_language_pack.intel.extract.extract$module→tree_sitter_language_pack.parsing.Node
- Direction
- tree_sitter_language_pack.intel.extract uses tree_sitter_language_pack.parsing, so a change to tree_sitter_language_pack.parsing can break tree_sitter_language_pack.intel.extract, while a change to tree_sitter_language_pack.intel.extract can't break tree_sitter_language_pack.parsing.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.extract uses a module listed above it, which is the healthy direction.
39→33 tree_sitter_language_pack.intel.extract uses tree_sitter_language_pack.intel.walk✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack.intel.extract uses a type in tree_sitter_language_pack.intel.walk.
- The types involved
tree_sitter_language_pack.intel.extract.Collector→tree_sitter_language_pack.intel.walk.Descend
- Direction
- tree_sitter_language_pack.intel.extract uses tree_sitter_language_pack.intel.walk, so a change to tree_sitter_language_pack.intel.walk can break tree_sitter_language_pack.intel.extract, while a change to tree_sitter_language_pack.intel.extract can't break tree_sitter_language_pack.intel.walk.
- Position
- Below the diagonal: tree_sitter_language_pack.intel.extract uses a module listed above it, which is the healthy direction.
40→35 tree_sitter_language_pack_dart uses tree_sitter_language_pack_dart.alef_bridge_error✕
- Connections
- 1 pair of types, where a type in tree_sitter_language_pack_dart uses a type in tree_sitter_language_pack_dart.alef_bridge_error.
- The types involved
tree_sitter_language_pack_dart.tree_sitter_language_pack_dart$module→tree_sitter_language_pack_dart.alef_bridge_error.AlefBridgeError
- Direction
- tree_sitter_language_pack_dart uses tree_sitter_language_pack_dart.alef_bridge_error, so a change to tree_sitter_language_pack_dart.alef_bridge_error can break tree_sitter_language_pack_dart, while a change to tree_sitter_language_pack_dart can't break tree_sitter_language_pack_dart.alef_bridge_error.
- Position
- Below the diagonal: tree_sitter_language_pack_dart 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
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 779 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | Medium |
Roadmap
Top priorities: Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package; Add tests that import the unreached modules (directly or through their public entry).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +5.0 pts | Medium | Type Safety |
| Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package. | +4.5 pts | Medium | Large Files |
| Add tests that import the unreached modules (directly or through their public entry). | +4.2 pts | Medium | Test Coverage |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +2.7 pts | Medium | Dependency Hygiene |
| Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate. | +2.2 pts | Medium | Security & performance tooling |
| Resolve the 1 Floating branch dependency finding(s) in Dependency Hygiene. | +0.6 pts | Low | Dependency Hygiene |
| Resolve the 1 No Package.resolved committed (test_apps/swift_e2e/Package.swift) finding(s) in Dependency Hygiene. | +0.6 pts | Low | Dependency Hygiene |
| Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with tree_sitter_language_pack::intel::intelligence::symbol_at (cyclomatic 24), Collector::visit (cyclomatic 16). | +0.4 pts | Medium | Cyclomatic Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
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 53 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 — 53 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, 929 of 939 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: the .NET half measured 4.1%; the JavaScript/TypeScript half could not be measured — the dependency install for crates/ts-pack-core-wasm/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D10 Test 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. The 1,050 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 92 test source file(s) (.py, .rs, .ts, .mjs) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — 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. Test reliability NOT MEASURED: this repository's test suite spans .NET and JavaScript/TypeScript, and the JavaScript/TypeScript half could not be re-run — unit: measured (0 flaky); e2e: measured (0 flaky); JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in crates/ts-pack-core-wasm/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in e2e/node/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in e2e/wasm/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in test_apps/node/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in test_apps/wasm/): not included — the dependency install for crates/ts-pack-core-wasm/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. No partial figure is published as if it were the whole: reliability is excluded from the score rather than counted as a near-zero.
- D11 Test Reliability — 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. Test reliability for the vitest suite in crates/ts-pack-core-wasm/ was NOT MEASURED: the dependency install for crates/ts-pack-core-wasm/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — 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. Test reliability for the vitest suite in e2e/node/ was NOT MEASURED: the dependency install for e2e/node/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — 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. Test reliability for the vitest suite in e2e/wasm/ was NOT MEASURED: the dependency install for e2e/wasm/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "e2e/wasm/REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — 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. Test reliability for the vitest suite in test_apps/node/ was NOT MEASURED: the dependency install for test_apps/node/ could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-12.18.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack…), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — 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. Test reliability for the vitest suite in test_apps/wasm/ was NOT MEASURED: the dependency install for test_apps/wasm/ could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-12.18.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack…), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D14 License Compliance — 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. This repository declares a Cargo manifest, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Cargo dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — 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. This repository declares a Python REDACTED/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — 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. This repository declares a Swift Package.swift/Package.resolved, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its SwiftPM dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — 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. This repository declares composer.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Composer dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — 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. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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 (50 contributor(s) across 2252 commit(s) sampled, automation and bot accounts excluded). One of them holds 92% of the history; the other 49 hold 0.2% 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.
- D17 Explicit Debt — 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. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .rs (17,564 lines, 66% of production source), .py (5,907 lines, 22% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- 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.
- 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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.
- 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — 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. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): 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.
- D23 Boundary Type-Coupling — 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. Large codebase (26,213 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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 — 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D28 Secrets (history) — 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. The newest 1000 of 2418 commits were scanned for secrets, back to commit 2632ffd16d40; older commits were not. `gitleaks` TIMED OUT after 62.4s against a 62.4s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. The working tree WAS scanned in full, and every row of the scanned ranges is reported. Nothing about the unscanned commits is asserted by the absence of a result; the budget is ours to raise.
- D32 Data Compliance (PII/GDPR) — 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. `crates/ts-pack-core-php/stubs/tree_sitter_language_pack_extension.php` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- X12 Unreachable branch — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X3 Exception handling — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- 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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- 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.
- D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was tree_sitter_language_pack::intel::intelligence::symbol_at at 24. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being tree_sitter_language_pack::intel::data_extraction::extract_data at 16 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/ts-pack-core/src/intel/data_extraction.rs (tree_sitter_language_pack::intel::data_extraction::extract_data at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with tree_sitter_language_pack::intel::intelligence::symbol_at (cyclomatic 24), Collector::visit (cyclomatic 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
7 method(s) exceeded the cognitive complexity threshold of 15; the worst was tree_sitter_language_pack::build_support::patches::parse_unified_diff at 24.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cognitive Complexity — start with tree_sitter_language_pack::build_support::patches::parse_unified_diff (cognitive 24), downloader._safe_extract (cognitive 22), tree_sitter_language_pack::intel::c::structure (cognitive 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cognitive Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
6 god class(es) detected.
What to do
- Resolve the 3 FileTooLong finding(s) in God Classes — start with mcp.rs, grammar.js, intelligence.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with download.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyFunctions finding(s) in God Classes — start with data_extraction.rs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
19 duplicated block group(s) detected. 3.7 % of the production lines (964 of 26,213) are in a reported copy. A further 16 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 7 of the 35 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 3 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with configuration.rs (2), large.py. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with download.rs, cache.rs, large.py. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (17 corresponding lines) finding(s) in Code Duplication — start with configuration.rs, data_extraction.rs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
18 production modules (Maven+Cargo+npm+Python+SwiftPM+Composer), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 4 of the 18 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 26 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with mcp.rs. — One of this dimension's main actionable groups (1 warning-level).
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1050 tests. Measured on the C# suite only — at least 92 test source file(s) (.py, .rs, .ts, .mjs) went unread, so its test quality is unmeasured and is not in these counts.
D12 · Dependency Hygiene
1 outdated direct SwiftPM dependencies, 2 pinning defect(s). 2 of 4 direct dependencies had their releases listed (0 naming no readable repository, 2 pinned to a branch or a revision rather than a version). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.
What to do
- Resolve the 1 No Package.resolved committed (test_apps/swift_e2e/Package.swift) finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Floating branch dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 0 packages use a banned license. The depth of this set was not established for this repository: the graded packages are what this pass resolved, and no lockfile was read, so it is not certified to be the full transitive closure. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Cargo manifest, a Python REDACTED/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, composer.json and package.json, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: crates/ts-pack-core/src/intel/intelligence.rs (6×24=144) Repeated repair below the complexity floor: scripts/clone_vendors.py (10 of 14 changes were fixes); scripts/check_test_app_pins.py (5 of 9 changes were fixes); crates/ts-pack-core/src/intel/data_extraction.rs (4 of 7 changes were fixes)
What to do
- Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with clone_vendors.py, check_test_app_pins.py, data_extraction.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with intelligence.rs. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
0 deducted debt markers + 0 dead symbols across 6829 LoC in the .NET projects (0.0/KLoC) → score 10.0. Measured on the .NET source only: .rs, .py (88% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 27 document(s) read across 12 unit(s).
D20 · ADR Quality
2 of 9 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D22 · Internal API Consistency
0 API inconsistencies among 4 exposed members measured against a convention their peers follow.
D26 · Project Cohesion
0 of 5 projects flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the current working tree and the part of the history named below, and found no secrets. History coverage: The newest 1000 of 2418 commits were scanned for secrets, back to commit 2632ffd16d40; older commits were not. `gitleaks` TIMED OUT after 62.4s against a 62.4s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows.
D29 · Static Analysis (SAST)
783 finding(s): 0 critical, 761 high, 0 medium, 22 low. 731 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 9 file(s) — `crates/ts-pack-core-php/stubs/tree_sitter_language_pack_extension.php` (line 74, line 76, line 91, …), `crates/ts-pack-core/src/download/cache.rs` (line 65), `crates/ts-pack-core/third_party/utf8proc/utf8proc.c`, `crates/ts-pack-core/third_party/utf8proc/utf8proc.h`, `fixtures/bench/python/large.py` (line 145, lines 151–154, lines 156–159, …), … (+4 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 10 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 14 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (11), REDACTED (3). — One of this dimension's main actionable groups (14 issue-level).
- Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED, REDACTED. — One of this dimension's main actionable groups (9 issue-level).
- No action in Static Analysis (SAST) — all 725 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (725 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
6 finding(s): 0 critical, 2 high, 3 medium, 1 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 0 high, 4 medium, 0 low.
What to do
- Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 71 of the 82 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
2/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).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 34 platform declaration(s) and 81 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
AX5 · Architecture & structure
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- `TreeSitterLanguagePack.ByteArrayJsonConverter` (packages/csharp/TreeSitterLanguagePack/ByteArrayJsonConverter.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `TreeSitterLanguagePack.E2eTests`, `TreeSitterLanguagePack.SmokeTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — packages/csharp/TreeSitterLanguagePack/ByteArrayJsonConverter.cs:24
- `TreeSitterLanguagePack.DocstringFormatJsonConverter` (packages/csharp/TreeSitterLanguagePack/DocstringFormat.cs:74) is public, and the library's own code uses it, but no other project in this repository uses it (read: `TreeSitterLanguagePack.E2eTests`, `TreeSitterLanguagePack.SmokeTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — packages/csharp/TreeSitterLanguagePack/DocstringFormat.cs:74
- `TreeSitterLanguagePack.StructureKindJsonConverter` (packages/csharp/TreeSitterLanguagePack/StructureKind.cs:101) is public, and the library's own code uses it, but no other project in this repository uses it (read: `TreeSitterLanguagePack.E2eTests`, `TreeSitterLanguagePack.SmokeTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — packages/csharp/TreeSitterLanguagePack/StructureKind.cs:101
- `TreeSitterLanguagePack.SymbolKindJsonConverter` (packages/csharp/TreeSitterLanguagePack/SymbolKind.cs:87) is public, and the library's own code uses it, but no other project in this repository uses it (read: `TreeSitterLanguagePack.E2eTests`, `TreeSitterLanguagePack.SmokeTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — packages/csharp/TreeSitterLanguagePack/SymbolKind.cs:87
What to do
- Make `TreeSitterLanguagePack.ByteArrayJsonConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `TreeSitterLanguagePack.DocstringFormatJsonConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `TreeSitterLanguagePack.StructureKindJsonConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `TreeSitterLanguagePack.SymbolKindJsonConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
P3 · Security & performance tooling
- `REDACTED` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
- `e2e/csharp/TreeSitterLanguagePack.E2eTests.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — e2e/csharp/TreeSitterLanguagePack.E2eTests.csproj:23
What to do
- Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
- 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
PF3 · Async & latency hygiene
R1 · Type Safety
- 0 typed · 14 plain JS — the untyped files are cli-proxy/npm/install.js, cli-proxy/npm/test.mjs, grammars/abnf/grammar.js, grammars/graphql/grammar.js, grammars/plantuml/grammar.js, grammars/plantuml/grammer/baseuml.js (+8 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- 5 duplicated blocks under grammars/ have copies in at least two of the sibling directories abnf, graphql, promela, reason, wolfram, xquery (+1 more sibling(s) not listed) — 1 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — grammars/wolfram/grammar.js:585
- cli-proxy/npm/install.js:219 · cli-proxy/npm/install.js:254 — the two spans are one implementation copied and then locally edited — 158 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — cli-proxy/npm/install.js:219
- grammars/reason/grammar.js:241 · grammars/reason/grammar.js:386 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — grammars/reason/grammar.js:241
- grammars/wolfram/grammar.js:5 · grammars/wolfram/grammar.js:26 — all 2 copies are in the same file, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — grammars/wolfram/grammar.js:5
- grammars/xquery/grammar.js:376 · grammars/xquery/grammar.js:387 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Check what actually differs between the copies before collapsing them: every one of them is an argument to a `grammar(…)` call, so where these calls are a MATRIX of cases — one per input, differing precisely in the case each one pins — the repetition is the enumeration and extracting the shared part would delete cases rather than de-duplicate anything. — grammars/xquery/grammar.js:376
- grammars/graphql/grammar.js:38 · grammars/graphql/grammar.js:52 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — grammars/graphql/grammar.js:38
- grammars/graphql/grammar.js:55 · grammars/graphql/grammar.js:62 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Check what actually differs between the copies before collapsing them: every one of them is an argument to a `grammar(…)` call, so where these calls are a MATRIX of cases — one per input, differing precisely in the case each one pins — the repetition is the enumeration and extracting the shared part would delete cases rather than de-duplicate anything. — grammars/graphql/grammar.js:55
- grammars/xquery/grammar.js:558 · grammars/xquery/grammar.js:676 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Check what actually differs between the copies before collapsing them: every one of them is an argument to a `grammar(…)` call, so where these calls are a MATRIX of cases — one per input, differing precisely in the case each one pins — the repetition is the enumeration and extracting the shared part would delete cases rather than de-duplicate anything. — grammars/xquery/grammar.js:558
- grammars/graphql/grammar.js:74 · grammars/reason/grammar.js:227 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — grammars/graphql/grammar.js:74
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
- grammars/wolfram/grammar.js has 882 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — grammars/wolfram/grammar.js:1
- grammars/xquery/grammar.js has 832 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — grammars/xquery/grammar.js:1
- grammars/reason/grammar.js has 712 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — grammars/reason/grammar.js:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×12) — grammars/wolfram/grammar.js:1, grammars/reason/grammar.js:1, grammars/xquery/grammar.js:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- The package in `grammars/plantuml` declares the lint script `lint` (`prettier --check grammar.js`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `grammars/plantuml` (or the workspace's task runner). — grammars/plantuml/package.json:7
- The package in `grammars/wolfram` declares the lint script `lint` (`eslint "**/*.{js,cjs,mjs,ts,tsx,json}"`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `grammars/wolfram` (or the workspace's task runner). — grammars/wolfram/package.json:11
R7 · Dead Code
- 4 file(s) (~808 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
- 2 file(s) (~167 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — docs-site
- 1 file(s) (~123 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — grammars/abnf
- 1 file(s) (~237 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — grammars/graphql
- 1 file(s) (~250 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — grammars/promela
- 1 file(s) (~919 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — grammars/reason
- 1 file(s) (~989 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — grammars/wolfram
- 1 file(s) (~835 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — grammars/xquery
- 1 file(s) (~81 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — grammars/yul
- 9 file(s) (~3838 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — test_apps/node
- 9 file(s) (~2140 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — test_apps/wasm
- This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×2) — grammars/wolfram/grammar.js:64, grammars/wolfram/grammar.js:69
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×13) — package.json:10, package.json:12, package.json:13, …
- Declared in docs-site/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — docs-site/package.json:17
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X5 · Nullable reference types
- ~1.0 `!` suppressions per 1k syntax nodes — 24 suppression(s) across the 22978 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 48.3 | Weak — gated by R1, R3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96.7 | Exemplary | Solid. |
| Maturity | 95.7 | Exemplary | Solid. |
| Readiness | 44.9 | Weak — gated by R4, R8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 72.1 | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 12 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 20 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 — 73 check(s) not relevant to this codebase
- AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — AX6 reached only 36% of this repository's production lines — rust (17,564 lines), c (320 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — #1 [internal] load build definition from dockerfile.json #1 transferring dockerfile: 509B done #1 DONE 0.0s dockerfile.json:1 -------------------- 1 | >>> { 2 | "id": "smoke_dockerfile", 3 | "description": "Smoke test: load dockerfile and parse a simple snippet", -------------------- ERROR: failed to solve: dockerfile parse error on line 1: unknown instruction: {; likely cause (the repository): the REDACTED does not parse: docker reports an instruction or option it does not know; runtime evidence skipped The cause is in the repository, not in our sandbox: the REDACTED does not parse: docker reports an instruction or option it does not know. Nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, 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 the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D11 Test Reliability — Test reliability not measured — polyglot suite, one half not re-run
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution, but this repository's production source is mostly .c, .go, .php, .py, .rb, .rs, .swift, .ts, .tsx — the .NET project files present are an immaterial minority — so the dimension does not apply.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .go, .php, .py, .rb, .rs, .swift source were not judged.
- D25 ADR Conformance — None of 8 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 161 value object(s)
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- 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
- IC1 Incompleteness & stubs — reported, not scored — this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- 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 by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
- 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- 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
- X12 Unreachable branch — X12 reached only 0% of this repository's production lines — rust (17,564 lines), python (5,907 lines), javascript (1,338 lines), php (1,213 lines), typescript (714 lines), go (640 lines), c (320 lines), swift (88 lines), ruby (87 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X16 reached only 0% of this repository's production lines — rust (17,564 lines), python (5,907 lines), javascript (1,338 lines), php (1,213 lines), typescript (714 lines), go (640 lines), c (320 lines), swift (88 lines), ruby (87 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X18 reached only 0% of this repository's production lines — rust (17,564 lines), python (5,907 lines), javascript (1,338 lines), php (1,213 lines), typescript (714 lines), go (640 lines), c (320 lines), swift (88 lines), ruby (87 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 async method does work a token could cancel
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — 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
- X27 Collection changed while being enumerated — X27 reached only 0% of this repository's production lines — rust (17,564 lines), python (5,907 lines), javascript (1,338 lines), php (1,213 lines), typescript (714 lines), go (640 lines), c (320 lines), swift (88 lines), ruby (87 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X28 Index access outside its own emptiness guard — 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — X3 reached only 0% of this repository's production lines — rust (17,564 lines), python (5,907 lines), javascript (1,338 lines), php (1,213 lines), typescript (714 lines), go (640 lines), c (320 lines), swift (88 lines), ruby (87 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 763 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 121 finding(s)
- No test reaches this file grammars/wolfram/grammar.js:1
- No test reaches this file grammars/reason/grammar.js:1
- No test reaches this file grammars/xquery/grammar.js:1
- No test reaches this file grammars/promela/grammar.js:1
- No test reaches this file grammars/graphql/grammar.js:1
- No test reaches this file grammars/abnf/grammar.js:1
- No test reaches this file grammars/yul/grammar.js:1
- No test reaches this file cli-proxy/npm/bin/ts-pack.js:1
- No test reaches this file grammars/plantuml/grammar.js:1
- No test reaches this file grammars/plantuml/grammer/baseuml.js:1
- No test reaches this file grammars/plantuml/grammer/jsonuml.js:1
- No test reaches this file grammars/plantuml/grammer/yamluml.js:1
- JavaScript dependencies are not locked crates/ts-pack-core-wasm/package.json:60
- JavaScript dependencies are not locked grammars/abnf/package.json:20
- JavaScript dependencies are not locked grammars/graphql/package.json:12
- JavaScript dependencies are not locked grammars/plantuml/package.json:16
- JavaScript dependencies are not locked grammars/promela/package.json:8
- JavaScript dependencies are not locked grammars/reason/package.json:10
- JavaScript dependencies are not locked grammars/wolfram/package.json:18
- JavaScript dependencies are not locked grammars/xquery/package.json:32
- JavaScript dependencies are not locked grammars/yul/package.json:9
- JavaScript dependencies are not locked plugin/package.json:7
- tree_sitter_language_pack::build_support::patches::parse_unified_diff (cognitive 24) crates/ts-pack-core/build_support/patches.rs:206
- tree_sitter_language_pack::intel::c::structure (cognitive 19) crates/ts-pack-core/src/intel/c.rs:40
- tree_sitter_language_pack::intel::elixir::elixir_callable_name (cognitive 19) crates/ts-pack-core/src/intel/elixir.rs:144
- tree_sitter_language_pack::intel::intelligence::resolve_structure_name (cognitive 19) crates/ts-pack-core/src/intel/intelligence.rs:862
- tree_sitter_language_pack::intel::intelligence::js_import_items_and_alias (cognitive 17) crates/ts-pack-core/src/intel/intelligence.rs:451
- tree_sitter_language_pack::intel::intelligence::symbol_at (cognitive 16) crates/ts-pack-core/src/intel/intelligence.rs:717
- Repeated repair: scripts/clone_vendors.py scripts/clone_vendors.py:396
- Repeated repair: scripts/check_test_app_pins.py scripts/check_test_app_pins.py:224
- Repeated repair: crates/ts-pack-core/src/intel/data_extraction.rs crates/ts-pack-core/src/intel/data_extraction.rs:254
- Repeated repair: crates/ts-pack-core/build_support/wasm.rs crates/ts-pack-core/build_support/wasm.rs:7
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: commands/mcp.rs crates/ts-pack-cli/src/commands/mcp.rs
- FileTooLong: wolfram/grammar.js grammars/wolfram/grammar.js
- FileTooLong: intel/intelligence.rs crates/ts-pack-core/src/intel/intelligence.rs
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (15 lines × 2) crates/ts-pack-core/src/intel/data_extraction/configuration.rs:124
- Duplicated block (15 lines × 2) crates/ts-pack-core/src/intel/data_extraction/configuration.rs:277
- Duplicated block (15 lines × 2) fixtures/bench/python/large.py:313
- Duplicated block (13 lines × 2) crates/ts-pack-core/src/download.rs:666
- Duplicated block (13 lines × 2) crates/ts-pack-core/src/download/cache.rs:318
- Duplicated block (13 lines × 2) fixtures/bench/python/large.py:499
- Duplicated block (7 lines × 2 locations) grammars/graphql/grammar.js:38
- Duplicated block (7 lines × 2 locations) grammars/graphql/grammar.js:55
- Duplicated block (7 lines × 2 locations) grammars/xquery/grammar.js:558
- Edited copy of a member (17 corresponding lines) crates/ts-pack-core/src/intel/data_extraction/configuration.rs:275
- Edited copy of a member (17 corresponding lines) crates/ts-pack-core/src/intel/data_extraction.rs:467
- Duplicated block (10 lines × 2) crates/ts-pack-core/src/intel/data_extraction.rs:474
- Duplicated block (10 lines × 2) crates/ts-pack-core/build_support/dynamic.rs:149
- This package's lint script runs in no CI job grammars/plantuml/package.json:7
- This package's lint script runs in no CI job grammars/wolfram/package.json:11
- NuGet dependencies are not locked e2e/csharp/TreeSitterLanguagePack.E2eTests.csproj:23
- NuGet dependencies are not locked test_apps/csharp/TreeSitterLanguagePack.E2eTests.csproj:23
- tree_sitter_language_pack::intel::intelligence::symbol_at (cyclomatic 24) crates/ts-pack-core/src/intel/intelligence.rs:717
- Collector::visit (cyclomatic 16) crates/ts-pack-core/src/intel/extract.rs:157
- No Package.resolved committed (test_apps/swift_e2e/Package.swift)
- Floating branch dependency: tree-sitter-language-pack
- Hotspot: crates/ts-pack-core/src/intel/intelligence.rs crates/ts-pack-core/src/intel/intelligence.rs:717
- downloader._safe_extract (cognitive 22) cli-proxy/pypi/ts_pack_cli/downloader.py:183
- TooManyMethods: DownloadManager crates/ts-pack-core/src/download.rs:126
- TooManyFunctions: tree_sitter_language_pack::intel::data_extraction crates/ts-pack-core/src/intel/data_extraction.rs:40
- ClassTooLong: DownloadManager crates/ts-pack-core/src/download.rs:126
- REDACTED
- Members sharing a duplicated core (6 members, 50+ identical tokens) crates/ts-pack-core/src/intel/data_extraction.rs:420
- Edited copy of a member (22 corresponding lines) crates/ts-pack-core/src/download/cache.rs:309
- Edited copy of a member (29 corresponding lines) crates/ts-pack-core/src/intel/data_extraction.rs:670
- Edited copy of a member (24 corresponding lines) crates/ts-pack-core/src/intel/data_extraction/configuration.rs:123
- Edited copy of a member (28 corresponding lines) crates/ts-pack-core/src/intel/data_extraction.rs:704
- Edited copy of a member (19 corresponding lines) crates/ts-pack-core/src/intel/data_extraction.rs:537
- Edited copy of a member (14 corresponding lines) crates/ts-pack-core/src/json_utils.rs:9
- Edited copy of a member (8 corresponding lines) crates/ts-pack-core/src/lib.rs:795
- Edited copies of one member (3 members, 12+ corresponding lines) crates/ts-pack-core/src/lib.rs:717
- Edited copies of one member (4 members, 7+ corresponding lines) crates/ts-pack-core/src/parsing.rs:437
- Edited copies of one member (3 members, 4+ corresponding lines) crates/ts-pack-core/src/intel/c.rs:213
- Edited copy of a member (4 corresponding lines) crates/ts-pack-core/src/intel/elixir.rs:80
- Duplicated block (11 lines × 2) crates/ts-pack-core/src/intel/data_extraction.rs:93
- Duplicated block (8 lines × 3) crates/ts-pack-core/src/intel/data_extraction/configuration.rs:45
- Duplicated block (8 lines × 2) crates/ts-pack-core/src/download.rs:329
- Duplicated block (6 lines × 3) crates/ts-pack-core/src/intel/data_extraction.rs:617
- Duplicated block (6 lines × 2) crates/ts-pack-core/src/download/cache.rs:310
- Duplicated block (11 lines × 8) crates/ts-pack-core/src/intel/data_extraction.rs:242
- Duplicated block (8 lines × 6) crates/ts-pack-core/src/intel/data_extraction.rs:421
- Duplicated block (5 lines × 2) crates/ts-pack-core/src/intel/data_extraction.rs:558
- Edited copy of a member (67 corresponding lines) fixtures/bench/python/large.py:267
- Edited copies of one member (3 members, 35+ corresponding lines) fixtures/bench/python/large.py:217
- Duplicated block (28 lines × 2) scripts/check_grammar_updates.py:57
- Duplicated block (10 lines × 3) fixtures/bench/python/large.py:237
- Duplicated block (9 lines × 2) scripts/lint_grammar_licenses.py:132
- Off the main sequence: tree-sitter-language-pack
- Low cohesion: TsPackMcp (LCOM4 15) crates/ts-pack-cli/src/commands/mcp.rs:206
- SAST runs, but gates no merge
- Type Safety
- Duplication concentrated across 7 sibling directories (5 clone groups) grammars/wolfram/grammar.js:585
- Duplicated block with local edits (19 matched lines × 2 locations) cli-proxy/npm/install.js:219
- Duplicated block (13 lines × 2 locations) grammars/reason/grammar.js:241
- Duplicated block (12 lines × 2 locations) grammars/wolfram/grammar.js:5
- Duplicated block (9 lines × 2 locations) grammars/xquery/grammar.js:376
- Duplicated block (5 lines × 2 locations) grammars/graphql/grammar.js:74
- grammars/wolfram/grammar.js: 882 lines of code grammars/wolfram/grammar.js:1
- grammars/xquery/grammar.js: 832 lines of code grammars/xquery/grammar.js:1
- grammars/reason/grammar.js: 712 lines of code grammars/reason/grammar.js:1
- Unused dependency '@textlint-rule/textlint-rule-no-invalid-control-character' package.json:10
- Unused dependency 'textlint-filter-rule-comments' package.json:12
- Unused dependency 'textlint-filter-rule-node-types' package.json:13
- Unused dependency 'textlint-plugin-mdx' package.json:14
- Unused dependency 'textlint-rule-common-misspellings' package.json:15
- Unused dependency 'textlint-rule-en-capitalization' package.json:16
- Unused dependency 'textlint-rule-no-empty-section' package.json:17
- Unused dependency 'textlint-rule-no-start-duplicated-conjunction' package.json:18
- Unused dependency 'textlint-rule-no-surrogate-pair' package.json:19
- Unused dependency 'textlint-rule-no-zero-width-spaces' package.json:20
- Unused dependency 'textlint-rule-stop-words' package.json:21
- Unused dependency 'textlint-rule-terminology' package.json:22
- Unused dependency 'textlint-rule-write-good' package.json:23
- Unused dependency 'sharp' docs-site/package.json:17
Minor — 54 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Silent fallback default on Err crates/ts-pack-core/src/registry.rs:264
- Silent fallback default on Err packages/swift/rust/src/lib.rs:1236
- Silent fallback default on Err packages/swift/rust/src/lib.rs:1243
- Silent fallback default on Err packages/swift/rust/src/lib.rs:1389
- Silent fallback default on Err packages/swift/rust/src/lib.rs:1396
- Silent fallback default on Err packages/swift/rust/src/lib.rs:1471
- Silent fallback default on Err packages/swift/rust/src/lib.rs:1483
- Silent fallback default on Err packages/swift/rust/src/lib.rs:2032
- Silent fallback default on Err packages/swift/rust/src/lib.rs:2039
- Silent fallback default on Err packages/swift/rust/src/lib.rs:2046
- Silent fallback default on Err packages/swift/rust/src/lib.rs:2053
- Silent fallback default on Err packages/swift/rust/src/lib.rs:2060
- Silent fallback default on Err packages/swift/rust/src/lib.rs:2067
- Silent fallback default on Err packages/swift/rust/src/lib.rs:2074
- Silent fallback default on Err packages/swift/rust/src/lib.rs:2081
- Silent fallback default on Err packages/swift/rust/src/lib.rs:2189
- Silent fallback default on Err packages/swift/rust/src/lib.rs:2204
- Silent fallback default on Err packages/swift/rust/src/lib.rs:2249
- Public type used only inside its own library packages/csharp/TreeSitterLanguagePack/ByteArrayJsonConverter.cs:24
- Public type used only inside its own library packages/csharp/TreeSitterLanguagePack/DocstringFormat.cs:74
- Public type used only inside its own library packages/csharp/TreeSitterLanguagePack/StructureKind.cs:101
- Public type used only inside its own library packages/csharp/TreeSitterLanguagePack/SymbolKind.cs:87
- Duplicated predicate scripts/_vendor_licenses.py:28
- Duplicated predicate crates/ts-pack-core/src/intel/extract.rs:233
- Duplicated predicate crates/ts-pack-core/src/intel/chunking.rs:566
- ADR considers only one option adrs/0000-record-architecture-decisions.md:17
- ADR considers only one option adrs/0005-permissively-licensed-grammars-only.md:17
- Silent fallback default on parse failure scripts/build_grammar_notices.py:193
- Silent fallback default on parse failure scripts/clone_vendors.py:154
- REDACTED
- REDACTED
- REDACTED
- No dependency-update automation e2e/csharp/TreeSitterLanguagePack.E2eTests.csproj:23
- Unused module-local declaration 'optional0' grammars/wolfram/grammar.js:64
- Unused module-local declaration 'choice0' grammars/wolfram/grammar.js:69
- Null-forgiving operator (`!`) suppressions override nullable warnings
Minor — 1 finding(s)
- Outdated: tree-sitter-language-pack
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-9738ba403a414841a244027e95a7ac0d/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-9738ba403a414841a244027e95a7ac0d/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=157" --report-format json --report-path /tmp/watchdog-gitleaks-9738ba403a414841a244027e95a7ac0d/history-2.json --exit-code 0 --source . | 0 | — |
| 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-9738ba403a414841a244027e95a7ac0d/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 --exclude .cargo --exclude crates/tree-sitter-language-pack-jni --exclude crates/ts-pack-core-ffi --exclude crates/ts-pack-core-node --exclude crates/ts-pack-core-php/src --exclude crates/ts-pack-core-wasm --exclude docs-site/src/content/docs/reference --exclude docs-site/src/snippets/generated/c --exclude docs-site/src/snippets/generated/csharp --exclude docs-site/src/snippets/generated/dart --exclude docs-site/src/snippets/generated/elixir --exclude docs-site/src/snippets/generated/go --exclude docs-site/src/snippets/generated/java --exclude docs-site/src/snippets/generated/kotlin-android/data_extraction --exclude docs-site/src/snippets/generated/kotlin-android/error-handling --exclude docs-site/src/snippets/generated/kotlin-android/language-detection --exclude docs-site/src/snippets/generated/kotlin-android/parsing --exclude docs-site/src/snippets/generated/kotlin-android/process --exclude docs-site/src/snippets/generated/kotlin-android/query --exclude docs-site/src/snippets/generated/kotlin-android/registry --exclude docs-site/src/snippets/generated/kotlin-android/smoke --exclude docs-site/src/snippets/generated/php --exclude docs-site/src/snippets/generated/python --exclude docs-site/src/snippets/generated/ruby --exclude docs-site/src/snippets/generated/rust --exclude docs-site/src/snippets/generated/swift --exclude docs-site/src/snippets/generated/typescript --exclude docs-site/src/snippets/generated/wasm/data_extraction --exclude docs-site/src/snippets/generated/wasm/error-handling --exclude docs-site/src/snippets/generated/wasm/language-detection --exclude docs-site/src/snippets/generated/wasm/parsing --exclude docs-site/src/snippets/generated/wasm/process --exclude docs-site/src/snippets/generated/wasm/query --exclude docs-site/src/snippets/generated/wasm/registry --exclude docs-site/src/snippets/generated/wasm/smoke --exclude docs-site/src/snippets/generated/zig --exclude e2e --exclude packages/csharp --exclude packages/dart --exclude packages/elixir --exclude packages/go --exclude packages/java --exclude packages/kotlin-android --exclude packages/python --exclude packages/ruby --exclude packages/swift --exclude packages/zig --exclude plugin/.opencode/plugins --exclude test_apps . | 783 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 6 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | 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. semgrep could not parse 1 file(s) — `crates/ts-pack-core-php/stubs/tree_sitter_language_pack_extension.php` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |