Executive summary
duckdb/duckdb-rs falls short of our standard for production because we found no recorded design decisions and no architecture document or diagram, and the documentation refers to four links that don't exist. It scores 55.4 out of 100 and is rated Adequate, and all 57 of its critical findings are security problems.
Maturity, at 42.9, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the two parts of the code only one person knows, worth about 4.2 points. Recording design decisions would lift Maturity itself, worth about 7.8 points. Raising Maturity to 70 would lift the score to about 63.8.
Thirty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seventeen weaknesses in the code could be used by an attacker, and nine secrets can leak from the build pipeline. Pinning each tool to an exact version, fixing the weaknesses the scanner points to and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once.
The product code is 105,272 lines, about €110,000 to rebuild.
If Maturity rose from 42.9 to 70, the lowest score rated Strong, the score would rise from 55.4 to about 63.8.
Rebuild cost: about €110,000 · Estimate
| Cost to rebuild | €38,000 to €190,000, for 632 to 2,006 hours of work, about 0.8 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 55. 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 | Large: 105,272 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 duckdb.core.logical_type | 2 duckdb.types.to_sql | 3 duckdb_neo.builder_helpers | 4 duckdb.core.vector.flat | 5 duckdb.types.value_ref | 6 duckdb_neo.instance | 7 duckdb_neo.vector.element | 8 duckdb.core.vector.array | 9 duckdb.types.from_sql | 10 duckdb_neo.vector.rows | 11 duckdb.core.vector.struct | 12 duckdb.types.decimal | 13 duckdb_neo.types.list | 14 duckdb.core.vector.list | 15 duckdb.types.value | 16 duckdb_neo.vector.reader | 17 duckdb.core.data_chunk | 18 duckdb.types.bind_container | 19 duckdb.vtab.function | 20 duckdb_neo.vector.writer | 21 duckdb.inner_connection | 22 duckdb_neo.vector | 23 duckdb | 24 duckdb_neo.data_chunk | 25 duckdb.statement | 26 duckdb_neo.connection | 27 duckdb_neo.value | 28 duckdb_neo.types | 29 duckdb_neo.logical_type | 30 duckdb_neo.types.temporal | 31 duckdb_neo.types.uuid | 32 duckdb_neo.bind_arguments | 33 duckdb_neo.signature | 34 duckdb_neo.types.array | 35 duckdb_neo.types.decimal | 36 duckdb_neo.types.enums | 37 duckdb_neo.types.map | 38 duckdb_neo.aggregate | 39 duckdb_neo.scalar | 40 duckdb_neo.table_function |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 duckdb.core.logical_type | ||||||||||||||||||||||||||||||||||||||||
| 2 duckdb.types.to_sql | ||||||||||||||||||||||||||||||||||||||||
| 3 duckdb_neo.builder_helpers | ||||||||||||||||||||||||||||||||||||||||
| 4 duckdb.core.vector.flat | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 duckdb.types.value_ref | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 6 duckdb_neo.instance | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 duckdb_neo.vector.element | 2 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||||
| 8 duckdb.core.vector.array | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 duckdb.types.from_sql | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 duckdb_neo.vector.rows | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 11 duckdb.core.vector.struct | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 12 duckdb.types.decimal | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 13 duckdb_neo.types.list | 3 | 2 | 1 | 1 | 1 | 1 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||
| 14 duckdb.core.vector.list | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 duckdb.types.value | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 duckdb_neo.vector.reader | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 17 duckdb.core.data_chunk | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 duckdb.types.bind_container | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 duckdb.vtab.function | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 duckdb_neo.vector.writer | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 duckdb.inner_connection | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 duckdb_neo.vector | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 duckdb | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 duckdb_neo.data_chunk | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 duckdb.statement | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 duckdb_neo.connection | 2 | 4 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 duckdb_neo.value | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 duckdb_neo.types | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 duckdb_neo.logical_type | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 duckdb_neo.types.temporal | 4 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 31 duckdb_neo.types.uuid | 4 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 32 duckdb_neo.bind_arguments | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 duckdb_neo.signature | 2 | |||||||||||||||||||||||||||||||||||||||
| 34 duckdb_neo.types.array | 3 | 2 | 1 | 1 | 1 | 1 | 1 | 3 | 2 | |||||||||||||||||||||||||||||||
| 35 duckdb_neo.types.decimal | 19 | 5 | 5 | 5 | 2 | 5 | 6 | |||||||||||||||||||||||||||||||||
| 36 duckdb_neo.types.enums | 3 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 duckdb_neo.types.map | 3 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||
| 38 duckdb_neo.aggregate | 1 | 1 | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 39 duckdb_neo.scalar | 1 | 1 | 1 | 5 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 40 duckdb_neo.table_function | 1 | 1 | 6 | 2 | 1 | 1 | 1 |
4→1 duckdb.core.vector.flat uses duckdb.core.logical_type✕
- Connections
- 1 pair of types, where a type in duckdb.core.vector.flat uses a type in duckdb.core.logical_type.
- The types involved
duckdb.core.vector.flat.FlatVector→duckdb.core.logical_type.LogicalTypeHandle
- Direction
- duckdb.core.vector.flat uses duckdb.core.logical_type, so a change to duckdb.core.logical_type can break duckdb.core.vector.flat, while a change to duckdb.core.vector.flat can't break duckdb.core.logical_type.
- Position
- Below the diagonal: duckdb.core.vector.flat uses a module listed above it, which is the healthy direction.
5→12 duckdb.types.value_ref uses duckdb.types.decimal part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb.types.value_ref uses a type in duckdb.types.decimal.
- The types involved
duckdb.types.value_ref.ValueRef→duckdb.types.decimal.Decimal
- Direction
- duckdb.types.value_ref uses duckdb.types.decimal, so a change to duckdb.types.decimal can break duckdb.types.value_ref, while a change to duckdb.types.value_ref can't break duckdb.types.decimal.
- 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.
5→15 duckdb.types.value_ref uses duckdb.types.value part of a loop✕
- Connections
- 2 pairs of types, where a type in duckdb.types.value_ref uses a type in duckdb.types.value.
- The types involved
duckdb.types.value_ref.ValueRef→duckdb.types.value.Valueduckdb.types.value_ref.value_ref$module→duckdb.types.value.Value
- Direction
- duckdb.types.value_ref uses duckdb.types.value, so a change to duckdb.types.value can break duckdb.types.value_ref, while a change to duckdb.types.value_ref can't break duckdb.types.value.
- 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.
6→26 duckdb_neo.instance uses duckdb_neo.connection part of a loop✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.instance uses a type in duckdb_neo.connection.
- The types involved
duckdb_neo.instance.Instance→duckdb_neo.connection.HasFactoryduckdb_neo.instance.InstanceFactory→duckdb_neo.connection.Factory
- Direction
- duckdb_neo.instance uses duckdb_neo.connection, so a change to duckdb_neo.connection can break duckdb_neo.instance, while a change to duckdb_neo.instance can't break duckdb_neo.connection.
- 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.
7→16 duckdb_neo.vector.element uses duckdb_neo.vector.reader part of a loop✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.vector.element uses a type in duckdb_neo.vector.reader.
- The types involved
duckdb_neo.vector.element.ReadableNativeElement→duckdb_neo.vector.reader.VectorReaderduckdb_neo.vector.element.Unknown→duckdb_neo.vector.reader.VectorReader
- Direction
- duckdb_neo.vector.element uses duckdb_neo.vector.reader, so a change to duckdb_neo.vector.reader can break duckdb_neo.vector.element, while a change to duckdb_neo.vector.element can't break duckdb_neo.vector.reader.
- 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.
7→20 duckdb_neo.vector.element uses duckdb_neo.vector.writer part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.vector.element uses a type in duckdb_neo.vector.writer.
- The types involved
duckdb_neo.vector.element.WritableNativeElement→duckdb_neo.vector.writer.VectorWriter
- Direction
- duckdb_neo.vector.element uses duckdb_neo.vector.writer, so a change to duckdb_neo.vector.writer can break duckdb_neo.vector.element, while a change to duckdb_neo.vector.element can't break duckdb_neo.vector.writer.
- 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.
7→24 duckdb_neo.vector.element uses duckdb_neo.data_chunk part of a loop✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.vector.element uses a type in duckdb_neo.data_chunk.
- The types involved
duckdb_neo.vector.element.NativeElement→duckdb_neo.data_chunk.VectorCollectionduckdb_neo.vector.element.Unknown→duckdb_neo.data_chunk.VectorCollection
- Direction
- duckdb_neo.vector.element uses duckdb_neo.data_chunk, so a change to duckdb_neo.data_chunk can break duckdb_neo.vector.element, while a change to duckdb_neo.vector.element can't break duckdb_neo.data_chunk.
- 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.
7→29 duckdb_neo.vector.element uses duckdb_neo.logical_type part of a loop✕
- Connections
- 3 pairs of types, where a type in duckdb_neo.vector.element uses a type in duckdb_neo.logical_type.
- The types involved
duckdb_neo.vector.element.NativeElement→duckdb_neo.logical_type.LogicalTypeduckdb_neo.vector.element.Unknown→duckdb_neo.logical_type.LogicalTypeduckdb_neo.vector.element.element$module→duckdb_neo.logical_type.LogicalType
- Direction
- duckdb_neo.vector.element uses duckdb_neo.logical_type, so a change to duckdb_neo.logical_type can break duckdb_neo.vector.element, while a change to duckdb_neo.vector.element can't break duckdb_neo.logical_type.
- 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.
8→1 duckdb.core.vector.array uses duckdb.core.logical_type✕
- Connections
- 1 pair of types, where a type in duckdb.core.vector.array uses a type in duckdb.core.logical_type.
- The types involved
duckdb.core.vector.array.ArrayVector→duckdb.core.logical_type.LogicalTypeHandle
- Direction
- duckdb.core.vector.array uses duckdb.core.logical_type, so a change to duckdb.core.logical_type can break duckdb.core.vector.array, while a change to duckdb.core.vector.array can't break duckdb.core.logical_type.
- Position
- Below the diagonal: duckdb.core.vector.array uses a module listed above it, which is the healthy direction.
8→4 duckdb.core.vector.array uses duckdb.core.vector.flat✕
- Connections
- 1 pair of types, where a type in duckdb.core.vector.array uses a type in duckdb.core.vector.flat.
- The types involved
duckdb.core.vector.array.ArrayVector→duckdb.core.vector.flat.FlatVector
- Direction
- duckdb.core.vector.array uses duckdb.core.vector.flat, so a change to duckdb.core.vector.flat can break duckdb.core.vector.array, while a change to duckdb.core.vector.array can't break duckdb.core.vector.flat.
- Position
- Below the diagonal: duckdb.core.vector.array uses a module listed above it, which is the healthy direction.
9→5 duckdb.types.from_sql uses duckdb.types.value_ref✕
- Connections
- 1 pair of types, where a type in duckdb.types.from_sql uses a type in duckdb.types.value_ref.
- The types involved
duckdb.types.from_sql.FromSql→duckdb.types.value_ref.ValueRef
- Direction
- duckdb.types.from_sql uses duckdb.types.value_ref, so a change to duckdb.types.value_ref can break duckdb.types.from_sql, while a change to duckdb.types.from_sql can't break duckdb.types.value_ref.
- Position
- Below the diagonal: duckdb.types.from_sql uses a module listed above it, which is the healthy direction.
9→12 duckdb.types.from_sql uses duckdb.types.decimal part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb.types.from_sql uses a type in duckdb.types.decimal.
- The types involved
duckdb.types.from_sql.from_sql$module→duckdb.types.decimal.Decimal
- Direction
- duckdb.types.from_sql uses duckdb.types.decimal, so a change to duckdb.types.decimal can break duckdb.types.from_sql, while a change to duckdb.types.from_sql can't break duckdb.types.decimal.
- 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.
10→7 duckdb_neo.vector.rows uses duckdb_neo.vector.element✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.vector.rows uses a type in duckdb_neo.vector.element.
- The types involved
duckdb_neo.vector.rows.WithReader→duckdb_neo.vector.element.NativeElementduckdb_neo.vector.rows.WithWriter→duckdb_neo.vector.element.NativeElement
- Direction
- duckdb_neo.vector.rows uses duckdb_neo.vector.element, so a change to duckdb_neo.vector.element can break duckdb_neo.vector.rows, while a change to duckdb_neo.vector.rows can't break duckdb_neo.vector.element.
- Position
- Below the diagonal: duckdb_neo.vector.rows uses a module listed above it, which is the healthy direction.
10→22 duckdb_neo.vector.rows uses duckdb_neo.vector part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.vector.rows uses a type in duckdb_neo.vector.
- The types involved
duckdb_neo.vector.rows.WithReader→duckdb_neo.vector.Vector
- Direction
- duckdb_neo.vector.rows uses duckdb_neo.vector, so a change to duckdb_neo.vector can break duckdb_neo.vector.rows, while a change to duckdb_neo.vector.rows can't break duckdb_neo.vector.
- 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.
10→27 duckdb_neo.vector.rows uses duckdb_neo.value part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.vector.rows uses a type in duckdb_neo.value.
- The types involved
duckdb_neo.vector.rows.RowWriter→duckdb_neo.value.Value
- Direction
- duckdb_neo.vector.rows uses duckdb_neo.value, so a change to duckdb_neo.value can break duckdb_neo.vector.rows, while a change to duckdb_neo.vector.rows can't break duckdb_neo.value.
- 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.
11→1 duckdb.core.vector.struct uses duckdb.core.logical_type✕
- Connections
- 1 pair of types, where a type in duckdb.core.vector.struct uses a type in duckdb.core.logical_type.
- The types involved
duckdb.core.vector.struct.StructVector→duckdb.core.logical_type.LogicalTypeHandle
- Direction
- duckdb.core.vector.struct uses duckdb.core.logical_type, so a change to duckdb.core.logical_type can break duckdb.core.vector.struct, while a change to duckdb.core.vector.struct can't break duckdb.core.logical_type.
- Position
- Below the diagonal: duckdb.core.vector.struct uses a module listed above it, which is the healthy direction.
11→4 duckdb.core.vector.struct uses duckdb.core.vector.flat✕
- Connections
- 1 pair of types, where a type in duckdb.core.vector.struct uses a type in duckdb.core.vector.flat.
- The types involved
duckdb.core.vector.struct.StructVector→duckdb.core.vector.flat.FlatVector
- Direction
- duckdb.core.vector.struct uses duckdb.core.vector.flat, so a change to duckdb.core.vector.flat can break duckdb.core.vector.struct, while a change to duckdb.core.vector.struct can't break duckdb.core.vector.flat.
- Position
- Below the diagonal: duckdb.core.vector.struct uses a module listed above it, which is the healthy direction.
11→8 duckdb.core.vector.struct uses duckdb.core.vector.array✕
- Connections
- 1 pair of types, where a type in duckdb.core.vector.struct uses a type in duckdb.core.vector.array.
- The types involved
duckdb.core.vector.struct.StructVector→duckdb.core.vector.array.ArrayVector
- Direction
- duckdb.core.vector.struct uses duckdb.core.vector.array, so a change to duckdb.core.vector.array can break duckdb.core.vector.struct, while a change to duckdb.core.vector.struct can't break duckdb.core.vector.array.
- Position
- Below the diagonal: duckdb.core.vector.struct uses a module listed above it, which is the healthy direction.
11→14 duckdb.core.vector.struct uses duckdb.core.vector.list part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb.core.vector.struct uses a type in duckdb.core.vector.list.
- The types involved
duckdb.core.vector.struct.StructVector→duckdb.core.vector.list.ListVector
- Direction
- duckdb.core.vector.struct uses duckdb.core.vector.list, so a change to duckdb.core.vector.list can break duckdb.core.vector.struct, while a change to duckdb.core.vector.struct can't break duckdb.core.vector.list.
- 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.
12→2 duckdb.types.decimal uses duckdb.types.to_sql✕
- Connections
- 1 pair of types, where a type in duckdb.types.decimal uses a type in duckdb.types.to_sql.
- The types involved
duckdb.types.decimal.Decimal→duckdb.types.to_sql.ToSql
- Direction
- duckdb.types.decimal uses duckdb.types.to_sql, so a change to duckdb.types.to_sql can break duckdb.types.decimal, while a change to duckdb.types.decimal can't break duckdb.types.to_sql.
- Position
- Below the diagonal: duckdb.types.decimal uses a module listed above it, which is the healthy direction.
12→5 duckdb.types.decimal uses duckdb.types.value_ref✕
- Connections
- 1 pair of types, where a type in duckdb.types.decimal uses a type in duckdb.types.value_ref.
- The types involved
duckdb.types.decimal.Decimal→duckdb.types.value_ref.ValueRef
- Direction
- duckdb.types.decimal uses duckdb.types.value_ref, so a change to duckdb.types.value_ref can break duckdb.types.decimal, while a change to duckdb.types.decimal can't break duckdb.types.value_ref.
- Position
- Below the diagonal: duckdb.types.decimal uses a module listed above it, which is the healthy direction.
12→9 duckdb.types.decimal uses duckdb.types.from_sql✕
- Connections
- 2 pairs of types, where a type in duckdb.types.decimal uses a type in duckdb.types.from_sql.
- The types involved
duckdb.types.decimal.Decimal→duckdb.types.from_sql.FromSqlduckdb.types.decimal.decimal$module→duckdb.types.from_sql.FromSqlError
- Direction
- duckdb.types.decimal uses duckdb.types.from_sql, so a change to duckdb.types.from_sql can break duckdb.types.decimal, while a change to duckdb.types.decimal can't break duckdb.types.from_sql.
- Position
- Below the diagonal: duckdb.types.decimal uses a module listed above it, which is the healthy direction.
13→7 duckdb_neo.types.list uses duckdb_neo.vector.element✕
- Connections
- 3 pairs of types, where a type in duckdb_neo.types.list uses a type in duckdb_neo.vector.element.
- The types involved
duckdb_neo.types.list.List→duckdb_neo.vector.element.NativeElementduckdb_neo.types.list.List→duckdb_neo.vector.element.ReadableNativeElementduckdb_neo.types.list.List→duckdb_neo.vector.element.WritableNativeElement
- Direction
- duckdb_neo.types.list uses duckdb_neo.vector.element, so a change to duckdb_neo.vector.element can break duckdb_neo.types.list, while a change to duckdb_neo.types.list can't break duckdb_neo.vector.element.
- Position
- Below the diagonal: duckdb_neo.types.list uses a module listed above it, which is the healthy direction.
13→10 duckdb_neo.types.list uses duckdb_neo.vector.rows✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.types.list uses a type in duckdb_neo.vector.rows.
- The types involved
duckdb_neo.types.list.List→duckdb_neo.vector.rows.WithReaderduckdb_neo.types.list.List→duckdb_neo.vector.rows.WithWriter
- Direction
- duckdb_neo.types.list uses duckdb_neo.vector.rows, so a change to duckdb_neo.vector.rows can break duckdb_neo.types.list, while a change to duckdb_neo.types.list can't break duckdb_neo.vector.rows.
- Position
- Below the diagonal: duckdb_neo.types.list uses a module listed above it, which is the healthy direction.
13→16 duckdb_neo.types.list uses duckdb_neo.vector.reader part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.list uses a type in duckdb_neo.vector.reader.
- The types involved
duckdb_neo.types.list.List→duckdb_neo.vector.reader.VectorReader
- Direction
- duckdb_neo.types.list uses duckdb_neo.vector.reader, so a change to duckdb_neo.vector.reader can break duckdb_neo.types.list, while a change to duckdb_neo.types.list can't break duckdb_neo.vector.reader.
- 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.
13→20 duckdb_neo.types.list uses duckdb_neo.vector.writer part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.list uses a type in duckdb_neo.vector.writer.
- The types involved
duckdb_neo.types.list.List→duckdb_neo.vector.writer.VectorWriter
- Direction
- duckdb_neo.types.list uses duckdb_neo.vector.writer, so a change to duckdb_neo.vector.writer can break duckdb_neo.types.list, while a change to duckdb_neo.types.list can't break duckdb_neo.vector.writer.
- 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.
13→22 duckdb_neo.types.list uses duckdb_neo.vector part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.list uses a type in duckdb_neo.vector.
- The types involved
duckdb_neo.types.list.List→duckdb_neo.vector.Vector
- Direction
- duckdb_neo.types.list uses duckdb_neo.vector, so a change to duckdb_neo.vector can break duckdb_neo.types.list, while a change to duckdb_neo.types.list can't break duckdb_neo.vector.
- 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.
13→24 duckdb_neo.types.list uses duckdb_neo.data_chunk part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.list uses a type in duckdb_neo.data_chunk.
- The types involved
duckdb_neo.types.list.List→duckdb_neo.data_chunk.VectorCollection
- Direction
- duckdb_neo.types.list uses duckdb_neo.data_chunk, so a change to duckdb_neo.data_chunk can break duckdb_neo.types.list, while a change to duckdb_neo.types.list can't break duckdb_neo.data_chunk.
- 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.
13→27 duckdb_neo.types.list uses duckdb_neo.value part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.list uses a type in duckdb_neo.value.
- The types involved
duckdb_neo.types.list.List→duckdb_neo.value.Value
- Direction
- duckdb_neo.types.list uses duckdb_neo.value, so a change to duckdb_neo.value can break duckdb_neo.types.list, while a change to duckdb_neo.types.list can't break duckdb_neo.value.
- 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.
13→28 duckdb_neo.types.list uses duckdb_neo.types part of a loop✕
- Connections
- 3 pairs of types, where a type in duckdb_neo.types.list uses a type in duckdb_neo.types.
- The types involved
duckdb_neo.types.list.List→duckdb_neo.types.DuckDBTypeduckdb_neo.types.list.List→duckdb_neo.types.FromValueduckdb_neo.types.list.List→duckdb_neo.types.ToValue
- Direction
- duckdb_neo.types.list uses duckdb_neo.types, so a change to duckdb_neo.types can break duckdb_neo.types.list, while a change to duckdb_neo.types.list can't break duckdb_neo.types.
- 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.
13→29 duckdb_neo.types.list uses duckdb_neo.logical_type part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.list uses a type in duckdb_neo.logical_type.
- The types involved
duckdb_neo.types.list.List→duckdb_neo.logical_type.LogicalType
- Direction
- duckdb_neo.types.list uses duckdb_neo.logical_type, so a change to duckdb_neo.logical_type can break duckdb_neo.types.list, while a change to duckdb_neo.types.list can't break duckdb_neo.logical_type.
- 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.
14→4 duckdb.core.vector.list uses duckdb.core.vector.flat✕
- Connections
- 1 pair of types, where a type in duckdb.core.vector.list uses a type in duckdb.core.vector.flat.
- The types involved
duckdb.core.vector.list.ListVector→duckdb.core.vector.flat.FlatVector
- Direction
- duckdb.core.vector.list uses duckdb.core.vector.flat, so a change to duckdb.core.vector.flat can break duckdb.core.vector.list, while a change to duckdb.core.vector.list can't break duckdb.core.vector.flat.
- Position
- Below the diagonal: duckdb.core.vector.list uses a module listed above it, which is the healthy direction.
14→8 duckdb.core.vector.list uses duckdb.core.vector.array✕
- Connections
- 1 pair of types, where a type in duckdb.core.vector.list uses a type in duckdb.core.vector.array.
- The types involved
duckdb.core.vector.list.ListVector→duckdb.core.vector.array.ArrayVector
- Direction
- duckdb.core.vector.list uses duckdb.core.vector.array, so a change to duckdb.core.vector.array can break duckdb.core.vector.list, while a change to duckdb.core.vector.list can't break duckdb.core.vector.array.
- Position
- Below the diagonal: duckdb.core.vector.list uses a module listed above it, which is the healthy direction.
14→11 duckdb.core.vector.list uses duckdb.core.vector.struct✕
- Connections
- 1 pair of types, where a type in duckdb.core.vector.list uses a type in duckdb.core.vector.struct.
- The types involved
duckdb.core.vector.list.ListVector→duckdb.core.vector.struct.StructVector
- Direction
- duckdb.core.vector.list uses duckdb.core.vector.struct, so a change to duckdb.core.vector.struct can break duckdb.core.vector.list, while a change to duckdb.core.vector.list can't break duckdb.core.vector.struct.
- Position
- Below the diagonal: duckdb.core.vector.list uses a module listed above it, which is the healthy direction.
15→2 duckdb.types.value uses duckdb.types.to_sql✕
- Connections
- 1 pair of types, where a type in duckdb.types.value uses a type in duckdb.types.to_sql.
- The types involved
duckdb.types.value.Value→duckdb.types.to_sql.ToSql
- Direction
- duckdb.types.value uses duckdb.types.to_sql, so a change to duckdb.types.to_sql can break duckdb.types.value, while a change to duckdb.types.value can't break duckdb.types.to_sql.
- Position
- Below the diagonal: duckdb.types.value uses a module listed above it, which is the healthy direction.
15→5 duckdb.types.value uses duckdb.types.value_ref✕
- Connections
- 1 pair of types, where a type in duckdb.types.value uses a type in duckdb.types.value_ref.
- The types involved
duckdb.types.value.Value→duckdb.types.value_ref.ValueRef
- Direction
- duckdb.types.value uses duckdb.types.value_ref, so a change to duckdb.types.value_ref can break duckdb.types.value, while a change to duckdb.types.value can't break duckdb.types.value_ref.
- Position
- Below the diagonal: duckdb.types.value uses a module listed above it, which is the healthy direction.
15→9 duckdb.types.value uses duckdb.types.from_sql✕
- Connections
- 1 pair of types, where a type in duckdb.types.value uses a type in duckdb.types.from_sql.
- The types involved
duckdb.types.value.Value→duckdb.types.from_sql.FromSql
- Direction
- duckdb.types.value uses duckdb.types.from_sql, so a change to duckdb.types.from_sql can break duckdb.types.value, while a change to duckdb.types.value can't break duckdb.types.from_sql.
- Position
- Below the diagonal: duckdb.types.value uses a module listed above it, which is the healthy direction.
15→12 duckdb.types.value uses duckdb.types.decimal✕
- Connections
- 1 pair of types, where a type in duckdb.types.value uses a type in duckdb.types.decimal.
- The types involved
duckdb.types.value.Value→duckdb.types.decimal.Decimal
- Direction
- duckdb.types.value uses duckdb.types.decimal, so a change to duckdb.types.decimal can break duckdb.types.value, while a change to duckdb.types.value can't break duckdb.types.decimal.
- Position
- Below the diagonal: duckdb.types.value uses a module listed above it, which is the healthy direction.
16→10 duckdb_neo.vector.reader uses duckdb_neo.vector.rows✕
- Connections
- 1 pair of types, where a type in duckdb_neo.vector.reader uses a type in duckdb_neo.vector.rows.
- The types involved
duckdb_neo.vector.reader.VectorReader→duckdb_neo.vector.rows.RowReader
- Direction
- duckdb_neo.vector.reader uses duckdb_neo.vector.rows, so a change to duckdb_neo.vector.rows can break duckdb_neo.vector.reader, while a change to duckdb_neo.vector.reader can't break duckdb_neo.vector.rows.
- Position
- Below the diagonal: duckdb_neo.vector.reader uses a module listed above it, which is the healthy direction.
16→13 duckdb_neo.vector.reader uses duckdb_neo.types.list✕
- Connections
- 1 pair of types, where a type in duckdb_neo.vector.reader uses a type in duckdb_neo.types.list.
- The types involved
duckdb_neo.vector.reader.VectorReader→duckdb_neo.types.list.ListIndex
- Direction
- duckdb_neo.vector.reader uses duckdb_neo.types.list, so a change to duckdb_neo.types.list can break duckdb_neo.vector.reader, while a change to duckdb_neo.vector.reader can't break duckdb_neo.types.list.
- Position
- Below the diagonal: duckdb_neo.vector.reader uses a module listed above it, which is the healthy direction.
16→22 duckdb_neo.vector.reader uses duckdb_neo.vector part of a loop✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.vector.reader uses a type in duckdb_neo.vector.
- The types involved
duckdb_neo.vector.reader.CachedReader→duckdb_neo.vector.StorageKindduckdb_neo.vector.reader.VectorReader→duckdb_neo.vector.Vector
- Direction
- duckdb_neo.vector.reader uses duckdb_neo.vector, so a change to duckdb_neo.vector can break duckdb_neo.vector.reader, while a change to duckdb_neo.vector.reader can't break duckdb_neo.vector.
- 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.
17→4 duckdb.core.data_chunk uses duckdb.core.vector.flat✕
- Connections
- 1 pair of types, where a type in duckdb.core.data_chunk uses a type in duckdb.core.vector.flat.
- The types involved
duckdb.core.data_chunk.DataChunkHandle→duckdb.core.vector.flat.FlatVector
- Direction
- duckdb.core.data_chunk uses duckdb.core.vector.flat, so a change to duckdb.core.vector.flat can break duckdb.core.data_chunk, while a change to duckdb.core.data_chunk can't break duckdb.core.vector.flat.
- Position
- Below the diagonal: duckdb.core.data_chunk uses a module listed above it, which is the healthy direction.
17→8 duckdb.core.data_chunk uses duckdb.core.vector.array✕
- Connections
- 1 pair of types, where a type in duckdb.core.data_chunk uses a type in duckdb.core.vector.array.
- The types involved
duckdb.core.data_chunk.DataChunkHandle→duckdb.core.vector.array.ArrayVector
- Direction
- duckdb.core.data_chunk uses duckdb.core.vector.array, so a change to duckdb.core.vector.array can break duckdb.core.data_chunk, while a change to duckdb.core.data_chunk can't break duckdb.core.vector.array.
- Position
- Below the diagonal: duckdb.core.data_chunk uses a module listed above it, which is the healthy direction.
17→11 duckdb.core.data_chunk uses duckdb.core.vector.struct✕
- Connections
- 1 pair of types, where a type in duckdb.core.data_chunk uses a type in duckdb.core.vector.struct.
- The types involved
duckdb.core.data_chunk.DataChunkHandle→duckdb.core.vector.struct.StructVector
- Direction
- duckdb.core.data_chunk uses duckdb.core.vector.struct, so a change to duckdb.core.vector.struct can break duckdb.core.data_chunk, while a change to duckdb.core.data_chunk can't break duckdb.core.vector.struct.
- Position
- Below the diagonal: duckdb.core.data_chunk uses a module listed above it, which is the healthy direction.
17→14 duckdb.core.data_chunk uses duckdb.core.vector.list✕
- Connections
- 1 pair of types, where a type in duckdb.core.data_chunk uses a type in duckdb.core.vector.list.
- The types involved
duckdb.core.data_chunk.DataChunkHandle→duckdb.core.vector.list.ListVector
- Direction
- duckdb.core.data_chunk uses duckdb.core.vector.list, so a change to duckdb.core.vector.list can break duckdb.core.data_chunk, while a change to duckdb.core.data_chunk can't break duckdb.core.vector.list.
- Position
- Below the diagonal: duckdb.core.data_chunk uses a module listed above it, which is the healthy direction.
18→1 duckdb.types.bind_container uses duckdb.core.logical_type✕
- Connections
- 2 pairs of types, where a type in duckdb.types.bind_container uses a type in duckdb.core.logical_type.
- The types involved
duckdb.types.bind_container.BuiltType→duckdb.core.logical_type.LogicalTypeHandleduckdb.types.bind_container.bind_container$module→duckdb.core.logical_type.LogicalTypeHandle
- Direction
- duckdb.types.bind_container uses duckdb.core.logical_type, so a change to duckdb.core.logical_type can break duckdb.types.bind_container, while a change to duckdb.types.bind_container can't break duckdb.core.logical_type.
- Position
- Below the diagonal: duckdb.types.bind_container uses a module listed above it, which is the healthy direction.
18→5 duckdb.types.bind_container uses duckdb.types.value_ref✕
- Connections
- 1 pair of types, where a type in duckdb.types.bind_container uses a type in duckdb.types.value_ref.
- The types involved
duckdb.types.bind_container.bind_container$module→duckdb.types.value_ref.TimeUnit
- Direction
- duckdb.types.bind_container uses duckdb.types.value_ref, so a change to duckdb.types.value_ref can break duckdb.types.bind_container, while a change to duckdb.types.bind_container can't break duckdb.types.value_ref.
- Position
- Below the diagonal: duckdb.types.bind_container uses a module listed above it, which is the healthy direction.
18→12 duckdb.types.bind_container uses duckdb.types.decimal✕
- Connections
- 1 pair of types, where a type in duckdb.types.bind_container uses a type in duckdb.types.decimal.
- The types involved
duckdb.types.bind_container.bind_container$module→duckdb.types.decimal.Decimal
- Direction
- duckdb.types.bind_container uses duckdb.types.decimal, so a change to duckdb.types.decimal can break duckdb.types.bind_container, while a change to duckdb.types.bind_container can't break duckdb.types.decimal.
- Position
- Below the diagonal: duckdb.types.bind_container uses a module listed above it, which is the healthy direction.
18→15 duckdb.types.bind_container uses duckdb.types.value✕
- Connections
- 1 pair of types, where a type in duckdb.types.bind_container uses a type in duckdb.types.value.
- The types involved
duckdb.types.bind_container.bind_container$module→duckdb.types.value.Value
- Direction
- duckdb.types.bind_container uses duckdb.types.value, so a change to duckdb.types.value can break duckdb.types.bind_container, while a change to duckdb.types.bind_container can't break duckdb.types.value.
- Position
- Below the diagonal: duckdb.types.bind_container uses a module listed above it, which is the healthy direction.
19→1 duckdb.vtab.function uses duckdb.core.logical_type✕
- Connections
- 2 pairs of types, where a type in duckdb.vtab.function uses a type in duckdb.core.logical_type.
- The types involved
duckdb.vtab.function.BindInfo→duckdb.core.logical_type.LogicalTypeHandleduckdb.vtab.function.TableFunction→duckdb.core.logical_type.LogicalTypeHandle
- Direction
- duckdb.vtab.function uses duckdb.core.logical_type, so a change to duckdb.core.logical_type can break duckdb.vtab.function, while a change to duckdb.vtab.function can't break duckdb.core.logical_type.
- Position
- Below the diagonal: duckdb.vtab.function uses a module listed above it, which is the healthy direction.
19→15 duckdb.vtab.function uses duckdb.types.value✕
- Connections
- 1 pair of types, where a type in duckdb.vtab.function uses a type in duckdb.types.value.
- The types involved
duckdb.vtab.function.BindInfo→duckdb.types.value.Value
- Direction
- duckdb.vtab.function uses duckdb.types.value, so a change to duckdb.types.value can break duckdb.vtab.function, while a change to duckdb.vtab.function can't break duckdb.types.value.
- Position
- Below the diagonal: duckdb.vtab.function uses a module listed above it, which is the healthy direction.
20→10 duckdb_neo.vector.writer uses duckdb_neo.vector.rows✕
- Connections
- 1 pair of types, where a type in duckdb_neo.vector.writer uses a type in duckdb_neo.vector.rows.
- The types involved
duckdb_neo.vector.writer.VectorWriter→duckdb_neo.vector.rows.RowWriter
- Direction
- duckdb_neo.vector.writer uses duckdb_neo.vector.rows, so a change to duckdb_neo.vector.rows can break duckdb_neo.vector.writer, while a change to duckdb_neo.vector.writer can't break duckdb_neo.vector.rows.
- Position
- Below the diagonal: duckdb_neo.vector.writer uses a module listed above it, which is the healthy direction.
20→16 duckdb_neo.vector.writer uses duckdb_neo.vector.reader✕
- Connections
- 1 pair of types, where a type in duckdb_neo.vector.writer uses a type in duckdb_neo.vector.reader.
- The types involved
duckdb_neo.vector.writer.VectorWriter→duckdb_neo.vector.reader.VectorReader
- Direction
- duckdb_neo.vector.writer uses duckdb_neo.vector.reader, so a change to duckdb_neo.vector.reader can break duckdb_neo.vector.writer, while a change to duckdb_neo.vector.writer can't break duckdb_neo.vector.reader.
- Position
- Below the diagonal: duckdb_neo.vector.writer uses a module listed above it, which is the healthy direction.
20→22 duckdb_neo.vector.writer uses duckdb_neo.vector part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.vector.writer uses a type in duckdb_neo.vector.
- The types involved
duckdb_neo.vector.writer.VectorWriter→duckdb_neo.vector.Vector
- Direction
- duckdb_neo.vector.writer uses duckdb_neo.vector, so a change to duckdb_neo.vector can break duckdb_neo.vector.writer, while a change to duckdb_neo.vector.writer can't break duckdb_neo.vector.
- 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.
20→27 duckdb_neo.vector.writer uses duckdb_neo.value part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.vector.writer uses a type in duckdb_neo.value.
- The types involved
duckdb_neo.vector.writer.VectorWriter→duckdb_neo.value.Value
- Direction
- duckdb_neo.vector.writer uses duckdb_neo.value, so a change to duckdb_neo.value can break duckdb_neo.vector.writer, while a change to duckdb_neo.vector.writer can't break duckdb_neo.value.
- 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.
21→19 duckdb.inner_connection uses duckdb.vtab.function✕
- Connections
- 1 pair of types, where a type in duckdb.inner_connection uses a type in duckdb.vtab.function.
- The types involved
duckdb.inner_connection.InnerConnection→duckdb.vtab.function.TableFunction
- Direction
- duckdb.inner_connection uses duckdb.vtab.function, so a change to duckdb.vtab.function can break duckdb.inner_connection, while a change to duckdb.inner_connection can't break duckdb.vtab.function.
- Position
- Below the diagonal: duckdb.inner_connection uses a module listed above it, which is the healthy direction.
21→23 duckdb.inner_connection uses duckdb part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb.inner_connection uses a type in duckdb.
- The types involved
duckdb.inner_connection.InnerConnection→duckdb.Connection
- Direction
- duckdb.inner_connection uses duckdb, so a change to duckdb can break duckdb.inner_connection, while a change to duckdb.inner_connection can't break duckdb.
- 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.
22→20 duckdb_neo.vector uses duckdb_neo.vector.writer✕
- Connections
- 1 pair of types, where a type in duckdb_neo.vector uses a type in duckdb_neo.vector.writer.
- The types involved
duckdb_neo.vector.Vector→duckdb_neo.vector.writer.VectorWriter
- Direction
- duckdb_neo.vector uses duckdb_neo.vector.writer, so a change to duckdb_neo.vector.writer can break duckdb_neo.vector, while a change to duckdb_neo.vector can't break duckdb_neo.vector.writer.
- Position
- Below the diagonal: duckdb_neo.vector uses a module listed above it, which is the healthy direction.
22→24 duckdb_neo.vector uses duckdb_neo.data_chunk part of a loop✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.vector uses a type in duckdb_neo.data_chunk.
- The types involved
duckdb_neo.vector.Vector→duckdb_neo.data_chunk.ChildrenMutduckdb_neo.vector.Vector→duckdb_neo.data_chunk.VectorCollection
- Direction
- duckdb_neo.vector uses duckdb_neo.data_chunk, so a change to duckdb_neo.data_chunk can break duckdb_neo.vector, while a change to duckdb_neo.vector can't break duckdb_neo.data_chunk.
- 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.
22→27 duckdb_neo.vector uses duckdb_neo.value part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.vector uses a type in duckdb_neo.value.
- The types involved
duckdb_neo.vector.Vector→duckdb_neo.value.Value
- Direction
- duckdb_neo.vector uses duckdb_neo.value, so a change to duckdb_neo.value can break duckdb_neo.vector, while a change to duckdb_neo.vector can't break duckdb_neo.value.
- 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.
22→29 duckdb_neo.vector uses duckdb_neo.logical_type part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.vector uses a type in duckdb_neo.logical_type.
- The types involved
duckdb_neo.vector.Vector→duckdb_neo.logical_type.LogicalType
- Direction
- duckdb_neo.vector uses duckdb_neo.logical_type, so a change to duckdb_neo.logical_type can break duckdb_neo.vector, while a change to duckdb_neo.vector can't break duckdb_neo.logical_type.
- 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.
23→21 duckdb uses duckdb.inner_connection✕
- Connections
- 2 pairs of types, where a type in duckdb uses a type in duckdb.inner_connection.
- The types involved
duckdb.Connection→duckdb.inner_connection.InnerConnectionduckdb.Connection→duckdb.inner_connection.InterruptHandle
- Direction
- duckdb uses duckdb.inner_connection, so a change to duckdb.inner_connection can break duckdb, while a change to duckdb can't break duckdb.inner_connection.
- Position
- Below the diagonal: duckdb uses a module listed above it, which is the healthy direction.
24→22 duckdb_neo.data_chunk uses duckdb_neo.vector✕
- Connections
- 1 pair of types, where a type in duckdb_neo.data_chunk uses a type in duckdb_neo.vector.
- The types involved
duckdb_neo.data_chunk.VectorCollection→duckdb_neo.vector.Access
- Direction
- duckdb_neo.data_chunk uses duckdb_neo.vector, so a change to duckdb_neo.vector can break duckdb_neo.data_chunk, while a change to duckdb_neo.data_chunk can't break duckdb_neo.vector.
- Position
- Below the diagonal: duckdb_neo.data_chunk uses a module listed above it, which is the healthy direction.
25→1 duckdb.statement uses duckdb.core.logical_type✕
- Connections
- 2 pairs of types, where a type in duckdb.statement uses a type in duckdb.core.logical_type.
- The types involved
duckdb.statement.Statement→duckdb.core.logical_type.LogicalTypeHandleduckdb.statement.Statement→duckdb.core.logical_type.LogicalTypeId
- Direction
- duckdb.statement uses duckdb.core.logical_type, so a change to duckdb.core.logical_type can break duckdb.statement, while a change to duckdb.statement can't break duckdb.core.logical_type.
- Position
- Below the diagonal: duckdb.statement uses a module listed above it, which is the healthy direction.
25→23 duckdb.statement uses duckdb✕
- Connections
- 1 pair of types, where a type in duckdb.statement uses a type in duckdb.
- The types involved
duckdb.statement.Statement→duckdb.Connection
- Direction
- duckdb.statement uses duckdb, so a change to duckdb can break duckdb.statement, while a change to duckdb.statement can't break duckdb.
- Position
- Below the diagonal: duckdb.statement uses a module listed above it, which is the healthy direction.
26→6 duckdb_neo.connection uses duckdb_neo.instance✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.connection uses a type in duckdb_neo.instance.
- The types involved
duckdb_neo.connection.Connection→duckdb_neo.instance.Instanceduckdb_neo.connection.Connection→duckdb_neo.instance.InstanceHandle
- Direction
- duckdb_neo.connection uses duckdb_neo.instance, so a change to duckdb_neo.instance can break duckdb_neo.connection, while a change to duckdb_neo.connection can't break duckdb_neo.instance.
- Position
- Below the diagonal: duckdb_neo.connection uses a module listed above it, which is the healthy direction.
26→24 duckdb_neo.connection uses duckdb_neo.data_chunk✕
- Connections
- 4 pairs of types, where a type in duckdb_neo.connection uses a type in duckdb_neo.data_chunk.
- The types involved
duckdb_neo.connection.Connection→duckdb_neo.data_chunk.DataChunkLinkduckdb_neo.connection.Connection→duckdb_neo.data_chunk.DataChunkRefduckdb_neo.connection.Context→duckdb_neo.data_chunk.DataChunkLinkduckdb_neo.connection.Context→duckdb_neo.data_chunk.DataChunkRef
- Direction
- duckdb_neo.connection uses duckdb_neo.data_chunk, so a change to duckdb_neo.data_chunk can break duckdb_neo.connection, while a change to duckdb_neo.connection can't break duckdb_neo.data_chunk.
- Position
- Below the diagonal: duckdb_neo.connection uses a module listed above it, which is the healthy direction.
26→27 duckdb_neo.connection uses duckdb_neo.value part of a loop✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.connection uses a type in duckdb_neo.value.
- The types involved
duckdb_neo.connection.FFILink→duckdb_neo.value.Valueduckdb_neo.connection.FFILink→duckdb_neo.value.ValueInput
- Direction
- duckdb_neo.connection uses duckdb_neo.value, so a change to duckdb_neo.value can break duckdb_neo.connection, while a change to duckdb_neo.connection can't break duckdb_neo.value.
- 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.
26→29 duckdb_neo.connection uses duckdb_neo.logical_type part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.connection uses a type in duckdb_neo.logical_type.
- The types involved
duckdb_neo.connection.FFILink→duckdb_neo.logical_type.LogicalType
- Direction
- duckdb_neo.connection uses duckdb_neo.logical_type, so a change to duckdb_neo.logical_type can break duckdb_neo.connection, while a change to duckdb_neo.connection can't break duckdb_neo.logical_type.
- 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.
27→26 duckdb_neo.value uses duckdb_neo.connection✕
- Connections
- 1 pair of types, where a type in duckdb_neo.value uses a type in duckdb_neo.connection.
- The types involved
duckdb_neo.value.value$module→duckdb_neo.connection.Factory
- Direction
- duckdb_neo.value uses duckdb_neo.connection, so a change to duckdb_neo.connection can break duckdb_neo.value, while a change to duckdb_neo.value can't break duckdb_neo.connection.
- Position
- Below the diagonal: duckdb_neo.value uses a module listed above it, which is the healthy direction.
27→29 duckdb_neo.value uses duckdb_neo.logical_type part of a loop✕
- Connections
- 1 pair of types, where a type in duckdb_neo.value uses a type in duckdb_neo.logical_type.
- The types involved
duckdb_neo.value.Value→duckdb_neo.logical_type.LogicalType
- Direction
- duckdb_neo.value uses duckdb_neo.logical_type, so a change to duckdb_neo.logical_type can break duckdb_neo.value, while a change to duckdb_neo.value can't break duckdb_neo.logical_type.
- 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.
28→27 duckdb_neo.types uses duckdb_neo.value✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types uses a type in duckdb_neo.value.
- The types involved
duckdb_neo.types.FromValue→duckdb_neo.value.Value
- Direction
- duckdb_neo.types uses duckdb_neo.value, so a change to duckdb_neo.value can break duckdb_neo.types, while a change to duckdb_neo.types can't break duckdb_neo.value.
- Position
- Below the diagonal: duckdb_neo.types uses a module listed above it, which is the healthy direction.
29→27 duckdb_neo.logical_type uses duckdb_neo.value✕
- Connections
- 1 pair of types, where a type in duckdb_neo.logical_type uses a type in duckdb_neo.value.
- The types involved
duckdb_neo.logical_type.LogicalType→duckdb_neo.value.Value
- Direction
- duckdb_neo.logical_type uses duckdb_neo.value, so a change to duckdb_neo.value can break duckdb_neo.logical_type, while a change to duckdb_neo.logical_type can't break duckdb_neo.value.
- Position
- Below the diagonal: duckdb_neo.logical_type uses a module listed above it, which is the healthy direction.
29→28 duckdb_neo.logical_type uses duckdb_neo.types✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.logical_type uses a type in duckdb_neo.types.
- The types involved
duckdb_neo.logical_type.LogicalType→duckdb_neo.types.FromValueduckdb_neo.logical_type.LogicalType→duckdb_neo.types.ToValue
- Direction
- duckdb_neo.logical_type uses duckdb_neo.types, so a change to duckdb_neo.types can break duckdb_neo.logical_type, while a change to duckdb_neo.logical_type can't break duckdb_neo.types.
- Position
- Below the diagonal: duckdb_neo.logical_type uses a module listed above it, which is the healthy direction.
30→7 duckdb_neo.types.temporal uses duckdb_neo.vector.element✕
- Connections
- 4 pairs of types, where a type in duckdb_neo.types.temporal uses a type in duckdb_neo.vector.element.
- The types involved
duckdb_neo.types.temporal.IntervalValue→duckdb_neo.vector.element.NativeElementduckdb_neo.types.temporal.IntervalValue→duckdb_neo.vector.element.PlainNativeduckdb_neo.types.temporal.IntervalValue→duckdb_neo.vector.element.ReadableNativeElementduckdb_neo.types.temporal.IntervalValue→duckdb_neo.vector.element.WritableNativeElement
- Direction
- duckdb_neo.types.temporal uses duckdb_neo.vector.element, so a change to duckdb_neo.vector.element can break duckdb_neo.types.temporal, while a change to duckdb_neo.types.temporal can't break duckdb_neo.vector.element.
- Position
- Below the diagonal: duckdb_neo.types.temporal uses a module listed above it, which is the healthy direction.
30→16 duckdb_neo.types.temporal uses duckdb_neo.vector.reader✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.temporal uses a type in duckdb_neo.vector.reader.
- The types involved
duckdb_neo.types.temporal.IntervalValue→duckdb_neo.vector.reader.VectorReader
- Direction
- duckdb_neo.types.temporal uses duckdb_neo.vector.reader, so a change to duckdb_neo.vector.reader can break duckdb_neo.types.temporal, while a change to duckdb_neo.types.temporal can't break duckdb_neo.vector.reader.
- Position
- Below the diagonal: duckdb_neo.types.temporal uses a module listed above it, which is the healthy direction.
30→20 duckdb_neo.types.temporal uses duckdb_neo.vector.writer✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.temporal uses a type in duckdb_neo.vector.writer.
- The types involved
duckdb_neo.types.temporal.IntervalValue→duckdb_neo.vector.writer.VectorWriter
- Direction
- duckdb_neo.types.temporal uses duckdb_neo.vector.writer, so a change to duckdb_neo.vector.writer can break duckdb_neo.types.temporal, while a change to duckdb_neo.types.temporal can't break duckdb_neo.vector.writer.
- Position
- Below the diagonal: duckdb_neo.types.temporal uses a module listed above it, which is the healthy direction.
30→27 duckdb_neo.types.temporal uses duckdb_neo.value✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.temporal uses a type in duckdb_neo.value.
- The types involved
duckdb_neo.types.temporal.IntervalValue→duckdb_neo.value.Value
- Direction
- duckdb_neo.types.temporal uses duckdb_neo.value, so a change to duckdb_neo.value can break duckdb_neo.types.temporal, while a change to duckdb_neo.types.temporal can't break duckdb_neo.value.
- Position
- Below the diagonal: duckdb_neo.types.temporal uses a module listed above it, which is the healthy direction.
30→28 duckdb_neo.types.temporal uses duckdb_neo.types✕
- Connections
- 3 pairs of types, where a type in duckdb_neo.types.temporal uses a type in duckdb_neo.types.
- The types involved
duckdb_neo.types.temporal.IntervalValue→duckdb_neo.types.DuckDBTypeduckdb_neo.types.temporal.IntervalValue→duckdb_neo.types.FromValueduckdb_neo.types.temporal.IntervalValue→duckdb_neo.types.ToValue
- Direction
- duckdb_neo.types.temporal uses duckdb_neo.types, so a change to duckdb_neo.types can break duckdb_neo.types.temporal, while a change to duckdb_neo.types.temporal can't break duckdb_neo.types.
- Position
- Below the diagonal: duckdb_neo.types.temporal uses a module listed above it, which is the healthy direction.
31→7 duckdb_neo.types.uuid uses duckdb_neo.vector.element✕
- Connections
- 4 pairs of types, where a type in duckdb_neo.types.uuid uses a type in duckdb_neo.vector.element.
- The types involved
duckdb_neo.types.uuid.UuidValueRaw→duckdb_neo.vector.element.NativeElementduckdb_neo.types.uuid.UuidValueRaw→duckdb_neo.vector.element.PlainNativeduckdb_neo.types.uuid.UuidValueRaw→duckdb_neo.vector.element.ReadableNativeElementduckdb_neo.types.uuid.UuidValueRaw→duckdb_neo.vector.element.WritableNativeElement
- Direction
- duckdb_neo.types.uuid uses duckdb_neo.vector.element, so a change to duckdb_neo.vector.element can break duckdb_neo.types.uuid, while a change to duckdb_neo.types.uuid can't break duckdb_neo.vector.element.
- Position
- Below the diagonal: duckdb_neo.types.uuid uses a module listed above it, which is the healthy direction.
31→16 duckdb_neo.types.uuid uses duckdb_neo.vector.reader✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.uuid uses a type in duckdb_neo.vector.reader.
- The types involved
duckdb_neo.types.uuid.UuidValueRaw→duckdb_neo.vector.reader.VectorReader
- Direction
- duckdb_neo.types.uuid uses duckdb_neo.vector.reader, so a change to duckdb_neo.vector.reader can break duckdb_neo.types.uuid, while a change to duckdb_neo.types.uuid can't break duckdb_neo.vector.reader.
- Position
- Below the diagonal: duckdb_neo.types.uuid uses a module listed above it, which is the healthy direction.
31→20 duckdb_neo.types.uuid uses duckdb_neo.vector.writer✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.uuid uses a type in duckdb_neo.vector.writer.
- The types involved
duckdb_neo.types.uuid.UuidValueRaw→duckdb_neo.vector.writer.VectorWriter
- Direction
- duckdb_neo.types.uuid uses duckdb_neo.vector.writer, so a change to duckdb_neo.vector.writer can break duckdb_neo.types.uuid, while a change to duckdb_neo.types.uuid can't break duckdb_neo.vector.writer.
- Position
- Below the diagonal: duckdb_neo.types.uuid uses a module listed above it, which is the healthy direction.
31→27 duckdb_neo.types.uuid uses duckdb_neo.value✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.uuid uses a type in duckdb_neo.value.
- The types involved
duckdb_neo.types.uuid.UuidValueRaw→duckdb_neo.value.Value
- Direction
- duckdb_neo.types.uuid uses duckdb_neo.value, so a change to duckdb_neo.value can break duckdb_neo.types.uuid, while a change to duckdb_neo.types.uuid can't break duckdb_neo.value.
- Position
- Below the diagonal: duckdb_neo.types.uuid uses a module listed above it, which is the healthy direction.
31→28 duckdb_neo.types.uuid uses duckdb_neo.types✕
- Connections
- 3 pairs of types, where a type in duckdb_neo.types.uuid uses a type in duckdb_neo.types.
- The types involved
duckdb_neo.types.uuid.UuidValueRaw→duckdb_neo.types.DuckDBTypeduckdb_neo.types.uuid.UuidValueRaw→duckdb_neo.types.FromValueduckdb_neo.types.uuid.UuidValueRaw→duckdb_neo.types.ToValue
- Direction
- duckdb_neo.types.uuid uses duckdb_neo.types, so a change to duckdb_neo.types can break duckdb_neo.types.uuid, while a change to duckdb_neo.types.uuid can't break duckdb_neo.types.
- Position
- Below the diagonal: duckdb_neo.types.uuid uses a module listed above it, which is the healthy direction.
32→27 duckdb_neo.bind_arguments uses duckdb_neo.value✕
- Connections
- 1 pair of types, where a type in duckdb_neo.bind_arguments uses a type in duckdb_neo.value.
- The types involved
duckdb_neo.bind_arguments.BindArgument→duckdb_neo.value.Value
- Direction
- duckdb_neo.bind_arguments uses duckdb_neo.value, so a change to duckdb_neo.value can break duckdb_neo.bind_arguments, while a change to duckdb_neo.bind_arguments can't break duckdb_neo.value.
- Position
- Below the diagonal: duckdb_neo.bind_arguments uses a module listed above it, which is the healthy direction.
32→29 duckdb_neo.bind_arguments uses duckdb_neo.logical_type✕
- Connections
- 1 pair of types, where a type in duckdb_neo.bind_arguments uses a type in duckdb_neo.logical_type.
- The types involved
duckdb_neo.bind_arguments.BindArgument→duckdb_neo.logical_type.LogicalType
- Direction
- duckdb_neo.bind_arguments uses duckdb_neo.logical_type, so a change to duckdb_neo.logical_type can break duckdb_neo.bind_arguments, while a change to duckdb_neo.bind_arguments can't break duckdb_neo.logical_type.
- Position
- Below the diagonal: duckdb_neo.bind_arguments uses a module listed above it, which is the healthy direction.
33→29 duckdb_neo.signature uses duckdb_neo.logical_type✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.signature uses a type in duckdb_neo.logical_type.
- The types involved
duckdb_neo.signature.FunctionParameter→duckdb_neo.logical_type.LogicalTypeduckdb_neo.signature.SignatureBuilder→duckdb_neo.logical_type.LogicalType
- Direction
- duckdb_neo.signature uses duckdb_neo.logical_type, so a change to duckdb_neo.logical_type can break duckdb_neo.signature, while a change to duckdb_neo.signature can't break duckdb_neo.logical_type.
- Position
- Below the diagonal: duckdb_neo.signature uses a module listed above it, which is the healthy direction.
34→7 duckdb_neo.types.array uses duckdb_neo.vector.element✕
- Connections
- 3 pairs of types, where a type in duckdb_neo.types.array uses a type in duckdb_neo.vector.element.
- The types involved
duckdb_neo.types.array.Array→duckdb_neo.vector.element.NativeElementduckdb_neo.types.array.Array→duckdb_neo.vector.element.ReadableNativeElementduckdb_neo.types.array.Array→duckdb_neo.vector.element.WritableNativeElement
- Direction
- duckdb_neo.types.array uses duckdb_neo.vector.element, so a change to duckdb_neo.vector.element can break duckdb_neo.types.array, while a change to duckdb_neo.types.array can't break duckdb_neo.vector.element.
- Position
- Below the diagonal: duckdb_neo.types.array uses a module listed above it, which is the healthy direction.
34→10 duckdb_neo.types.array uses duckdb_neo.vector.rows✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.types.array uses a type in duckdb_neo.vector.rows.
- The types involved
duckdb_neo.types.array.Array→duckdb_neo.vector.rows.WithReaderduckdb_neo.types.array.Array→duckdb_neo.vector.rows.WithWriter
- Direction
- duckdb_neo.types.array uses duckdb_neo.vector.rows, so a change to duckdb_neo.vector.rows can break duckdb_neo.types.array, while a change to duckdb_neo.types.array can't break duckdb_neo.vector.rows.
- Position
- Below the diagonal: duckdb_neo.types.array uses a module listed above it, which is the healthy direction.
34→16 duckdb_neo.types.array uses duckdb_neo.vector.reader✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.array uses a type in duckdb_neo.vector.reader.
- The types involved
duckdb_neo.types.array.Array→duckdb_neo.vector.reader.VectorReader
- Direction
- duckdb_neo.types.array uses duckdb_neo.vector.reader, so a change to duckdb_neo.vector.reader can break duckdb_neo.types.array, while a change to duckdb_neo.types.array can't break duckdb_neo.vector.reader.
- Position
- Below the diagonal: duckdb_neo.types.array uses a module listed above it, which is the healthy direction.
34→20 duckdb_neo.types.array uses duckdb_neo.vector.writer✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.array uses a type in duckdb_neo.vector.writer.
- The types involved
duckdb_neo.types.array.Array→duckdb_neo.vector.writer.VectorWriter
- Direction
- duckdb_neo.types.array uses duckdb_neo.vector.writer, so a change to duckdb_neo.vector.writer can break duckdb_neo.types.array, while a change to duckdb_neo.types.array can't break duckdb_neo.vector.writer.
- Position
- Below the diagonal: duckdb_neo.types.array uses a module listed above it, which is the healthy direction.
34→22 duckdb_neo.types.array uses duckdb_neo.vector✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.array uses a type in duckdb_neo.vector.
- The types involved
duckdb_neo.types.array.Array→duckdb_neo.vector.Vector
- Direction
- duckdb_neo.types.array uses duckdb_neo.vector, so a change to duckdb_neo.vector can break duckdb_neo.types.array, while a change to duckdb_neo.types.array can't break duckdb_neo.vector.
- Position
- Below the diagonal: duckdb_neo.types.array uses a module listed above it, which is the healthy direction.
34→24 duckdb_neo.types.array uses duckdb_neo.data_chunk✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.array uses a type in duckdb_neo.data_chunk.
- The types involved
duckdb_neo.types.array.Array→duckdb_neo.data_chunk.VectorCollection
- Direction
- duckdb_neo.types.array uses duckdb_neo.data_chunk, so a change to duckdb_neo.data_chunk can break duckdb_neo.types.array, while a change to duckdb_neo.types.array can't break duckdb_neo.data_chunk.
- Position
- Below the diagonal: duckdb_neo.types.array uses a module listed above it, which is the healthy direction.
34→27 duckdb_neo.types.array uses duckdb_neo.value✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.array uses a type in duckdb_neo.value.
- The types involved
duckdb_neo.types.array.Array→duckdb_neo.value.Value
- Direction
- duckdb_neo.types.array uses duckdb_neo.value, so a change to duckdb_neo.value can break duckdb_neo.types.array, while a change to duckdb_neo.types.array can't break duckdb_neo.value.
- Position
- Below the diagonal: duckdb_neo.types.array uses a module listed above it, which is the healthy direction.
34→28 duckdb_neo.types.array uses duckdb_neo.types✕
- Connections
- 3 pairs of types, where a type in duckdb_neo.types.array uses a type in duckdb_neo.types.
- The types involved
duckdb_neo.types.array.Array→duckdb_neo.types.DuckDBTypeduckdb_neo.types.array.Array→duckdb_neo.types.FromValueduckdb_neo.types.array.Array→duckdb_neo.types.ToValue
- Direction
- duckdb_neo.types.array uses duckdb_neo.types, so a change to duckdb_neo.types can break duckdb_neo.types.array, while a change to duckdb_neo.types.array can't break duckdb_neo.types.
- Position
- Below the diagonal: duckdb_neo.types.array uses a module listed above it, which is the healthy direction.
34→29 duckdb_neo.types.array uses duckdb_neo.logical_type✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.types.array uses a type in duckdb_neo.logical_type.
- The types involved
duckdb_neo.types.array.Array→duckdb_neo.logical_type.LogicalTypeduckdb_neo.types.array.array$module→duckdb_neo.logical_type.LogicalType
- Direction
- duckdb_neo.types.array uses duckdb_neo.logical_type, so a change to duckdb_neo.logical_type can break duckdb_neo.types.array, while a change to duckdb_neo.types.array can't break duckdb_neo.logical_type.
- Position
- Below the diagonal: duckdb_neo.types.array uses a module listed above it, which is the healthy direction.
35→7 duckdb_neo.types.decimal uses duckdb_neo.vector.element✕
- Connections
- 19 pairs of types, where a type in duckdb_neo.types.decimal uses a type in duckdb_neo.vector.element.
- The types involved
duckdb_neo.types.decimal.Decimal→duckdb_neo.vector.element.NativeElementduckdb_neo.types.decimal.Decimal→duckdb_neo.vector.element.ReadableNativeElementduckdb_neo.types.decimal.Decimal→duckdb_neo.vector.element.WritableNativeElementduckdb_neo.types.decimal.HugeDecimal→duckdb_neo.vector.element.NativeElementduckdb_neo.types.decimal.HugeDecimal→duckdb_neo.vector.element.PlainNativeduckdb_neo.types.decimal.HugeDecimal→duckdb_neo.vector.element.ReadableNativeElementduckdb_neo.types.decimal.HugeDecimal→duckdb_neo.vector.element.WritableNativeElementduckdb_neo.types.decimal.LongDecimal→duckdb_neo.vector.element.NativeElementduckdb_neo.types.decimal.LongDecimal→duckdb_neo.vector.element.PlainNativeduckdb_neo.types.decimal.LongDecimal→duckdb_neo.vector.element.ReadableNativeElementduckdb_neo.types.decimal.LongDecimal→duckdb_neo.vector.element.WritableNativeElementduckdb_neo.types.decimal.ShortDecimal→duckdb_neo.vector.element.NativeElementduckdb_neo.types.decimal.ShortDecimal→duckdb_neo.vector.element.PlainNativeduckdb_neo.types.decimal.ShortDecimal→duckdb_neo.vector.element.ReadableNativeElementduckdb_neo.types.decimal.ShortDecimal→duckdb_neo.vector.element.WritableNativeElementduckdb_neo.types.decimal.WordDecimal→duckdb_neo.vector.element.NativeElementduckdb_neo.types.decimal.WordDecimal→duckdb_neo.vector.element.PlainNativeduckdb_neo.types.decimal.WordDecimal→duckdb_neo.vector.element.ReadableNativeElementduckdb_neo.types.decimal.WordDecimal→duckdb_neo.vector.element.WritableNativeElement
- Direction
- duckdb_neo.types.decimal uses duckdb_neo.vector.element, so a change to duckdb_neo.vector.element can break duckdb_neo.types.decimal, while a change to duckdb_neo.types.decimal can't break duckdb_neo.vector.element.
- Position
- Below the diagonal: duckdb_neo.types.decimal uses a module listed above it, which is the healthy direction.
35→16 duckdb_neo.types.decimal uses duckdb_neo.vector.reader✕
- Connections
- 5 pairs of types, where a type in duckdb_neo.types.decimal uses a type in duckdb_neo.vector.reader.
- The types involved
duckdb_neo.types.decimal.Decimal→duckdb_neo.vector.reader.VectorReaderduckdb_neo.types.decimal.HugeDecimal→duckdb_neo.vector.reader.VectorReaderduckdb_neo.types.decimal.LongDecimal→duckdb_neo.vector.reader.VectorReaderduckdb_neo.types.decimal.ShortDecimal→duckdb_neo.vector.reader.VectorReaderduckdb_neo.types.decimal.WordDecimal→duckdb_neo.vector.reader.VectorReader
- Direction
- duckdb_neo.types.decimal uses duckdb_neo.vector.reader, so a change to duckdb_neo.vector.reader can break duckdb_neo.types.decimal, while a change to duckdb_neo.types.decimal can't break duckdb_neo.vector.reader.
- Position
- Below the diagonal: duckdb_neo.types.decimal uses a module listed above it, which is the healthy direction.
35→20 duckdb_neo.types.decimal uses duckdb_neo.vector.writer✕
- Connections
- 5 pairs of types, where a type in duckdb_neo.types.decimal uses a type in duckdb_neo.vector.writer.
- The types involved
duckdb_neo.types.decimal.Decimal→duckdb_neo.vector.writer.VectorWriterduckdb_neo.types.decimal.HugeDecimal→duckdb_neo.vector.writer.VectorWriterduckdb_neo.types.decimal.LongDecimal→duckdb_neo.vector.writer.VectorWriterduckdb_neo.types.decimal.ShortDecimal→duckdb_neo.vector.writer.VectorWriterduckdb_neo.types.decimal.WordDecimal→duckdb_neo.vector.writer.VectorWriter
- Direction
- duckdb_neo.types.decimal uses duckdb_neo.vector.writer, so a change to duckdb_neo.vector.writer can break duckdb_neo.types.decimal, while a change to duckdb_neo.types.decimal can't break duckdb_neo.vector.writer.
- Position
- Below the diagonal: duckdb_neo.types.decimal uses a module listed above it, which is the healthy direction.
35→24 duckdb_neo.types.decimal uses duckdb_neo.data_chunk✕
- Connections
- 5 pairs of types, where a type in duckdb_neo.types.decimal uses a type in duckdb_neo.data_chunk.
- The types involved
duckdb_neo.types.decimal.Decimal→duckdb_neo.data_chunk.VectorCollectionduckdb_neo.types.decimal.HugeDecimal→duckdb_neo.data_chunk.VectorCollectionduckdb_neo.types.decimal.LongDecimal→duckdb_neo.data_chunk.VectorCollectionduckdb_neo.types.decimal.ShortDecimal→duckdb_neo.data_chunk.VectorCollectionduckdb_neo.types.decimal.WordDecimal→duckdb_neo.data_chunk.VectorCollection
- Direction
- duckdb_neo.types.decimal uses duckdb_neo.data_chunk, so a change to duckdb_neo.data_chunk can break duckdb_neo.types.decimal, while a change to duckdb_neo.types.decimal can't break duckdb_neo.data_chunk.
- Position
- Below the diagonal: duckdb_neo.types.decimal uses a module listed above it, which is the healthy direction.
35→27 duckdb_neo.types.decimal uses duckdb_neo.value✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.types.decimal uses a type in duckdb_neo.value.
- The types involved
duckdb_neo.types.decimal.Decimal→duckdb_neo.value.Valueduckdb_neo.types.decimal.DecimalValue→duckdb_neo.value.Value
- Direction
- duckdb_neo.types.decimal uses duckdb_neo.value, so a change to duckdb_neo.value can break duckdb_neo.types.decimal, while a change to duckdb_neo.types.decimal can't break duckdb_neo.value.
- Position
- Below the diagonal: duckdb_neo.types.decimal uses a module listed above it, which is the healthy direction.
35→28 duckdb_neo.types.decimal uses duckdb_neo.types✕
- Connections
- 5 pairs of types, where a type in duckdb_neo.types.decimal uses a type in duckdb_neo.types.
- The types involved
duckdb_neo.types.decimal.Decimal→duckdb_neo.types.DuckDBTypeduckdb_neo.types.decimal.Decimal→duckdb_neo.types.FromValueduckdb_neo.types.decimal.Decimal→duckdb_neo.types.ToValueduckdb_neo.types.decimal.DecimalValue→duckdb_neo.types.FromValueduckdb_neo.types.decimal.DecimalValue→duckdb_neo.types.ToValue
- Direction
- duckdb_neo.types.decimal uses duckdb_neo.types, so a change to duckdb_neo.types can break duckdb_neo.types.decimal, while a change to duckdb_neo.types.decimal can't break duckdb_neo.types.
- Position
- Below the diagonal: duckdb_neo.types.decimal uses a module listed above it, which is the healthy direction.
35→29 duckdb_neo.types.decimal uses duckdb_neo.logical_type✕
- Connections
- 6 pairs of types, where a type in duckdb_neo.types.decimal uses a type in duckdb_neo.logical_type.
- The types involved
duckdb_neo.types.decimal.Decimal→duckdb_neo.logical_type.LogicalTypeduckdb_neo.types.decimal.DecimalSignature→duckdb_neo.logical_type.LogicalTypeduckdb_neo.types.decimal.HugeDecimal→duckdb_neo.logical_type.LogicalTypeduckdb_neo.types.decimal.LongDecimal→duckdb_neo.logical_type.LogicalTypeduckdb_neo.types.decimal.ShortDecimal→duckdb_neo.logical_type.LogicalTypeduckdb_neo.types.decimal.WordDecimal→duckdb_neo.logical_type.LogicalType
- Direction
- duckdb_neo.types.decimal uses duckdb_neo.logical_type, so a change to duckdb_neo.logical_type can break duckdb_neo.types.decimal, while a change to duckdb_neo.types.decimal can't break duckdb_neo.logical_type.
- Position
- Below the diagonal: duckdb_neo.types.decimal uses a module listed above it, which is the healthy direction.
36→7 duckdb_neo.types.enums uses duckdb_neo.vector.element✕
- Connections
- 3 pairs of types, where a type in duckdb_neo.types.enums uses a type in duckdb_neo.vector.element.
- The types involved
duckdb_neo.types.enums.EnumIndex→duckdb_neo.vector.element.NativeElementduckdb_neo.types.enums.EnumIndex→duckdb_neo.vector.element.ReadableNativeElementduckdb_neo.types.enums.EnumIndex→duckdb_neo.vector.element.WritableNativeElement
- Direction
- duckdb_neo.types.enums uses duckdb_neo.vector.element, so a change to duckdb_neo.vector.element can break duckdb_neo.types.enums, while a change to duckdb_neo.types.enums can't break duckdb_neo.vector.element.
- Position
- Below the diagonal: duckdb_neo.types.enums uses a module listed above it, which is the healthy direction.
36→16 duckdb_neo.types.enums uses duckdb_neo.vector.reader✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.enums uses a type in duckdb_neo.vector.reader.
- The types involved
duckdb_neo.types.enums.EnumIndex→duckdb_neo.vector.reader.VectorReader
- Direction
- duckdb_neo.types.enums uses duckdb_neo.vector.reader, so a change to duckdb_neo.vector.reader can break duckdb_neo.types.enums, while a change to duckdb_neo.types.enums can't break duckdb_neo.vector.reader.
- Position
- Below the diagonal: duckdb_neo.types.enums uses a module listed above it, which is the healthy direction.
36→20 duckdb_neo.types.enums uses duckdb_neo.vector.writer✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.enums uses a type in duckdb_neo.vector.writer.
- The types involved
duckdb_neo.types.enums.EnumIndex→duckdb_neo.vector.writer.VectorWriter
- Direction
- duckdb_neo.types.enums uses duckdb_neo.vector.writer, so a change to duckdb_neo.vector.writer can break duckdb_neo.types.enums, while a change to duckdb_neo.types.enums can't break duckdb_neo.vector.writer.
- Position
- Below the diagonal: duckdb_neo.types.enums uses a module listed above it, which is the healthy direction.
36→24 duckdb_neo.types.enums uses duckdb_neo.data_chunk✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.enums uses a type in duckdb_neo.data_chunk.
- The types involved
duckdb_neo.types.enums.EnumIndex→duckdb_neo.data_chunk.VectorCollection
- Direction
- duckdb_neo.types.enums uses duckdb_neo.data_chunk, so a change to duckdb_neo.data_chunk can break duckdb_neo.types.enums, while a change to duckdb_neo.types.enums can't break duckdb_neo.data_chunk.
- Position
- Below the diagonal: duckdb_neo.types.enums uses a module listed above it, which is the healthy direction.
36→29 duckdb_neo.types.enums uses duckdb_neo.logical_type✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.enums uses a type in duckdb_neo.logical_type.
- The types involved
duckdb_neo.types.enums.EnumIndex→duckdb_neo.logical_type.LogicalType
- Direction
- duckdb_neo.types.enums uses duckdb_neo.logical_type, so a change to duckdb_neo.logical_type can break duckdb_neo.types.enums, while a change to duckdb_neo.types.enums can't break duckdb_neo.logical_type.
- Position
- Below the diagonal: duckdb_neo.types.enums uses a module listed above it, which is the healthy direction.
37→7 duckdb_neo.types.map uses duckdb_neo.vector.element✕
- Connections
- 3 pairs of types, where a type in duckdb_neo.types.map uses a type in duckdb_neo.vector.element.
- The types involved
duckdb_neo.types.map.Map→duckdb_neo.vector.element.NativeElementduckdb_neo.types.map.Map→duckdb_neo.vector.element.ReadableNativeElementduckdb_neo.types.map.Map→duckdb_neo.vector.element.WritableNativeElement
- Direction
- duckdb_neo.types.map uses duckdb_neo.vector.element, so a change to duckdb_neo.vector.element can break duckdb_neo.types.map, while a change to duckdb_neo.types.map can't break duckdb_neo.vector.element.
- Position
- Below the diagonal: duckdb_neo.types.map uses a module listed above it, which is the healthy direction.
37→10 duckdb_neo.types.map uses duckdb_neo.vector.rows✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.types.map uses a type in duckdb_neo.vector.rows.
- The types involved
duckdb_neo.types.map.Map→duckdb_neo.vector.rows.WithReaderduckdb_neo.types.map.Map→duckdb_neo.vector.rows.WithWriter
- Direction
- duckdb_neo.types.map uses duckdb_neo.vector.rows, so a change to duckdb_neo.vector.rows can break duckdb_neo.types.map, while a change to duckdb_neo.types.map can't break duckdb_neo.vector.rows.
- Position
- Below the diagonal: duckdb_neo.types.map uses a module listed above it, which is the healthy direction.
37→13 duckdb_neo.types.map uses duckdb_neo.types.list✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.map uses a type in duckdb_neo.types.list.
- The types involved
duckdb_neo.types.map.Map→duckdb_neo.types.list.ListIndex
- Direction
- duckdb_neo.types.map uses duckdb_neo.types.list, so a change to duckdb_neo.types.list can break duckdb_neo.types.map, while a change to duckdb_neo.types.map can't break duckdb_neo.types.list.
- Position
- Below the diagonal: duckdb_neo.types.map uses a module listed above it, which is the healthy direction.
37→16 duckdb_neo.types.map uses duckdb_neo.vector.reader✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.map uses a type in duckdb_neo.vector.reader.
- The types involved
duckdb_neo.types.map.Map→duckdb_neo.vector.reader.VectorReader
- Direction
- duckdb_neo.types.map uses duckdb_neo.vector.reader, so a change to duckdb_neo.vector.reader can break duckdb_neo.types.map, while a change to duckdb_neo.types.map can't break duckdb_neo.vector.reader.
- Position
- Below the diagonal: duckdb_neo.types.map uses a module listed above it, which is the healthy direction.
37→20 duckdb_neo.types.map uses duckdb_neo.vector.writer✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.map uses a type in duckdb_neo.vector.writer.
- The types involved
duckdb_neo.types.map.Map→duckdb_neo.vector.writer.VectorWriter
- Direction
- duckdb_neo.types.map uses duckdb_neo.vector.writer, so a change to duckdb_neo.vector.writer can break duckdb_neo.types.map, while a change to duckdb_neo.types.map can't break duckdb_neo.vector.writer.
- Position
- Below the diagonal: duckdb_neo.types.map uses a module listed above it, which is the healthy direction.
37→22 duckdb_neo.types.map uses duckdb_neo.vector✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.map uses a type in duckdb_neo.vector.
- The types involved
duckdb_neo.types.map.Map→duckdb_neo.vector.Vector
- Direction
- duckdb_neo.types.map uses duckdb_neo.vector, so a change to duckdb_neo.vector can break duckdb_neo.types.map, while a change to duckdb_neo.types.map can't break duckdb_neo.vector.
- Position
- Below the diagonal: duckdb_neo.types.map uses a module listed above it, which is the healthy direction.
37→24 duckdb_neo.types.map uses duckdb_neo.data_chunk✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.map uses a type in duckdb_neo.data_chunk.
- The types involved
duckdb_neo.types.map.Map→duckdb_neo.data_chunk.VectorCollection
- Direction
- duckdb_neo.types.map uses duckdb_neo.data_chunk, so a change to duckdb_neo.data_chunk can break duckdb_neo.types.map, while a change to duckdb_neo.types.map can't break duckdb_neo.data_chunk.
- Position
- Below the diagonal: duckdb_neo.types.map uses a module listed above it, which is the healthy direction.
37→27 duckdb_neo.types.map uses duckdb_neo.value✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.map uses a type in duckdb_neo.value.
- The types involved
duckdb_neo.types.map.Map→duckdb_neo.value.Value
- Direction
- duckdb_neo.types.map uses duckdb_neo.value, so a change to duckdb_neo.value can break duckdb_neo.types.map, while a change to duckdb_neo.types.map can't break duckdb_neo.value.
- Position
- Below the diagonal: duckdb_neo.types.map uses a module listed above it, which is the healthy direction.
37→28 duckdb_neo.types.map uses duckdb_neo.types✕
- Connections
- 3 pairs of types, where a type in duckdb_neo.types.map uses a type in duckdb_neo.types.
- The types involved
duckdb_neo.types.map.Map→duckdb_neo.types.DuckDBTypeduckdb_neo.types.map.Map→duckdb_neo.types.FromValueduckdb_neo.types.map.Map→duckdb_neo.types.ToValue
- Direction
- duckdb_neo.types.map uses duckdb_neo.types, so a change to duckdb_neo.types can break duckdb_neo.types.map, while a change to duckdb_neo.types.map can't break duckdb_neo.types.
- Position
- Below the diagonal: duckdb_neo.types.map uses a module listed above it, which is the healthy direction.
37→29 duckdb_neo.types.map uses duckdb_neo.logical_type✕
- Connections
- 1 pair of types, where a type in duckdb_neo.types.map uses a type in duckdb_neo.logical_type.
- The types involved
duckdb_neo.types.map.Map→duckdb_neo.logical_type.LogicalType
- Direction
- duckdb_neo.types.map uses duckdb_neo.logical_type, so a change to duckdb_neo.logical_type can break duckdb_neo.types.map, while a change to duckdb_neo.types.map can't break duckdb_neo.logical_type.
- Position
- Below the diagonal: duckdb_neo.types.map uses a module listed above it, which is the healthy direction.
38→3 duckdb_neo.aggregate uses duckdb_neo.builder_helpers✕
- Connections
- 1 pair of types, where a type in duckdb_neo.aggregate uses a type in duckdb_neo.builder_helpers.
- The types involved
duckdb_neo.aggregate.AggregateFunctionBuilder→duckdb_neo.builder_helpers.OpaqueHandle
- Direction
- duckdb_neo.aggregate uses duckdb_neo.builder_helpers, so a change to duckdb_neo.builder_helpers can break duckdb_neo.aggregate, while a change to duckdb_neo.aggregate can't break duckdb_neo.builder_helpers.
- Position
- Below the diagonal: duckdb_neo.aggregate uses a module listed above it, which is the healthy direction.
38→22 duckdb_neo.aggregate uses duckdb_neo.vector✕
- Connections
- 1 pair of types, where a type in duckdb_neo.aggregate uses a type in duckdb_neo.vector.
- The types involved
duckdb_neo.aggregate.AggregateCallbacks→duckdb_neo.vector.Vector
- Direction
- duckdb_neo.aggregate uses duckdb_neo.vector, so a change to duckdb_neo.vector can break duckdb_neo.aggregate, while a change to duckdb_neo.aggregate can't break duckdb_neo.vector.
- Position
- Below the diagonal: duckdb_neo.aggregate uses a module listed above it, which is the healthy direction.
38→24 duckdb_neo.aggregate uses duckdb_neo.data_chunk✕
- Connections
- 1 pair of types, where a type in duckdb_neo.aggregate uses a type in duckdb_neo.data_chunk.
- The types involved
duckdb_neo.aggregate.AggregateCallbacks→duckdb_neo.data_chunk.VectorCollection
- Direction
- duckdb_neo.aggregate uses duckdb_neo.data_chunk, so a change to duckdb_neo.data_chunk can break duckdb_neo.aggregate, while a change to duckdb_neo.aggregate can't break duckdb_neo.data_chunk.
- Position
- Below the diagonal: duckdb_neo.aggregate uses a module listed above it, which is the healthy direction.
38→26 duckdb_neo.aggregate uses duckdb_neo.connection✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.aggregate uses a type in duckdb_neo.connection.
- The types involved
duckdb_neo.aggregate.AggregateCallbacks→duckdb_neo.connection.Contextduckdb_neo.aggregate.aggregate$module→duckdb_neo.connection.Context
- Direction
- duckdb_neo.aggregate uses duckdb_neo.connection, so a change to duckdb_neo.connection can break duckdb_neo.aggregate, while a change to duckdb_neo.aggregate can't break duckdb_neo.connection.
- Position
- Below the diagonal: duckdb_neo.aggregate uses a module listed above it, which is the healthy direction.
38→29 duckdb_neo.aggregate uses duckdb_neo.logical_type✕
- Connections
- 1 pair of types, where a type in duckdb_neo.aggregate uses a type in duckdb_neo.logical_type.
- The types involved
duckdb_neo.aggregate.ReturnTypeHandle→duckdb_neo.logical_type.LogicalType
- Direction
- duckdb_neo.aggregate uses duckdb_neo.logical_type, so a change to duckdb_neo.logical_type can break duckdb_neo.aggregate, while a change to duckdb_neo.aggregate can't break duckdb_neo.logical_type.
- Position
- Below the diagonal: duckdb_neo.aggregate uses a module listed above it, which is the healthy direction.
38→32 duckdb_neo.aggregate uses duckdb_neo.bind_arguments✕
- Connections
- 1 pair of types, where a type in duckdb_neo.aggregate uses a type in duckdb_neo.bind_arguments.
- The types involved
duckdb_neo.aggregate.AggregateCallbacks→duckdb_neo.bind_arguments.BindArguments
- Direction
- duckdb_neo.aggregate uses duckdb_neo.bind_arguments, so a change to duckdb_neo.bind_arguments can break duckdb_neo.aggregate, while a change to duckdb_neo.aggregate can't break duckdb_neo.bind_arguments.
- Position
- Below the diagonal: duckdb_neo.aggregate uses a module listed above it, which is the healthy direction.
38→33 duckdb_neo.aggregate uses duckdb_neo.signature✕
- Connections
- 1 pair of types, where a type in duckdb_neo.aggregate uses a type in duckdb_neo.signature.
- The types involved
duckdb_neo.aggregate.AggregateFunctionBuilder→duckdb_neo.signature.SignatureBuilder
- Direction
- duckdb_neo.aggregate uses duckdb_neo.signature, so a change to duckdb_neo.signature can break duckdb_neo.aggregate, while a change to duckdb_neo.aggregate can't break duckdb_neo.signature.
- Position
- Below the diagonal: duckdb_neo.aggregate uses a module listed above it, which is the healthy direction.
39→3 duckdb_neo.scalar uses duckdb_neo.builder_helpers✕
- Connections
- 1 pair of types, where a type in duckdb_neo.scalar uses a type in duckdb_neo.builder_helpers.
- The types involved
duckdb_neo.scalar.ScalarFunctionBuilder→duckdb_neo.builder_helpers.OpaqueHandle
- Direction
- duckdb_neo.scalar uses duckdb_neo.builder_helpers, so a change to duckdb_neo.builder_helpers can break duckdb_neo.scalar, while a change to duckdb_neo.scalar can't break duckdb_neo.builder_helpers.
- Position
- Below the diagonal: duckdb_neo.scalar uses a module listed above it, which is the healthy direction.
39→22 duckdb_neo.scalar uses duckdb_neo.vector✕
- Connections
- 1 pair of types, where a type in duckdb_neo.scalar uses a type in duckdb_neo.vector.
- The types involved
duckdb_neo.scalar.ScalarCallbacks→duckdb_neo.vector.Vector
- Direction
- duckdb_neo.scalar uses duckdb_neo.vector, so a change to duckdb_neo.vector can break duckdb_neo.scalar, while a change to duckdb_neo.scalar can't break duckdb_neo.vector.
- Position
- Below the diagonal: duckdb_neo.scalar uses a module listed above it, which is the healthy direction.
39→24 duckdb_neo.scalar uses duckdb_neo.data_chunk✕
- Connections
- 1 pair of types, where a type in duckdb_neo.scalar uses a type in duckdb_neo.data_chunk.
- The types involved
duckdb_neo.scalar.ScalarCallbacks→duckdb_neo.data_chunk.VectorCollection
- Direction
- duckdb_neo.scalar uses duckdb_neo.data_chunk, so a change to duckdb_neo.data_chunk can break duckdb_neo.scalar, while a change to duckdb_neo.scalar can't break duckdb_neo.data_chunk.
- Position
- Below the diagonal: duckdb_neo.scalar uses a module listed above it, which is the healthy direction.
39→26 duckdb_neo.scalar uses duckdb_neo.connection✕
- Connections
- 5 pairs of types, where a type in duckdb_neo.scalar uses a type in duckdb_neo.connection.
- The types involved
duckdb_neo.scalar.ScalarBindCallbacks→duckdb_neo.connection.Contextduckdb_neo.scalar.ScalarCallbacks→duckdb_neo.connection.Contextduckdb_neo.scalar.ScalarInitCallbacks→duckdb_neo.connection.Contextduckdb_neo.scalar.ScalarResolveTypesCallbacks→duckdb_neo.connection.Contextduckdb_neo.scalar.scalar$module→duckdb_neo.connection.Context
- Direction
- duckdb_neo.scalar uses duckdb_neo.connection, so a change to duckdb_neo.connection can break duckdb_neo.scalar, while a change to duckdb_neo.scalar can't break duckdb_neo.connection.
- Position
- Below the diagonal: duckdb_neo.scalar uses a module listed above it, which is the healthy direction.
39→32 duckdb_neo.scalar uses duckdb_neo.bind_arguments✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.scalar uses a type in duckdb_neo.bind_arguments.
- The types involved
duckdb_neo.scalar.ScalarBindCallbacks→duckdb_neo.bind_arguments.BindArgumentsduckdb_neo.scalar.ScalarResolveTypesCallbacks→duckdb_neo.bind_arguments.BindArguments
- Direction
- duckdb_neo.scalar uses duckdb_neo.bind_arguments, so a change to duckdb_neo.bind_arguments can break duckdb_neo.scalar, while a change to duckdb_neo.scalar can't break duckdb_neo.bind_arguments.
- Position
- Below the diagonal: duckdb_neo.scalar uses a module listed above it, which is the healthy direction.
39→33 duckdb_neo.scalar uses duckdb_neo.signature✕
- Connections
- 1 pair of types, where a type in duckdb_neo.scalar uses a type in duckdb_neo.signature.
- The types involved
duckdb_neo.scalar.ScalarFunctionBuilder→duckdb_neo.signature.SignatureBuilder
- Direction
- duckdb_neo.scalar uses duckdb_neo.signature, so a change to duckdb_neo.signature can break duckdb_neo.scalar, while a change to duckdb_neo.scalar can't break duckdb_neo.signature.
- Position
- Below the diagonal: duckdb_neo.scalar uses a module listed above it, which is the healthy direction.
40→3 duckdb_neo.table_function uses duckdb_neo.builder_helpers✕
- Connections
- 1 pair of types, where a type in duckdb_neo.table_function uses a type in duckdb_neo.builder_helpers.
- The types involved
duckdb_neo.table_function.TableFunctionBuilder→duckdb_neo.builder_helpers.OpaqueHandle
- Direction
- duckdb_neo.table_function uses duckdb_neo.builder_helpers, so a change to duckdb_neo.builder_helpers can break duckdb_neo.table_function, while a change to duckdb_neo.table_function can't break duckdb_neo.builder_helpers.
- Position
- Below the diagonal: duckdb_neo.table_function uses a module listed above it, which is the healthy direction.
40→24 duckdb_neo.table_function uses duckdb_neo.data_chunk✕
- Connections
- 1 pair of types, where a type in duckdb_neo.table_function uses a type in duckdb_neo.data_chunk.
- The types involved
duckdb_neo.table_function.TableFunctionCallbacks→duckdb_neo.data_chunk.DataChunkRef
- Direction
- duckdb_neo.table_function uses duckdb_neo.data_chunk, so a change to duckdb_neo.data_chunk can break duckdb_neo.table_function, while a change to duckdb_neo.table_function can't break duckdb_neo.data_chunk.
- Position
- Below the diagonal: duckdb_neo.table_function uses a module listed above it, which is the healthy direction.
40→26 duckdb_neo.table_function uses duckdb_neo.connection✕
- Connections
- 6 pairs of types, where a type in duckdb_neo.table_function uses a type in duckdb_neo.connection.
- The types involved
duckdb_neo.table_function.TableClaimBatchCallbacks→duckdb_neo.connection.Contextduckdb_neo.table_function.TableFilterPushdownCallbacks→duckdb_neo.connection.Contextduckdb_neo.table_function.TableFunctionCallbacks→duckdb_neo.connection.Contextduckdb_neo.table_function.TableGetBindInfoCallbacks→duckdb_neo.connection.Contextduckdb_neo.table_function.TablePartitioningCallbacks→duckdb_neo.connection.Contextduckdb_neo.table_function.table_function$module→duckdb_neo.connection.Context
- Direction
- duckdb_neo.table_function uses duckdb_neo.connection, so a change to duckdb_neo.connection can break duckdb_neo.table_function, while a change to duckdb_neo.table_function can't break duckdb_neo.connection.
- Position
- Below the diagonal: duckdb_neo.table_function uses a module listed above it, which is the healthy direction.
40→27 duckdb_neo.table_function uses duckdb_neo.value✕
- Connections
- 2 pairs of types, where a type in duckdb_neo.table_function uses a type in duckdb_neo.value.
- The types involved
duckdb_neo.table_function.BindInfoApi→duckdb_neo.value.Valueduckdb_neo.table_function.PartitionData→duckdb_neo.value.Value
- Direction
- duckdb_neo.table_function uses duckdb_neo.value, so a change to duckdb_neo.value can break duckdb_neo.table_function, while a change to duckdb_neo.table_function can't break duckdb_neo.value.
- Position
- Below the diagonal: duckdb_neo.table_function uses a module listed above it, which is the healthy direction.
40→29 duckdb_neo.table_function uses duckdb_neo.logical_type✕
- Connections
- 1 pair of types, where a type in duckdb_neo.table_function uses a type in duckdb_neo.logical_type.
- The types involved
duckdb_neo.table_function.BindFunctionHandle→duckdb_neo.logical_type.LogicalType
- Direction
- duckdb_neo.table_function uses duckdb_neo.logical_type, so a change to duckdb_neo.logical_type can break duckdb_neo.table_function, while a change to duckdb_neo.table_function can't break duckdb_neo.logical_type.
- Position
- Below the diagonal: duckdb_neo.table_function uses a module listed above it, which is the healthy direction.
40→32 duckdb_neo.table_function uses duckdb_neo.bind_arguments✕
- Connections
- 1 pair of types, where a type in duckdb_neo.table_function uses a type in duckdb_neo.bind_arguments.
- The types involved
duckdb_neo.table_function.TableFunctionCallbacks→duckdb_neo.bind_arguments.BindArgument
- Direction
- duckdb_neo.table_function uses duckdb_neo.bind_arguments, so a change to duckdb_neo.bind_arguments can break duckdb_neo.table_function, while a change to duckdb_neo.table_function can't break duckdb_neo.bind_arguments.
- Position
- Below the diagonal: duckdb_neo.table_function uses a module listed above it, which is the healthy direction.
40→33 duckdb_neo.table_function uses duckdb_neo.signature✕
- Connections
- 1 pair of types, where a type in duckdb_neo.table_function uses a type in duckdb_neo.signature.
- The types involved
duckdb_neo.table_function.TableFunctionBuilder→duckdb_neo.signature.SignatureBuilder
- Direction
- duckdb_neo.table_function uses duckdb_neo.signature, so a change to duckdb_neo.signature can break duckdb_neo.table_function, while a change to duckdb_neo.table_function can't break duckdb_neo.signature.
- Position
- Below the diagonal: duckdb_neo.table_function 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 | 57 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 33 | Medium |
Roadmap
Top priorities: Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Reconcile the README with reality: crates/duckdb-loadable-macros/README.md links to `crates/duckdb-neo/extensions.md`, but `crates/duckdb-loadable-macros/crates/duckdb-neo/extensions.md` does not exist; crates/duckdb-loadable-macros/README.md links to `CONTRIBUTING.md`, but `crates/duckdb-loadable-macros/CONTRIBUTING.md` does not exist; crates/libduckdb-sys/README.md links to `crates/duckdb-neo/extensions.md`, but `crates/libduckdb-sys/crates/duckdb-neo/extensions.md` does not exist; crates/libduckdb-sys/README.md links to `CONTRIBUTING.md`, but `crates/libduckdb-sys/CONTRIBUTING.md` does not exist; Resolve the 2 Off-boarding risk finding(s) in Bus Factor.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Off-boarding risk finding(s) in Bus Factor. | +4.2 pts | Low | Bus Factor |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +7.8 pts | Medium | Architecture documentation |
| Reconcile the README with reality: crates/duckdb-loadable-macros/README.md links to `crates/duckdb-neo/extensions.md`, but `crates/duckdb-loadable-macros/crates/duckdb-neo/extensions.md` does not exist; crates/duckdb-loadable-macros/README.md links to `CONTRIBUTING.md`, but `crates/duckdb-loadable-macros/CONTRIBUTING.md` does not exist; crates/libduckdb-sys/README.md links to `crates/duckdb-neo/extensions.md`, but `crates/libduckdb-sys/crates/duckdb-neo/extensions.md` does not exist; crates/libduckdb-sys/README.md links to `CONTRIBUTING.md`, but `crates/libduckdb-sys/CONTRIBUTING.md` does not exist. | +6.1 pts | Medium | Documentation accuracy |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +2.4 pts | Low | Bus Factor |
| Resolve the 17 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (14), REDACTED, REDACTED. | +2.6 pts | Medium | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +1.1 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. | +0.9 pts | Low | Static Analysis (SAST) |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.2 pts | Medium | Release Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | 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.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium advisory (unsound): REDACTED |
| crates/duckdb/src/core/logical_type.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/duckdb-neo/src/types/bignum.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| crates/duckdb/src/core/vector/array.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| crates/duckdb/src/lib.rs | 6.9 | Mixed | Explicit Debt: TodoComment |
| crates/duckdb/src/statement.rs | 6.9 | Mixed | Explicit Debt: TodoComment |
| crates/duckdb-neo/src/copy_function/mod.rs | 7.1 | Mixed | Code Duplication: Edited copy of a member (26 corresponding lines) |
| crates/libduckdb-sys/buildtime_bindgen.rs | 7.1 | Mixed | Code Duplication: Near-duplicate member pair (69 shared lines) |
| crates/duckdb-neo/src/connection_options.rs | 7.1 | Mixed | Code Duplication: Edited copies of one member (5 members, 11+ corresponding lines) |
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 42 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 42 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, 237 of 257 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — 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. Most of this repository's production source (.rs) had no cyclomatic complexity computed for it: no function bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — 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. Most of this repository's production source (.rs) had no cognitive complexity computed for it: no function bodies were exposed for those file kinds by any language model this pass could load.
- D4 Code Duplication — 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 20 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .rs (103,845 lines, 99% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
- 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 Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- 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 source is present (.rs) and this repository declares a Cargo test suite (repository root, 140 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D15 Churn × Complexity Hotspots — 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. A hotspot is churn × complexity. Churn was measured (93988 line(s) across the 90-day window), but no complexity could be computed for .rs, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
- 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.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated 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.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- 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.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# or Visual Basic was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# and Visual Basic syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin, PHP, F# and Visual Basic source only, and no C# was loaded, and this repository's C, C++, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Kotlin, Scala, Go, Swift, Python and Ruby source only, and no C# was loaded, no Java, Kotlin, Scala, Go, Swift, Python or Ruby was found, and this repository's C, C++ is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — 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. 140 further occurrence(s) are not listed individually; the score already reflects all 180.
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
- 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.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- 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.
- 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 Dockerfile (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
D4 · Code Duplication
20 duplicated block group(s) detected. 1.4 % of the production lines (1,449 of 105,272) are in a reported copy. A further 48 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .rs (99% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
What to do
- Resolve the 7 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with connection.rs, bind_arguments.rs, function.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 5 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with structs.rs, array.rs, pragma.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with mod.rs (2), statement.rs, list_writer.rs. — One of this dimension's main actionable groups (5 warning-level).
D5 · Coupling
4 production modules (Cargo), 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 3 of the 4 (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)
2 of 122 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs, instance.rs. — One of this dimension's main actionable groups (2 warning-level).
D12 · Dependency Hygiene
6 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 401 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
D16 · Bus Factor
51 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/duckdb-neo/src/vector/tests.rs. Counted over 162 of the 178 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
22 deducted task-comment markers across 105272 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 19 TodoComment finding(s) in Explicit Debt — start with lib.rs (4), statement.rs (3), mod.rs (3). — One of this dimension's main actionable groups (19 warning-level).
- Resolve the 2 XxxComment finding(s) in Explicit Debt — start with appender_params.rs, params.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with row.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 6 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 5 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
57 finding(s): 0 critical, 57 high, 0 medium, 0 low. 30 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 3 file(s) — `crates/duckdb-neo/src/vector/init.rs` (line 32), `crates/libduckdb-sys/src/bindgen_bundled_version.rs` (line 906, line 910, line 914, …), `crates/libduckdb-sys/src/bindgen_bundled_version_v2.rs` (line 370, line 414, line 422, …) — 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 5 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 17 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (14), REDACTED, REDACTED. — One of this dimension's main actionable groups (17 issue-level).
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- No action in Static Analysis (SAST) — all 30 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 (30 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
25 finding(s): 0 critical, 0 high, 25 medium, 0 low.
What to do
- Resolve the 14 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (14). — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 7 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 2 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
1 of 162 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/duckdb/src/types/url.rs. Counted over 162 of the 178 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
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- 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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
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 2 platform declaration(s) and 0 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
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `step` does real work, but one of its branches is `unimplemented!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — crates/duckdb-neo/src/query_result.rs:225
- `write_arrow_array_to_vector_ref` does real work, but one of its branches is `Err` with a "not implemented" message — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — crates/duckdb/src/arrow_interop/to_duckdb.rs:250
- `value_ref_internal` does real work, but one of its branches is `unimplemented!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — crates/duckdb/src/row.rs:543
- `from` does real work, but one of its branches is `unimplemented!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — crates/duckdb/src/types/mod.rs:252
- `data_type` does real work, but one of its branches is `todo!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — crates/duckdb/src/types/value.rs:280
- `cargo_warning` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/libduckdb-sys/build_bundled_cmake.rs:551
- `code_to_str` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/libduckdb-sys/src/v1/error.rs:90
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
- crates/duckdb-loadable-macros/README.md links to `crates/duckdb-neo/extensions.md`, but `crates/duckdb-loadable-macros/crates/duckdb-neo/extensions.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — crates/duckdb-loadable-macros/README.md:109
- crates/duckdb-loadable-macros/README.md links to `CONTRIBUTING.md`, but `crates/duckdb-loadable-macros/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — crates/duckdb-loadable-macros/README.md:415
- crates/libduckdb-sys/README.md links to `crates/duckdb-neo/extensions.md`, but `crates/libduckdb-sys/crates/duckdb-neo/extensions.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — crates/libduckdb-sys/README.md:109
- crates/libduckdb-sys/README.md links to `CONTRIBUTING.md`, but `crates/libduckdb-sys/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — crates/libduckdb-sys/README.md:415
What to do
- Reconcile the README with reality: crates/duckdb-loadable-macros/README.md links to `crates/duckdb-neo/extensions.md`, but `crates/duckdb-loadable-macros/crates/duckdb-neo/extensions.md` does not exist; crates/duckdb-loadable-macros/README.md links to `CONTRIBUTING.md`, but `crates/duckdb-loadable-macros/CONTRIBUTING.md` does not exist; crates/libduckdb-sys/README.md links to `crates/duckdb-neo/extensions.md`, but `crates/libduckdb-sys/crates/duckdb-neo/extensions.md` does not exist; crates/libduckdb-sys/README.md links to `CONTRIBUTING.md`, but `crates/libduckdb-sys/CONTRIBUTING.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/libduckdb-sys`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `github-actions`, `gitsubmodule` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release. — REDACTED:15
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline
X12 · Unreachable branch
- `let code = match error.code { crate::error::DuckDBError::None => DuckDBError:…` follows `{ return; }` (line 104) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run. — crates/duckdb-neo/src/builder_helpers.rs:107
- `let extension = Extension { handle : input.extension, context : unsafe { Cont…` follows `{ return; }` (line 55) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run. — crates/duckdb-neo/src/extension.rs:58
- `Some(unsafe { T::get(self, index, index) })` follows `{ return None; }` (line 333) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run. — crates/duckdb-neo/src/vector/reader.rs:337
What to do
- Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `fmt` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 170 with a piece of the document (and at line 176, line 193, line 194, line 215) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `fmt` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/duckdb/src/error.rs:170
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
- `mem::forget(payload)` (line 144) takes `payload` out of Rust's ownership: its `Drop` never runs, so whatever it holds — a descriptor, a socket, a buffer, a lock — is never given back, and nothing can give it back later because the value is gone. Let it drop (or call its explicit close) where its work ends; if the handle must outlive this function, turn it into a raw handle with `into_raw`/`into_raw_fd` and reclaim it with the matching `from_raw` when the owner is done. — crates/duckdb/src/callback.rs:144
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X5 · Nullable reference types
- `env::var("OUT_DIR")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/build.rs:35
- `std::fs::copy(bindings_path,out_path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `copy_pregenerated_bindings` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/build.rs:138
- `crate::bundled_sources::unpack(Path::new("duckdb.tar.gz"),Path::new(out_dir))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/build_bundled_cc.rs:50
- `std::fs::File::open(source_root.join("duckdb/manifest.json"))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/build_bundled_cc.rs:55
- `serde_json::from_reader(manifest_file)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/build_bundled_cc.rs:56
- `source.parent()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/build_bundled_cc.rs:89
- `source_dir.join("src/include").canonicalize()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/build_bundled_cmake.rs:39
- `env::var("CARGO_CFG_TARGET_ARCH")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `configure_macos_deployment_target` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/build_bundled_cmake.rs:287
- `env::var("CARGO_CFG_TARGET_OS")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `link_system_libs` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/build_bundled_cmake.rs:586
- `syn::parse_str(&output)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `generate_functions_v2` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/buildtime_bindgen.rs:26
- `ast.items.into_iter().find_map(|i|{if let syn::Item::Struct(s)=i{if s.ident=="duckdb_ext_api_v2"{Some(s)}else{None}}else{None}})` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `generate_functions_v2` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/buildtime_bindgen.rs:37
- `field.ident` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `generate_functions_v2` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/buildtime_bindgen.rs:43
- `i.name.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate_functions_v2` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/buildtime_bindgen.rs:54
- `syn::parse2(tokens)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `generate_functions_v2` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — crates/libduckdb-sys/buildtime_bindgen.rs:72, crates/libduckdb-sys/buildtime_bindgen.rs:105
- `std::ffi::CString::new(version)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `duckdb_rs_extension_api_v2_init` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — crates/libduckdb-sys/buildtime_bindgen.rs:91, crates/libduckdb-sys/src/bindgen_bundled_version_loadable_v2.rs:19473
- `syn::parse_str(&output)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `generate_functions_v1` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/buildtime_bindgen.rs:114
- `ast.items.into_iter().find_map(|i|{if let syn::Item::Struct(s)=i{if s.ident=="duckdb_ext_api_v1"{Some(s)}else{None}}else{None}})` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `generate_functions_v1` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/buildtime_bindgen.rs:125
- `field.ident` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `generate_functions_v1` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/buildtime_bindgen.rs:131
- `i.name.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate_functions_v1` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/buildtime_bindgen.rs:142
- `syn::parse2(tokens)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `generate_functions_v1` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — crates/libduckdb-sys/buildtime_bindgen.rs:159, crates/libduckdb-sys/buildtime_bindgen.rs:190
- `std::ffi::CString::new(version)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `duckdb_rs_extension_api_init` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — crates/libduckdb-sys/buildtime_bindgen.rs:178, crates/libduckdb-sys/src/bindgen_bundled_version_loadable.rs:12026
- `(*access).get_api` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `duckdb_rs_extension_api_init` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — crates/libduckdb-sys/buildtime_bindgen.rs:179, crates/libduckdb-sys/src/bindgen_bundled_version_loadable.rs:12027
- `builder.generate().unwrap_or_else(|e|panic!("could not run bindgen on header {header}: {e}")).write(Box::new(&mut output))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `write_to_out_dir` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/buildtime_bindgen.rs:248
- `String::from_utf8(output)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `write_to_out_dir` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/buildtime_bindgen.rs:250
- `pkg_version.split('.').nth(1)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `duckdb_version_from_pkg_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/src/build_version.rs:5
- `pkg_version.split('.').nth(1).expect("CARGO_PKG_VERSION should use the documented 1.MAJOR_MINOR_PATCH.x format").parse::<u32>()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `duckdb_version_from_pkg_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/src/build_version.rs:7
- `CString::new(sql)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `query_result` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/src/lib.rs:167
- `core::ptr::NonNull::new(ptr as*mut c_char)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `from_raw_parts` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/libduckdb-sys/src/v1/string.rs:59
- `slot.get()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `cached` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/duckdb-neo/src/data_chunk.rs:141
- `slot.get_mut()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `cached_iter_mut` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/duckdb-neo/src/data_chunk.rs:154
- `check_api_call_no_err!(ffi::duckdb_v2_data_chunk_destroy,&mut self.chunk.handle)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `drop` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/duckdb-neo/src/data_chunk.rs:602
- `vector.children()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `child_reader` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/duckdb-neo/src/lib.rs:162
- `check_api_call!(ffi::duckdb_v2_logical_type_is_equal,self.handle,other.handle,RET)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `eq` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/duckdb-neo/src/logical_type.rs:219
- `check_api_call!(ffi::duckdb_v2_logical_type_copy,self.handle,RET)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `clone` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/duckdb-neo/src/logical_type.rs:226
- `check_api_call!(ffi::duckdb_v2_qname_equals,self.handle,other.handle,RET)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `eq` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/duckdb-neo/src/qualified_name.rs:138
What to do
- Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 87.9 | Strong | Solid. |
| Architecture | 94.3 | Exemplary | Strongest area. |
| Maturity | 42.9 | Weak — gated by M2, M4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 71.0 | Strong | Solid. |
| Security | 50.2 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 90.0 | Exemplary | Solid. |
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 web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no interface, protocol or abstract type declares an operation an implementer must write
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .rs exposed no member bodies
- D10 Test Quality — ~8641 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D15 Churn × Complexity Hotspots — complexity unreadable for .rs — churn × complexity hotspots could not be measured
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D2 Cognitive Complexity — cognitive complexity not measured — .rs exposed no member bodies
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (5190 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (duckdb-neo), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- 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.
- D3 God Classes — Most of this repository's production source (.rs) was not read by god-class detection, so type and module size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's type and module size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Rust suite
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 3 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 38 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 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 154 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, 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
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 57 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
Serious — 175 finding(s)
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/build.rs:35
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/build.rs:138
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/build_bundled_cc.rs:50
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/build_bundled_cc.rs:55
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/build_bundled_cc.rs:56
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/build_bundled_cc.rs:89
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/build_bundled_cmake.rs:39
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/build_bundled_cmake.rs:287
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/build_bundled_cmake.rs:586
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:26
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:37
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:43
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:54
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:72
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:91
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:105
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:114
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:125
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:131
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:142
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:159
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:178
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:179
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:190
- Symbol treated as nullable, then dereferenced unguarded crates/libduckdb-sys/buildtime_bindgen.rs:248
- TodoComment crates/libduckdb-sys/src/lib.rs:70
- TodoComment crates/duckdb-neo/src/expression.rs:245
- TodoComment crates/duckdb-neo/src/types/bignum.rs:155
- TodoComment REDACTED:59
- TodoComment crates/duckdb/src/lib.rs:900
- TodoComment crates/duckdb/src/lib.rs:944
- TodoComment crates/duckdb/src/lib.rs:1168
- TodoComment crates/duckdb/src/params.rs:197
- TodoComment crates/duckdb/src/row.rs:545
- TodoComment crates/duckdb/src/statement.rs:611
- TodoComment crates/duckdb/src/statement.rs:758
- TodoComment crates/duckdb/src/statement.rs:946
- TodoComment crates/duckdb/src/core/logical_type.rs:210
- TodoComment crates/duckdb/src/core/vector/array.rs:78
- TodoComment crates/duckdb/src/core/vector/list.rs:103
- TodoComment crates/duckdb/src/arrow_interop/to_duckdb.rs:498
- TodoComment crates/duckdb/src/arrow_interop/tests/mod.rs:231
- TodoComment crates/duckdb/src/arrow_interop/tests/mod.rs:753
- TodoComment crates/duckdb/src/appender/mod.rs:223
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (8 corresponding lines) crates/duckdb-neo/src/connection.rs:285
- Edited copy of a member (8 corresponding lines) crates/duckdb-neo/src/bind_arguments.rs:99
- Edited copy of a member (8 corresponding lines) crates/duckdb/src/vscalar/function.rs:159
- Edited copy of a member (8 corresponding lines) crates/duckdb-neo/src/vector/array_writer.rs:64
- Edited copy of a member (8 corresponding lines) crates/duckdb/src/core/logical_type.rs:190
- Edited copy of a member (8 corresponding lines) crates/duckdb-neo/src/aggregate/mod.rs:391
- Edited copy of a member (8 corresponding lines) crates/duckdb-neo/src/connection_options.rs:188
- Edited copy of a member (10 corresponding lines) crates/duckdb-neo/src/types/structs.rs:117
- Edited copy of a member (10 corresponding lines) crates/duckdb-neo/src/types/array.rs:97
- Edited copy of a member (10 corresponding lines) crates/duckdb/src/pragma.rs:162
- Edited copy of a member (10 corresponding lines) crates/duckdb-neo/src/vector/nested_reader.rs:29
- Edited copy of a member (10 corresponding lines) crates/duckdb-neo/src/vector/reader.rs:188
- Duplicated block (8 lines × 2) crates/duckdb/src/vscalar/mod.rs:199
- Duplicated block (8 lines × 2) crates/duckdb/src/vtab/mod.rs:159
- Duplicated block (8 lines × 2) crates/duckdb-neo/src/statement.rs:327
- Duplicated block (8 lines × 2) crates/duckdb-neo/src/vector/list_writer.rs:138
- Duplicated block (8 lines × 2) crates/duckdb-neo/src/vector/nested_reader.rs:31
- Unfinished branch — a todo!() / unimplemented!() arm in a real function crates/duckdb-neo/src/query_result.rs:225
- Unfinished branch — a todo!() / unimplemented!() arm in a real function crates/duckdb/src/arrow_interop/to_duckdb.rs:250
- Unfinished branch — a todo!() / unimplemented!() arm in a real function crates/duckdb/src/row.rs:543
- Unfinished branch — a todo!() / unimplemented!() arm in a real function crates/duckdb/src/types/mod.rs:252
- Unfinished branch — a todo!() / unimplemented!() arm in a real function crates/duckdb/src/types/value.rs:280
- Edited copy of a member (15 corresponding lines) crates/duckdb/src/core/logical_type.rs:291
- Edited copy of a member (15 corresponding lines) crates/duckdb-neo/src/vector/init.rs:126
- Edited copy of a member (15 corresponding lines) crates/duckdb-neo/src/vector/array_writer.rs:32
- Edited copy of a member (16 corresponding lines) crates/duckdb/src/vtab/mod.rs:151
- Edited copy of a member (16 corresponding lines) crates/duckdb-neo/src/copy_function/mod.rs:617
- Edited copy of a member (16 corresponding lines) crates/duckdb/src/error.rs:316
- Edited copy of a member (14 corresponding lines) crates/duckdb/src/vscalar/mod.rs:198
- Edited copy of a member (14 corresponding lines) crates/duckdb-neo/src/statement.rs:202
- Edited copy of a member (14 corresponding lines) crates/duckdb-neo/src/logical_type.rs:81
- Edited copy of a member (12 corresponding lines) crates/duckdb-neo/src/copy_function/mod.rs:595
- Edited copy of a member (12 corresponding lines) crates/duckdb/src/types/bind_container.rs:138
- Edited copy of a member (12 corresponding lines) crates/duckdb-neo/src/types/array.rs:43
- Duplicated block (6 lines × 2) crates/duckdb-neo/src/vector/init.rs:127
- Duplicated block (6 lines × 2) crates/libduckdb-sys/buildtime_bindgen.rs:26
- Duplicated block (6 lines × 2) crates/duckdb-loadable-macros/src/neo/struct_value.rs:8
- Duplicated block (5 lines × 2) crates/duckdb-loadable-macros/src/neo/struct_vector.rs:287
- Duplicated block (5 lines × 2) crates/duckdb-neo/src/aggregate/mod.rs:280
- Duplicated block (5 lines × 2) crates/duckdb-loadable-macros/src/neo/struct_vector.rs:294
- Statement is unreachable — control never gets past the statement before it crates/duckdb-neo/src/builder_helpers.rs:107
- Statement is unreachable — control never gets past the statement before it crates/duckdb-neo/src/extension.rs:58
- Statement is unreachable — control never gets past the statement before it crates/duckdb-neo/src/vector/reader.rs:337
- XxxComment crates/duckdb/src/appender_params.rs:47
- XxxComment crates/duckdb/src/params.rs:177
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copies of one member (3 members, 11+ corresponding lines) crates/duckdb-neo/src/table_function/mod.rs:333
- Edited copies of one member (3 members, 11+ corresponding lines) crates/duckdb-neo/src/types/bignum.rs:139
- Edited copy of a member (13 corresponding lines) crates/duckdb/src/raw_statement.rs:158
- Edited copy of a member (13 corresponding lines) crates/duckdb/src/vtab/mod.rs:117
- Edited copy of a member (11 corresponding lines) crates/duckdb-neo/src/table_function/mod.rs:85
- Edited copy of a member (11 corresponding lines) crates/duckdb-neo/src/copy_function/mod.rs:495
- Edited copy of a member (4 corresponding lines) crates/duckdb-neo/src/connection_options.rs:53
- Edited copy of a member (4 corresponding lines) crates/duckdb-neo/src/connection_options.rs:199
- Duplicated block (7 lines × 2) crates/duckdb-neo/src/vector/reader.rs:265
- Duplicated block (7 lines × 2) crates/duckdb-neo/src/types/array.rs:98
- Low cohesion: Vector (LCOM4 6) crates/duckdb-neo/src/vector/mod.rs:158
- Low cohesion: Instance (LCOM4 4) crates/duckdb-neo/src/instance.rs:211
- FixmeComment crates/duckdb/src/row.rs:75
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (69 shared lines) crates/libduckdb-sys/buildtime_bindgen.rs:24
- Edited copy of a member (18 corresponding lines) crates/duckdb-neo/src/statement.rs:326
- Edited copies of one member (3 members, 23+ corresponding lines) crates/duckdb-loadable-macros/src/neo/struct_value.rs:6
- Edited copy of a member (26 corresponding lines) crates/duckdb-neo/src/copy_function/mod.rs:565
- Edited copy of a member (20 corresponding lines) crates/duckdb-neo/src/vector/list_writer.rs:155
- Edited copy of a member (29 corresponding lines) crates/duckdb-neo/src/value.rs:328
- Edited copy of a member (21 corresponding lines) crates/duckdb-neo/src/vector/list_writer.rs:115
- Edited copy of a member (23 corresponding lines) crates/duckdb-neo/src/copy_function/mod.rs:686
- Edited copies of one member (3 members, 16+ corresponding lines) crates/duckdb-neo/src/builder_helpers.rs:12
- Edited copies of one member (5 members, 11+ corresponding lines) crates/duckdb-neo/src/connection_options.rs:67
- Edited copy of a member (9 corresponding lines) crates/duckdb/src/vscalar/function.rs:30
- Edited copy of a member (7 corresponding lines) crates/duckdb-neo/src/vector/list_writer.rs:233
- Edited copies of one member (3 members, 4+ corresponding lines) crates/duckdb-neo/src/connection_options.rs:61
- Edited copy of a member (5 corresponding lines) crates/duckdb-neo/src/vector/combined.rs:145
- Edited copies of one member (5 members, 4+ corresponding lines) crates/duckdb-neo/src/copy_function/mod.rs:484
- Edited copy of a member (3 corresponding lines) crates/duckdb-neo/src/value.rs:391
- Duplicated block (26 lines × 2) crates/libduckdb-sys/buildtime_bindgen.rs:64
- Duplicated block (22–23 lines × 2) crates/libduckdb-sys/buildtime_bindgen.rs:39
- Duplicated block (14–15 lines × 2) crates/libduckdb-sys/buildtime_bindgen.rs:96
- Duplicated block (11 lines × 3) crates/duckdb-neo/src/vector/writer.rs:575
- Duplicated block (16 lines × 2) crates/duckdb-loadable-macros/src/neo/struct_vector.rs:266
- Duplicated block (6–7 lines × 2) crates/duckdb/src/vtab/mod.rs:152
- Duplicated block (7 lines × 3) crates/duckdb/src/core/vector/array.rs:119
- Off the main sequence: libduckdb-sys
- Empty method body — does nothing with its inputs crates/libduckdb-sys/build_bundled_cmake.rs:551
- Hollow method — returns a constant without doing the work crates/libduckdb-sys/src/v1/error.rs:90
- Recursive walk over a caller-supplied document has no depth cap crates/duckdb/src/error.rs:170
- Owned value's release suppressed and never restored crates/duckdb/src/callback.rs:144
Minor — 19 finding(s)
- README/code drift crates/duckdb-loadable-macros/README.md:109
- README/code drift crates/duckdb-loadable-macros/README.md:415
- README/code drift crates/libduckdb-sys/README.md:109
- README/code drift crates/libduckdb-sys/README.md:415
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion crates/duckdb-neo/Cargo.toml:1
- Orphaned files with no living knowledge
- Orphaned file crates/duckdb/src/types/url.rs:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- Dependabot does not watch github-actions/gitsubmodule REDACTED:2
- No release approval gate REDACTED:15
- No changelog
Minor — 6 finding(s)
- Outdated: arrow
- Outdated: cc
- Outdated: flate2
- Outdated: serde_json
- Outdated: ureq
- Outdated: uuid
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-3abdd6a5e62741c081c22001e365aabe/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-3abdd6a5e62741c081c22001e365aabe/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=83" --report-format json --report-path /tmp/watchdog-gitleaks-3abdd6a5e62741c081c22001e365aabe/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3abdd6a5e62741c081c22001e365aabe/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 . | 57 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 25 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |