Executive summary
resemble-ai/chatterbox falls short of our standard for a preview release because we found no automated security scanning of the code, its secrets or its dependencies. It scores 63 out of 100 and is rated Adequate, and two of its three critical findings are security problems in the build pipeline.
Production Readiness, at 50, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the package under a licence on your banned list, worth about 5 points. Adding automated security scanning would lift Production Readiness itself, worth about 9 points. Raising Production Readiness to 62 would lift the score to about 69.
Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One package carries licence risk. Pinning each tool to an exact version and replacing or clearing the banned-licence packages would close both risks.
The product code is 7,994 lines, about €9,200 to rebuild.
If Production Readiness rose from 50 to 62, the lowest score rated Strong, the score would rise from 63 to about 69.
New since the last survey: 8 findings
- Code Duplication · Edited copy of a member (54 corresponding lines) src/chatterbox/mtl_tts.py
- Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) src/chatterbox/mtl_tts.py
- Code Duplication · Edited copy of a member (36 corresponding lines) src/chatterbox/mtl_tts.py
- Code Duplication · Edited copies of one member (3 members, 36+ corresponding lines) src/chatterbox/mtl_tts.py
- Code Duplication · Edited copy of a member (17 corresponding lines) gradio_tts_app.py
- Code Duplication · Edited copy of a member (11 corresponding lines) src/chatterbox/tts.py
- Code Duplication · Edited copy of a member (6 corresponding lines) src/chatterbox/models/tokenizers/tokenizer.py
- Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) src/chatterbox/mtl_tts.py
Rebuild cost: about €9,200 · Estimate
| Cost to rebuild | €3,000 to €15,000, for 51 to 161 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 63. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 7,994 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 src.chatterbox | 3 src.chatterbox.models | 4 src.chatterbox.models.s3gen | 5 src.chatterbox.models.s3gen.f0_predictor | 6 src.chatterbox.models.s3gen.flow | 7 src.chatterbox.models.s3gen.hifigan | 8 src.chatterbox.models.s3gen.matcha | 9 src.chatterbox.models.s3gen.matcha.decoder | 10 src.chatterbox.models.s3gen.matcha.flow_matching | 11 src.chatterbox.models.s3gen.matcha.text_encoder | 12 src.chatterbox.models.s3gen.matcha.transformer | 13 src.chatterbox.models.s3gen.s3gen | 14 src.chatterbox.models.s3gen.transformer.activation | 15 src.chatterbox.models.s3gen.transformer.attention | 16 src.chatterbox.models.s3gen.transformer.convolution | 17 src.chatterbox.models.s3gen.transformer.embedding | 18 src.chatterbox.models.s3gen.transformer.encoder_layer | 19 src.chatterbox.models.s3gen.transformer.positionwise_feed_forward | 20 src.chatterbox.models.s3gen.transformer.subsampling | 21 src.chatterbox.models.s3gen.transformer.upsample_encoder | 22 src.chatterbox.models.s3gen.utils | 23 src.chatterbox.models.s3gen.xvector | 24 src.chatterbox.models.s3tokenizer.s3tokenizer | 25 src.chatterbox.models.t3 | 26 src.chatterbox.models.t3.inference.t3_hf_backend | 27 src.chatterbox.models.t3.modules.learned_pos_emb | 28 src.chatterbox.models.t3.modules.t3_config | 29 src.chatterbox.models.tokenizers.tokenizer | 30 src.chatterbox.models.voice_encoder.config | 31 src.chatterbox.models.voice_encoder.voice_encoder | 32 src.chatterbox.models.s3gen.decoder | 33 src.chatterbox.models.s3gen.flow_matching | 34 src.chatterbox.models.t3.modules.cond_enc | 35 src.chatterbox.models.voice_encoder | 36 src.chatterbox.vc | 37 src.chatterbox.models.t3.t3 | 38 src.chatterbox.mtl_tts | 39 src.chatterbox.tts | 40 src.chatterbox.tts_turbo |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 src.chatterbox | ||||||||||||||||||||||||||||||||||||||||
| 3 src.chatterbox.models | ||||||||||||||||||||||||||||||||||||||||
| 4 src.chatterbox.models.s3gen | ||||||||||||||||||||||||||||||||||||||||
| 5 src.chatterbox.models.s3gen.f0_predictor | ||||||||||||||||||||||||||||||||||||||||
| 6 src.chatterbox.models.s3gen.flow | ||||||||||||||||||||||||||||||||||||||||
| 7 src.chatterbox.models.s3gen.hifigan | ||||||||||||||||||||||||||||||||||||||||
| 8 src.chatterbox.models.s3gen.matcha | ||||||||||||||||||||||||||||||||||||||||
| 9 src.chatterbox.models.s3gen.matcha.decoder | ||||||||||||||||||||||||||||||||||||||||
| 10 src.chatterbox.models.s3gen.matcha.flow_matching | ||||||||||||||||||||||||||||||||||||||||
| 11 src.chatterbox.models.s3gen.matcha.text_encoder | ||||||||||||||||||||||||||||||||||||||||
| 12 src.chatterbox.models.s3gen.matcha.transformer | ||||||||||||||||||||||||||||||||||||||||
| 13 src.chatterbox.models.s3gen.s3gen | ||||||||||||||||||||||||||||||||||||||||
| 14 src.chatterbox.models.s3gen.transformer.activation | ||||||||||||||||||||||||||||||||||||||||
| 15 src.chatterbox.models.s3gen.transformer.attention | ||||||||||||||||||||||||||||||||||||||||
| 16 src.chatterbox.models.s3gen.transformer.convolution | ||||||||||||||||||||||||||||||||||||||||
| 17 src.chatterbox.models.s3gen.transformer.embedding | ||||||||||||||||||||||||||||||||||||||||
| 18 src.chatterbox.models.s3gen.transformer.encoder_layer | ||||||||||||||||||||||||||||||||||||||||
| 19 src.chatterbox.models.s3gen.transformer.positionwise_feed_forward | ||||||||||||||||||||||||||||||||||||||||
| 20 src.chatterbox.models.s3gen.transformer.subsampling | ||||||||||||||||||||||||||||||||||||||||
| 21 src.chatterbox.models.s3gen.transformer.upsample_encoder | ||||||||||||||||||||||||||||||||||||||||
| 22 src.chatterbox.models.s3gen.utils | ||||||||||||||||||||||||||||||||||||||||
| 23 src.chatterbox.models.s3gen.xvector | ||||||||||||||||||||||||||||||||||||||||
| 24 src.chatterbox.models.s3tokenizer.s3tokenizer | ||||||||||||||||||||||||||||||||||||||||
| 25 src.chatterbox.models.t3 | ||||||||||||||||||||||||||||||||||||||||
| 26 src.chatterbox.models.t3.inference.t3_hf_backend | ||||||||||||||||||||||||||||||||||||||||
| 27 src.chatterbox.models.t3.modules.learned_pos_emb | ||||||||||||||||||||||||||||||||||||||||
| 28 src.chatterbox.models.t3.modules.t3_config | ||||||||||||||||||||||||||||||||||||||||
| 29 src.chatterbox.models.tokenizers.tokenizer | ||||||||||||||||||||||||||||||||||||||||
| 30 src.chatterbox.models.voice_encoder.config | ||||||||||||||||||||||||||||||||||||||||
| 31 src.chatterbox.models.voice_encoder.voice_encoder | ||||||||||||||||||||||||||||||||||||||||
| 32 src.chatterbox.models.s3gen.decoder | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 src.chatterbox.models.s3gen.flow_matching | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 src.chatterbox.models.t3.modules.cond_enc | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 src.chatterbox.models.voice_encoder | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 src.chatterbox.vc | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 src.chatterbox.models.t3.t3 | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 src.chatterbox.mtl_tts | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 src.chatterbox.tts | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 40 src.chatterbox.tts_turbo | 1 | 1 | 1 | 1 | 1 |
32→9 src.chatterbox.models.s3gen.decoder uses src.chatterbox.models.s3gen.matcha.decoder✕
- Connections
- 2 pairs of types, where a type in src.chatterbox.models.s3gen.decoder uses a type in src.chatterbox.models.s3gen.matcha.decoder.
- The types involved
src.chatterbox.models.s3gen.decoder.CausalBlock1D→src.chatterbox.models.s3gen.matcha.decoder.Block1Dsrc.chatterbox.models.s3gen.decoder.CausalResnetBlock1D→src.chatterbox.models.s3gen.matcha.decoder.ResnetBlock1D
- Direction
- src.chatterbox.models.s3gen.decoder uses src.chatterbox.models.s3gen.matcha.decoder, so a change to src.chatterbox.models.s3gen.matcha.decoder can break src.chatterbox.models.s3gen.decoder, while a change to src.chatterbox.models.s3gen.decoder can't break src.chatterbox.models.s3gen.matcha.decoder.
- Position
- Below the diagonal: src.chatterbox.models.s3gen.decoder uses a module listed above it, which is the healthy direction.
33→10 src.chatterbox.models.s3gen.flow_matching uses src.chatterbox.models.s3gen.matcha.flow_matching✕
- Connections
- 1 pair of types, where a type in src.chatterbox.models.s3gen.flow_matching uses a type in src.chatterbox.models.s3gen.matcha.flow_matching.
- The types involved
src.chatterbox.models.s3gen.flow_matching.ConditionalCFM→src.chatterbox.models.s3gen.matcha.flow_matching.BASECFM
- Direction
- src.chatterbox.models.s3gen.flow_matching uses src.chatterbox.models.s3gen.matcha.flow_matching, so a change to src.chatterbox.models.s3gen.matcha.flow_matching can break src.chatterbox.models.s3gen.flow_matching, while a change to src.chatterbox.models.s3gen.flow_matching can't break src.chatterbox.models.s3gen.matcha.flow_matching.
- Position
- Below the diagonal: src.chatterbox.models.s3gen.flow_matching uses a module listed above it, which is the healthy direction.
34→28 src.chatterbox.models.t3.modules.cond_enc uses src.chatterbox.models.t3.modules.t3_config✕
- Connections
- 1 pair of types, where a type in src.chatterbox.models.t3.modules.cond_enc uses a type in src.chatterbox.models.t3.modules.t3_config.
- The types involved
src.chatterbox.models.t3.modules.cond_enc.T3CondEnc→src.chatterbox.models.t3.modules.t3_config.T3Config
- Direction
- src.chatterbox.models.t3.modules.cond_enc uses src.chatterbox.models.t3.modules.t3_config, so a change to src.chatterbox.models.t3.modules.t3_config can break src.chatterbox.models.t3.modules.cond_enc, while a change to src.chatterbox.models.t3.modules.cond_enc can't break src.chatterbox.models.t3.modules.t3_config.
- Position
- Below the diagonal: src.chatterbox.models.t3.modules.cond_enc uses a module listed above it, which is the healthy direction.
35→30 src.chatterbox.models.voice_encoder uses src.chatterbox.models.voice_encoder.config✕
- Connections
- 1 pair of types, where a type in src.chatterbox.models.voice_encoder uses a type in src.chatterbox.models.voice_encoder.config.
- The types involved
src.chatterbox.models.voice_encoder.voice_encoder→src.chatterbox.models.voice_encoder.config.VoiceEncConfig
- Direction
- src.chatterbox.models.voice_encoder uses src.chatterbox.models.voice_encoder.config, so a change to src.chatterbox.models.voice_encoder.config can break src.chatterbox.models.voice_encoder, while a change to src.chatterbox.models.voice_encoder can't break src.chatterbox.models.voice_encoder.config.
- Position
- Below the diagonal: src.chatterbox.models.voice_encoder uses a module listed above it, which is the healthy direction.
36→13 src.chatterbox.vc uses src.chatterbox.models.s3gen.s3gen✕
- Connections
- 1 pair of types, where a type in src.chatterbox.vc uses a type in src.chatterbox.models.s3gen.s3gen.
- The types involved
src.chatterbox.vc.ChatterboxVC→src.chatterbox.models.s3gen.s3gen.S3Token2Wav
- Direction
- src.chatterbox.vc uses src.chatterbox.models.s3gen.s3gen, so a change to src.chatterbox.models.s3gen.s3gen can break src.chatterbox.vc, while a change to src.chatterbox.vc can't break src.chatterbox.models.s3gen.s3gen.
- Position
- Below the diagonal: src.chatterbox.vc uses a module listed above it, which is the healthy direction.
37→34 src.chatterbox.models.t3.t3 uses src.chatterbox.models.t3.modules.cond_enc✕
- Connections
- 1 pair of types, where a type in src.chatterbox.models.t3.t3 uses a type in src.chatterbox.models.t3.modules.cond_enc.
- The types involved
src.chatterbox.models.t3.t3.T3→src.chatterbox.models.t3.modules.cond_enc.T3Cond
- Direction
- src.chatterbox.models.t3.t3 uses src.chatterbox.models.t3.modules.cond_enc, so a change to src.chatterbox.models.t3.modules.cond_enc can break src.chatterbox.models.t3.t3, while a change to src.chatterbox.models.t3.t3 can't break src.chatterbox.models.t3.modules.cond_enc.
- Position
- Below the diagonal: src.chatterbox.models.t3.t3 uses a module listed above it, which is the healthy direction.
38→13 src.chatterbox.mtl_tts uses src.chatterbox.models.s3gen.s3gen✕
- Connections
- 1 pair of types, where a type in src.chatterbox.mtl_tts uses a type in src.chatterbox.models.s3gen.s3gen.
- The types involved
src.chatterbox.mtl_tts.ChatterboxMultilingualTTS→src.chatterbox.models.s3gen.s3gen.S3Token2Wav
- Direction
- src.chatterbox.mtl_tts uses src.chatterbox.models.s3gen.s3gen, so a change to src.chatterbox.models.s3gen.s3gen can break src.chatterbox.mtl_tts, while a change to src.chatterbox.mtl_tts can't break src.chatterbox.models.s3gen.s3gen.
- Position
- Below the diagonal: src.chatterbox.mtl_tts uses a module listed above it, which is the healthy direction.
38→29 src.chatterbox.mtl_tts uses src.chatterbox.models.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in src.chatterbox.mtl_tts uses a type in src.chatterbox.models.tokenizers.tokenizer.
- The types involved
src.chatterbox.mtl_tts.ChatterboxMultilingualTTS→src.chatterbox.models.tokenizers.tokenizer.MTLTokenizer
- Direction
- src.chatterbox.mtl_tts uses src.chatterbox.models.tokenizers.tokenizer, so a change to src.chatterbox.models.tokenizers.tokenizer can break src.chatterbox.mtl_tts, while a change to src.chatterbox.mtl_tts can't break src.chatterbox.models.tokenizers.tokenizer.
- Position
- Below the diagonal: src.chatterbox.mtl_tts uses a module listed above it, which is the healthy direction.
38→31 src.chatterbox.mtl_tts uses src.chatterbox.models.voice_encoder.voice_encoder✕
- Connections
- 1 pair of types, where a type in src.chatterbox.mtl_tts uses a type in src.chatterbox.models.voice_encoder.voice_encoder.
- The types involved
src.chatterbox.mtl_tts.ChatterboxMultilingualTTS→src.chatterbox.models.voice_encoder.voice_encoder.VoiceEncoder
- Direction
- src.chatterbox.mtl_tts uses src.chatterbox.models.voice_encoder.voice_encoder, so a change to src.chatterbox.models.voice_encoder.voice_encoder can break src.chatterbox.mtl_tts, while a change to src.chatterbox.mtl_tts can't break src.chatterbox.models.voice_encoder.voice_encoder.
- Position
- Below the diagonal: src.chatterbox.mtl_tts uses a module listed above it, which is the healthy direction.
38→34 src.chatterbox.mtl_tts uses src.chatterbox.models.t3.modules.cond_enc✕
- Connections
- 1 pair of types, where a type in src.chatterbox.mtl_tts uses a type in src.chatterbox.models.t3.modules.cond_enc.
- The types involved
src.chatterbox.mtl_tts.Conditionals→src.chatterbox.models.t3.modules.cond_enc.T3Cond
- Direction
- src.chatterbox.mtl_tts uses src.chatterbox.models.t3.modules.cond_enc, so a change to src.chatterbox.models.t3.modules.cond_enc can break src.chatterbox.mtl_tts, while a change to src.chatterbox.mtl_tts can't break src.chatterbox.models.t3.modules.cond_enc.
- Position
- Below the diagonal: src.chatterbox.mtl_tts uses a module listed above it, which is the healthy direction.
38→37 src.chatterbox.mtl_tts uses src.chatterbox.models.t3.t3✕
- Connections
- 1 pair of types, where a type in src.chatterbox.mtl_tts uses a type in src.chatterbox.models.t3.t3.
- The types involved
src.chatterbox.mtl_tts.ChatterboxMultilingualTTS→src.chatterbox.models.t3.t3.T3
- Direction
- src.chatterbox.mtl_tts uses src.chatterbox.models.t3.t3, so a change to src.chatterbox.models.t3.t3 can break src.chatterbox.mtl_tts, while a change to src.chatterbox.mtl_tts can't break src.chatterbox.models.t3.t3.
- Position
- Below the diagonal: src.chatterbox.mtl_tts uses a module listed above it, which is the healthy direction.
39→13 src.chatterbox.tts uses src.chatterbox.models.s3gen.s3gen✕
- Connections
- 1 pair of types, where a type in src.chatterbox.tts uses a type in src.chatterbox.models.s3gen.s3gen.
- The types involved
src.chatterbox.tts.ChatterboxTTS→src.chatterbox.models.s3gen.s3gen.S3Token2Wav
- Direction
- src.chatterbox.tts uses src.chatterbox.models.s3gen.s3gen, so a change to src.chatterbox.models.s3gen.s3gen can break src.chatterbox.tts, while a change to src.chatterbox.tts can't break src.chatterbox.models.s3gen.s3gen.
- Position
- Below the diagonal: src.chatterbox.tts uses a module listed above it, which is the healthy direction.
39→29 src.chatterbox.tts uses src.chatterbox.models.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in src.chatterbox.tts uses a type in src.chatterbox.models.tokenizers.tokenizer.
- The types involved
src.chatterbox.tts.ChatterboxTTS→src.chatterbox.models.tokenizers.tokenizer.EnTokenizer
- Direction
- src.chatterbox.tts uses src.chatterbox.models.tokenizers.tokenizer, so a change to src.chatterbox.models.tokenizers.tokenizer can break src.chatterbox.tts, while a change to src.chatterbox.tts can't break src.chatterbox.models.tokenizers.tokenizer.
- Position
- Below the diagonal: src.chatterbox.tts uses a module listed above it, which is the healthy direction.
39→31 src.chatterbox.tts uses src.chatterbox.models.voice_encoder.voice_encoder✕
- Connections
- 1 pair of types, where a type in src.chatterbox.tts uses a type in src.chatterbox.models.voice_encoder.voice_encoder.
- The types involved
src.chatterbox.tts.ChatterboxTTS→src.chatterbox.models.voice_encoder.voice_encoder.VoiceEncoder
- Direction
- src.chatterbox.tts uses src.chatterbox.models.voice_encoder.voice_encoder, so a change to src.chatterbox.models.voice_encoder.voice_encoder can break src.chatterbox.tts, while a change to src.chatterbox.tts can't break src.chatterbox.models.voice_encoder.voice_encoder.
- Position
- Below the diagonal: src.chatterbox.tts uses a module listed above it, which is the healthy direction.
39→34 src.chatterbox.tts uses src.chatterbox.models.t3.modules.cond_enc✕
- Connections
- 1 pair of types, where a type in src.chatterbox.tts uses a type in src.chatterbox.models.t3.modules.cond_enc.
- The types involved
src.chatterbox.tts.Conditionals→src.chatterbox.models.t3.modules.cond_enc.T3Cond
- Direction
- src.chatterbox.tts uses src.chatterbox.models.t3.modules.cond_enc, so a change to src.chatterbox.models.t3.modules.cond_enc can break src.chatterbox.tts, while a change to src.chatterbox.tts can't break src.chatterbox.models.t3.modules.cond_enc.
- Position
- Below the diagonal: src.chatterbox.tts uses a module listed above it, which is the healthy direction.
39→37 src.chatterbox.tts uses src.chatterbox.models.t3.t3✕
- Connections
- 1 pair of types, where a type in src.chatterbox.tts uses a type in src.chatterbox.models.t3.t3.
- The types involved
src.chatterbox.tts.ChatterboxTTS→src.chatterbox.models.t3.t3.T3
- Direction
- src.chatterbox.tts uses src.chatterbox.models.t3.t3, so a change to src.chatterbox.models.t3.t3 can break src.chatterbox.tts, while a change to src.chatterbox.tts can't break src.chatterbox.models.t3.t3.
- Position
- Below the diagonal: src.chatterbox.tts uses a module listed above it, which is the healthy direction.
40→13 src.chatterbox.tts_turbo uses src.chatterbox.models.s3gen.s3gen✕
- Connections
- 1 pair of types, where a type in src.chatterbox.tts_turbo uses a type in src.chatterbox.models.s3gen.s3gen.
- The types involved
src.chatterbox.tts_turbo.ChatterboxTurboTTS→src.chatterbox.models.s3gen.s3gen.S3Token2Wav
- Direction
- src.chatterbox.tts_turbo uses src.chatterbox.models.s3gen.s3gen, so a change to src.chatterbox.models.s3gen.s3gen can break src.chatterbox.tts_turbo, while a change to src.chatterbox.tts_turbo can't break src.chatterbox.models.s3gen.s3gen.
- Position
- Below the diagonal: src.chatterbox.tts_turbo uses a module listed above it, which is the healthy direction.
40→29 src.chatterbox.tts_turbo uses src.chatterbox.models.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in src.chatterbox.tts_turbo uses a type in src.chatterbox.models.tokenizers.tokenizer.
- The types involved
src.chatterbox.tts_turbo.ChatterboxTurboTTS→src.chatterbox.models.tokenizers.tokenizer.EnTokenizer
- Direction
- src.chatterbox.tts_turbo uses src.chatterbox.models.tokenizers.tokenizer, so a change to src.chatterbox.models.tokenizers.tokenizer can break src.chatterbox.tts_turbo, while a change to src.chatterbox.tts_turbo can't break src.chatterbox.models.tokenizers.tokenizer.
- Position
- Below the diagonal: src.chatterbox.tts_turbo uses a module listed above it, which is the healthy direction.
40→31 src.chatterbox.tts_turbo uses src.chatterbox.models.voice_encoder.voice_encoder✕
- Connections
- 1 pair of types, where a type in src.chatterbox.tts_turbo uses a type in src.chatterbox.models.voice_encoder.voice_encoder.
- The types involved
src.chatterbox.tts_turbo.ChatterboxTurboTTS→src.chatterbox.models.voice_encoder.voice_encoder.VoiceEncoder
- Direction
- src.chatterbox.tts_turbo uses src.chatterbox.models.voice_encoder.voice_encoder, so a change to src.chatterbox.models.voice_encoder.voice_encoder can break src.chatterbox.tts_turbo, while a change to src.chatterbox.tts_turbo can't break src.chatterbox.models.voice_encoder.voice_encoder.
- Position
- Below the diagonal: src.chatterbox.tts_turbo uses a module listed above it, which is the healthy direction.
40→34 src.chatterbox.tts_turbo uses src.chatterbox.models.t3.modules.cond_enc✕
- Connections
- 1 pair of types, where a type in src.chatterbox.tts_turbo uses a type in src.chatterbox.models.t3.modules.cond_enc.
- The types involved
src.chatterbox.tts_turbo.Conditionals→src.chatterbox.models.t3.modules.cond_enc.T3Cond
- Direction
- src.chatterbox.tts_turbo uses src.chatterbox.models.t3.modules.cond_enc, so a change to src.chatterbox.models.t3.modules.cond_enc can break src.chatterbox.tts_turbo, while a change to src.chatterbox.tts_turbo can't break src.chatterbox.models.t3.modules.cond_enc.
- Position
- Below the diagonal: src.chatterbox.tts_turbo uses a module listed above it, which is the healthy direction.
40→37 src.chatterbox.tts_turbo uses src.chatterbox.models.t3.t3✕
- Connections
- 1 pair of types, where a type in src.chatterbox.tts_turbo uses a type in src.chatterbox.models.t3.t3.
- The types involved
src.chatterbox.tts_turbo.ChatterboxTurboTTS→src.chatterbox.models.t3.t3.T3
- Direction
- src.chatterbox.tts_turbo uses src.chatterbox.models.t3.t3, so a change to src.chatterbox.models.t3.t3 can break src.chatterbox.tts_turbo, while a change to src.chatterbox.tts_turbo can't break src.chatterbox.models.t3.t3.
- Position
- Below the diagonal: src.chatterbox.tts_turbo uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 4 | High / Critical |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing; Resolve the 1 Banned license finding(s) in License Compliance; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Banned license finding(s) in License Compliance. | +4.7 pts | Low | License Compliance |
| Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing. | +9.4 pts | Medium | Security & performance tooling |
| 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. | +4.0 pts | Medium | Architecture documentation |
| Interpolated log message defeats structured logging | +3.6 pts | Medium | Structured logging |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.4 pts | Medium | Release Hygiene |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.3 pts | Low | Static Analysis (SAST) |
| Resolve the 7 TodoComment finding(s) in Explicit Debt — start with mtl_tts.py (2), tts.py (2), t3.py (2). | +0.2 pts | Low | Explicit Debt |
| Enable measurement for Architecture & structure. | unlocks measurement | Low | Architecture & structure |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| src/chatterbox/mtl_tts.py | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/chatterbox/tts.py | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/chatterbox/models/t3/t3.py | 7.3 | Near-clean | Explicit Debt: TodoComment |
| gradio_tts_app.py | 7.8 | Near-clean | Code Duplication: Edited copy of a member (17 corresponding lines) |
| src/chatterbox/models/t3/modules/cond_enc.py | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/chatterbox/models/tokenizers/tokenizer.py | 8.5 | Near-clean | Code Duplication: Edited copy of a member (6 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 31 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 — 31 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, 39 of 51 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
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.py) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- 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 (.py) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Too few commits for a meaningful bus factor (43 commit(s) sampled, fewer than the 50 this dimension needs before a bus factor means anything).
- 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (pyproject.toml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- 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.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (43 commit(s) sampled).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala and Rust source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala or Rust was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M3 Folder & project structure — 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala, PHP and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala, PHP or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, Kotlin source, and Rust source only, and no C# was loaded, no TypeScript was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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").
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
- 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.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
7 duplicated block group(s) detected. 5.2 % of the production lines (414 of 7,994) are in a reported copy. A further 8 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (54 corresponding lines) finding(s) in Code Duplication — start with mtl_tts.py. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copies of one member (3 members, 23+ corresponding lines) finding(s) in Code Duplication — start with mtl_tts.py. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (36 corresponding lines) finding(s) in Code Duplication — start with mtl_tts.py. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 15 classes have LCOM4 above 3.
D12 · Dependency Hygiene
7 outdated, 0 yanked pinned Python distributions. 9 of 14 shipped distributions were graded against pypi.org (0 not published there, 5 declared without an exact pin, which installs the newest release the declaration admits and so cannot be behind one). Only EXACT pins are graded for currency: a floor or a range already installs the newest release it admits, so reporting one would report this repository for being current. Whether a deliberate upper cap has itself gone stale is a different and weaker question, and is not asked. Whether any distribution is UNMAINTAINED is not graded — PyPI publishes no maintenance status, and release age does not stand in for one. Lockfiles are not read (poetry.lock, uv.lock, Pipfile.lock, pdm.lock), so a lock-resolved install is outside this verdict. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 127 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 14 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (113 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 14 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged. A further 1 direct requirement(s) are installed from a URL or a version-control checkout and publish no licence this pass can read; they are outside this verdict.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
7 deducted task-comment markers across 7994 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 7 TodoComment finding(s) in Explicit Debt — start with mtl_tts.py (2), tts.py (2), t3.py (2). — One of this dimension's main actionable groups (7 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
4 finding(s): 0 critical, 2 high, 2 medium, 0 low. 2 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.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 2 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 (2 issue-level, 0 of them charged here).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 14 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `pyproject.toml` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — pyproject.toml:11
What to do
- Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X12 · Unreachable branch
X28 · Index access outside its own emptiness guard
X3 · Exception handling
X4 · Structured logging
- `warning` at line 215 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — src/chatterbox/tts_turbo.py:215
- `warning` at line 291 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — src/chatterbox/tts_turbo.py:291
- `warning` at line 132 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — src/chatterbox/models/tokenizers/tokenizer.py:132
- `warning` at line 188 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — src/chatterbox/models/tokenizers/tokenizer.py:188
- `warning` at line 252 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — src/chatterbox/models/tokenizers/tokenizer.py:252
- `info` at line 367 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — src/chatterbox/models/t3/t3.py:367
- `info` at line 75 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — src/chatterbox/models/s3gen/flow.py:75
- `error` at line 165 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — src/chatterbox/models/s3gen/flow.py:165
- `warning` at line 52 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — src/chatterbox/models/s3gen/utils/mel.py:52
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 72% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Strongest area. |
| Maturity | 67% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 50% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 97% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 81 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: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — 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
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- 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 — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~57 lines of test source are present (.py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .py test runner
- D16 Bus Factor — too few commits for a meaningful bus factor
- 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.
- 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 (1698 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (3076 LoC, 119 module-visible types across 13 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry) — not scanned yet).
- 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.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry) — not scanned yet).
- D5 Coupling — Not applicable — this Python build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (4 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala and Rust, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 3 finding(s)
- REDACTED
- REDACTED
- Banned license: pykakasi
Serious — 26 finding(s)
- TodoComment src/chatterbox/mtl_tts.py:328
- TodoComment src/chatterbox/tts.py:249
- TodoComment src/chatterbox/mtl_tts.py:338
- TodoComment src/chatterbox/tts.py:259
- TodoComment src/chatterbox/models/t3/t3.py:154
- TodoComment src/chatterbox/models/t3/t3.py:274
- TodoComment src/chatterbox/models/t3/modules/cond_enc.py:73
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (54 corresponding lines) src/chatterbox/mtl_tts.py:293
- Edited copies of one member (3 members, 23+ corresponding lines) src/chatterbox/mtl_tts.py:255
- Edited copy of a member (36 corresponding lines) src/chatterbox/mtl_tts.py:189
- Edited copies of one member (3 members, 36+ corresponding lines) src/chatterbox/mtl_tts.py:72
- Edited copy of a member (17 corresponding lines) gradio_tts_app.py:25
- Edited copy of a member (11 corresponding lines) src/chatterbox/tts.py:170
- Edited copy of a member (6 corresponding lines) src/chatterbox/models/tokenizers/tokenizer.py:45
- Edited copies of one member (3 members, 4+ corresponding lines) src/chatterbox/mtl_tts.py:149
- Duplicated block (31–34 lines × 3) src/chatterbox/mtl_tts.py:72
- Duplicated block (23 lines × 2) src/chatterbox/mtl_tts.py:317
- Duplicated block (15 lines × 3) src/chatterbox/mtl_tts.py:264
- Duplicated block (9 lines × 2) src/chatterbox/mtl_tts.py:307
- Duplicated block (5 lines × 2) gradio_tts_app.py:12
- Duplicated block (5 lines × 3) src/chatterbox/mtl_tts.py:134
- Duplicated block (8 lines × 2) src/chatterbox/mtl_tts.py:168
Minor — 15 finding(s)
- Interpolated log message defeats structured logging src/chatterbox/tts_turbo.py:215
- Interpolated log message defeats structured logging src/chatterbox/tts_turbo.py:291
- Interpolated log message defeats structured logging src/chatterbox/models/tokenizers/tokenizer.py:132
- Interpolated log message defeats structured logging src/chatterbox/models/tokenizers/tokenizer.py:188
- Interpolated log message defeats structured logging src/chatterbox/models/tokenizers/tokenizer.py:252
- Interpolated log message defeats structured logging src/chatterbox/models/t3/t3.py:367
- Interpolated log message defeats structured logging src/chatterbox/models/s3gen/flow.py:75
- Interpolated log message defeats structured logging src/chatterbox/models/s3gen/flow.py:165
- Interpolated log message defeats structured logging src/chatterbox/models/s3gen/utils/mel.py:52
- REDACTED
- No ADRs
- No SAST REDACTED:6
- No dependency-update automation pyproject.toml:11
- No changelog
- Duplicated predicate src/chatterbox/mtl_tts.py:234
Minor — 7 finding(s)
- Outdated: diffusers
- Outdated: gradio
- Outdated: librosa
- Outdated: safetensors
- Outdated: torch
- Outdated: torchaudio
- Outdated: transformers
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-53b0296d2e9549b886ffb7173c2a27b2/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-53b0296d2e9549b886ffb7173c2a27b2/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 . | 4 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: 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 | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry) — not scanned yet). | 0 | — |