Executive summary
iptv-org/iptv falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 59 out of 100 and is rated Adequate, and 828 of its 830 critical findings are security problems.
Production Readiness, at 56, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is updating the outdated dependencies, worth about 2 points. Adding automated security scanning would lift Production Readiness itself, also worth about 2.
826 passwords or keys are open to anyone who can read the repository. One automatic update takes new releases before a bad one can be spotted, and one known security hole in a package the code depends on can be used by attackers. Replacing each exposed password or key, setting a waiting period for automatic updates and updating the vulnerable packages would close these risks. The loop of files that import each other needs breaking.
The product code is 3,704 lines, about €7,600 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 9 findings
- Secrets (history) · REDACTED
- Secrets (history) · REDACTED
- Secrets (history) · REDACTED
- Secrets (history) · REDACTED
- Secrets (history) · REDACTED
- Secrets (history) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 56 findings
- Cyclomatic Complexity · create.main (cyclomatic 39) scripts/commands/report/create.ts
- Cyclomatic Complexity · validate.main (cyclomatic 25) scripts/commands/playlist/validate.ts
- Cyclomatic Complexity · validate.main (cyclomatic 24) scripts/commands/discussion/validate.ts
- Cyclomatic Complexity · CountriesTable.create (cyclomatic 18) scripts/tables/countriesTable.ts
- Cyclomatic Complexity · update.addStream (cyclomatic 17) scripts/commands/playlist/update.ts
- Cognitive Complexity · validate.main (cognitive 48) scripts/commands/playlist/validate.ts
- Cognitive Complexity · create.main (cognitive 39) scripts/commands/report/create.ts
- Cognitive Complexity · validate.main (cognitive 30) scripts/commands/issue/validate.ts
- Cognitive Complexity · validate.main (cognitive 25) scripts/commands/discussion/validate.ts
- Cognitive Complexity · StreamTester.test (cognitive 24) scripts/core/streamTester.ts
- Cognitive Complexity · CountriesTable.create (cognitive 23) scripts/tables/countriesTable.ts
- Cognitive Complexity · update.addStream (cognitive 19) scripts/commands/playlist/update.ts
- Cognitive Complexity · utils.getStreamInfo (cognitive 17) scripts/utils.ts
- Cognitive Complexity · Stream.getBroadcastSubdivisions (cognitive 17) scripts/models/stream.ts
- God Classes · FunctionTooLong: create.main scripts/commands/report/create.ts
- God Classes · TooManyMethods: Stream scripts/models/stream.ts
- God Classes · MethodTooLong: CountriesTable.create scripts/tables/countriesTable.ts
- God Classes · FunctionTooLong: validate.main scripts/commands/playlist/validate.ts
- REDACTED Scanning · Leaked secret: hardcoded-credential REDACTED
- Churn × Complexity Hotspots · Hotspot: scripts/commands/issue/validate.ts scripts/commands/issue/validate.ts
- Secrets (history) · REDACTED: REDACTED REDACTED
- Secrets (history) · High secret: WD-SECRET-0005 REDACTED
- Secrets (history) · High secret: WD-SECRET-0005 REDACTED
- Static Analysis (SAST) · Medium: watchdog-regexp-from-parameter-ts scripts/models/stream.ts
- Test Coverage · No test reaches this file scripts/commands/playlist/update.ts
- Test Coverage · No test reaches this file scripts/commands/playlist/test.ts
- Test Coverage · No test reaches this file scripts/commands/report/create.ts
- Test Coverage · No test reaches this file scripts/commands/playlist/edit.ts
- Test Coverage · No test reaches this file scripts/tables/countriesTable.ts
- Test Coverage · No test reaches this file scripts/commands/playlist/format.ts
- Test Coverage · No test reaches this file scripts/commands/playlist/generate.ts
- Test Coverage · No test reaches this file scripts/generators/countriesGenerator.ts
- Test Coverage · No test reaches this file scripts/generators/indexCountryGenerator.ts
- Test Coverage · No test reaches this file scripts/tables/categoriesTable.ts
- Test Coverage · No test reaches this file scripts/tables/languagesTable.ts
- Test Coverage · No test reaches this file scripts/generators/categoriesGenerator.ts
- Test Coverage · No test reaches this file scripts/generators/languagesGenerator.ts
- Test Coverage · No test reaches this file scripts/generators/indexCategoryGenerator.ts
- Test Coverage · No test reaches this file scripts/generators/indexLanguageGenerator.ts
- Test Coverage · No test reaches this file scripts/generators/citiesGenerator.ts
- Test Coverage · No test reaches this file scripts/generators/regionsGenerator.ts
- Test Coverage · No test reaches this file scripts/generators/subdivisionsGenerator.ts
- Test Coverage · No test reaches this file scripts/generators/sourcesGenerator.ts
- Test Coverage · No test reaches this file scripts/tables/regionsTable.ts
- Test Coverage · No test reaches this file scripts/generators/rawGenerator.ts
- Test Coverage · No test reaches this file scripts/generators/indexGenerator.ts
- Test Coverage · No test reaches this file scripts/commands/playlist/export.ts
- Test Coverage · No test reaches this file scripts/commands/readme/update.ts
- Test Coverage · No test reaches this file scripts/commands/api/load.ts
- Async correctness · `async` callback passed to `forEach` scripts/generators/categoriesGenerator.ts
- Async correctness · `async` callback passed to `forEach` scripts/generators/languagesGenerator.ts
- Exception handling · Swallowed exception (empty catch) scripts/utils.ts
- Exception handling · Swallowed exception (empty catch) scripts/utils.ts
- Exception handling · Swallowed exception (empty catch) scripts/utils.ts
- Incompleteness & stubs · Fake-async — async method never awaits scripts/commands/playlist/update.ts
- Incompleteness & stubs · Fake-async — async method never awaits scripts/commands/playlist/update.ts
Rebuild cost: about €7,600 · Estimate
| Cost to rebuild | €2,500 to €13,000, for 42 to 133 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.8 at a score of 59. 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: 3,704 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 commands.api | 2 commands.discussion | 3 commands.issue | 4 commands.readme | 5 commands.report | 6 core.dataSet | 7 core.htmlTable | 8 core.logParser | 9 core.markdown | 10 core.numberParser | 11 core.proxyParser | 12 generators.generator | 13 tables.table | 14 core.cliTable | 15 models.discussion | 16 models.issue | 17 models.stream | 18 tables.categoriesTable | 19 tables.countriesTable | 20 tables.languagesTable | 21 tables.regionsTable | 22 commands.playlist | 23 core.playlistParser | 24 core.streamTester | 25 generators.categoriesGenerator | 26 generators.citiesGenerator | 27 generators.countriesGenerator | 28 generators.indexCategoryGenerator | 29 generators.indexCountryGenerator | 30 generators.indexGenerator | 31 generators.indexLanguageGenerator | 32 generators.languagesGenerator | 33 generators.rawGenerator | 34 generators.regionsGenerator | 35 generators.sourcesGenerator | 36 generators.subdivisionsGenerator | 37 models.playlist | 38 utils | 39 scripts |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 commands.api | |||||||||||||||||||||||||||||||||||||||
| 2 commands.discussion | |||||||||||||||||||||||||||||||||||||||
| 3 commands.issue | |||||||||||||||||||||||||||||||||||||||
| 4 commands.readme | |||||||||||||||||||||||||||||||||||||||
| 5 commands.report | |||||||||||||||||||||||||||||||||||||||
| 6 core.dataSet | |||||||||||||||||||||||||||||||||||||||
| 7 core.htmlTable | |||||||||||||||||||||||||||||||||||||||
| 8 core.logParser | |||||||||||||||||||||||||||||||||||||||
| 9 core.markdown | |||||||||||||||||||||||||||||||||||||||
| 10 core.numberParser | |||||||||||||||||||||||||||||||||||||||
| 11 core.proxyParser | |||||||||||||||||||||||||||||||||||||||
| 12 generators.generator | |||||||||||||||||||||||||||||||||||||||
| 13 tables.table | |||||||||||||||||||||||||||||||||||||||
| 14 core.cliTable | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 models.discussion | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 models.issue | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 models.stream | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 tables.categoriesTable | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 tables.countriesTable | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 tables.languagesTable | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 tables.regionsTable | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 commands.playlist | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 core.playlistParser | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 core.streamTester | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 generators.categoriesGenerator | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 generators.citiesGenerator | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 generators.countriesGenerator | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 generators.indexCategoryGenerator | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 generators.indexCountryGenerator | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 generators.indexGenerator | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 generators.indexLanguageGenerator | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 generators.languagesGenerator | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 generators.rawGenerator | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 generators.regionsGenerator | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 generators.sourcesGenerator | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 generators.subdivisionsGenerator | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 models.playlist | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 utils | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 scripts | 1 | 1 | 1 | 1 |
14→13 core.cliTable uses tables.table✕
- Connections
- 1 pair of types, where a type in core.cliTable uses a type in tables.table.
- The types involved
scripts.core.cliTable.CliTable→scripts.tables.table.Table
- Direction
- core.cliTable uses tables.table, so a change to tables.table can break core.cliTable, while a change to core.cliTable can't break tables.table.
- Position
- Below the diagonal: core.cliTable uses a module listed above it, which is the healthy direction.
15→6 models.discussion uses core.dataSet✕
- Connections
- 1 pair of types, where a type in models.discussion uses a type in core.dataSet.
- The types involved
scripts.models.discussion.Discussion→scripts.core.dataSet.DataSet
- Direction
- models.discussion uses core.dataSet, so a change to core.dataSet can break models.discussion, while a change to models.discussion can't break core.dataSet.
- Position
- Below the diagonal: models.discussion uses a module listed above it, which is the healthy direction.
16→6 models.issue uses core.dataSet✕
- Connections
- 1 pair of types, where a type in models.issue uses a type in core.dataSet.
- The types involved
scripts.models.issue.Issue→scripts.core.dataSet.DataSet
- Direction
- models.issue uses core.dataSet, so a change to core.dataSet can break models.issue, while a change to models.issue can't break core.dataSet.
- Position
- Below the diagonal: models.issue uses a module listed above it, which is the healthy direction.
17→6 models.stream uses core.dataSet✕
- Connections
- 1 pair of types, where a type in models.stream uses a type in core.dataSet.
- The types involved
scripts.models.stream.Stream→scripts.core.dataSet.DataSet
- Direction
- models.stream uses core.dataSet, so a change to core.dataSet can break models.stream, while a change to models.stream can't break core.dataSet.
- Position
- Below the diagonal: models.stream uses a module listed above it, which is the healthy direction.
18→13 tables.categoriesTable uses tables.table✕
- Connections
- 1 pair of types, where a type in tables.categoriesTable uses a type in tables.table.
- The types involved
scripts.tables.categoriesTable.CategoriesTable→scripts.tables.table.Table
- Direction
- tables.categoriesTable uses tables.table, so a change to tables.table can break tables.categoriesTable, while a change to tables.categoriesTable can't break tables.table.
- Position
- Below the diagonal: tables.categoriesTable uses a module listed above it, which is the healthy direction.
19→13 tables.countriesTable uses tables.table✕
- Connections
- 1 pair of types, where a type in tables.countriesTable uses a type in tables.table.
- The types involved
scripts.tables.countriesTable.CountriesTable→scripts.tables.table.Table
- Direction
- tables.countriesTable uses tables.table, so a change to tables.table can break tables.countriesTable, while a change to tables.countriesTable can't break tables.table.
- Position
- Below the diagonal: tables.countriesTable uses a module listed above it, which is the healthy direction.
20→13 tables.languagesTable uses tables.table✕
- Connections
- 1 pair of types, where a type in tables.languagesTable uses a type in tables.table.
- The types involved
scripts.tables.languagesTable.LanguagesTable→scripts.tables.table.Table
- Direction
- tables.languagesTable uses tables.table, so a change to tables.table can break tables.languagesTable, while a change to tables.languagesTable can't break tables.table.
- Position
- Below the diagonal: tables.languagesTable uses a module listed above it, which is the healthy direction.
21→13 tables.regionsTable uses tables.table✕
- Connections
- 1 pair of types, where a type in tables.regionsTable uses a type in tables.table.
- The types involved
scripts.tables.regionsTable.RegionsTable→scripts.tables.table.Table
- Direction
- tables.regionsTable uses tables.table, so a change to tables.table can break tables.regionsTable, while a change to tables.regionsTable can't break tables.table.
- Position
- Below the diagonal: tables.regionsTable uses a module listed above it, which is the healthy direction.
22→16 commands.playlist uses models.issue✕
- Connections
- 1 pair of types, where a type in commands.playlist uses a type in models.issue.
- The types involved
scripts.commands.playlist.update→scripts.models.issue.Issue
- Direction
- commands.playlist uses models.issue, so a change to models.issue can break commands.playlist, while a change to commands.playlist can't break models.issue.
- Position
- Below the diagonal: commands.playlist uses a module listed above it, which is the healthy direction.
22→17 commands.playlist uses models.stream✕
- Connections
- 2 pairs of types, where a type in commands.playlist uses a type in models.stream.
- The types involved
scripts.commands.playlist.edit→scripts.models.stream.Streamscripts.commands.playlist.test→scripts.models.stream.Stream
- Direction
- commands.playlist uses models.stream, so a change to models.stream can break commands.playlist, while a change to commands.playlist can't break models.stream.
- Position
- Below the diagonal: commands.playlist uses a module listed above it, which is the healthy direction.
23→17 core.playlistParser uses models.stream✕
- Connections
- 1 pair of types, where a type in core.playlistParser uses a type in models.stream.
- The types involved
scripts.core.playlistParser.PlaylistParser→scripts.models.stream.Stream
- Direction
- core.playlistParser uses models.stream, so a change to models.stream can break core.playlistParser, while a change to core.playlistParser can't break models.stream.
- Position
- Below the diagonal: core.playlistParser uses a module listed above it, which is the healthy direction.
24→17 core.streamTester uses models.stream✕
- Connections
- 1 pair of types, where a type in core.streamTester uses a type in models.stream.
- The types involved
scripts.core.streamTester.StreamTester→scripts.models.stream.Stream
- Direction
- core.streamTester uses models.stream, so a change to models.stream can break core.streamTester, while a change to core.streamTester can't break models.stream.
- Position
- Below the diagonal: core.streamTester uses a module listed above it, which is the healthy direction.
25→12 generators.categoriesGenerator uses generators.generator✕
- Connections
- 1 pair of types, where a type in generators.categoriesGenerator uses a type in generators.generator.
- The types involved
scripts.generators.categoriesGenerator.CategoriesGenerator→scripts.generators.generator.Generator
- Direction
- generators.categoriesGenerator uses generators.generator, so a change to generators.generator can break generators.categoriesGenerator, while a change to generators.categoriesGenerator can't break generators.generator.
- Position
- Below the diagonal: generators.categoriesGenerator uses a module listed above it, which is the healthy direction.
25→17 generators.categoriesGenerator uses models.stream✕
- Connections
- 1 pair of types, where a type in generators.categoriesGenerator uses a type in models.stream.
- The types involved
scripts.generators.categoriesGenerator.CategoriesGenerator→scripts.models.stream.Stream
- Direction
- generators.categoriesGenerator uses models.stream, so a change to models.stream can break generators.categoriesGenerator, while a change to generators.categoriesGenerator can't break models.stream.
- Position
- Below the diagonal: generators.categoriesGenerator uses a module listed above it, which is the healthy direction.
26→12 generators.citiesGenerator uses generators.generator✕
- Connections
- 1 pair of types, where a type in generators.citiesGenerator uses a type in generators.generator.
- The types involved
scripts.generators.citiesGenerator.CitiesGenerator→scripts.generators.generator.Generator
- Direction
- generators.citiesGenerator uses generators.generator, so a change to generators.generator can break generators.citiesGenerator, while a change to generators.citiesGenerator can't break generators.generator.
- Position
- Below the diagonal: generators.citiesGenerator uses a module listed above it, which is the healthy direction.
26→17 generators.citiesGenerator uses models.stream✕
- Connections
- 1 pair of types, where a type in generators.citiesGenerator uses a type in models.stream.
- The types involved
scripts.generators.citiesGenerator.CitiesGenerator→scripts.models.stream.Stream
- Direction
- generators.citiesGenerator uses models.stream, so a change to models.stream can break generators.citiesGenerator, while a change to generators.citiesGenerator can't break models.stream.
- Position
- Below the diagonal: generators.citiesGenerator uses a module listed above it, which is the healthy direction.
27→12 generators.countriesGenerator uses generators.generator✕
- Connections
- 1 pair of types, where a type in generators.countriesGenerator uses a type in generators.generator.
- The types involved
scripts.generators.countriesGenerator.CountriesGenerator→scripts.generators.generator.Generator
- Direction
- generators.countriesGenerator uses generators.generator, so a change to generators.generator can break generators.countriesGenerator, while a change to generators.countriesGenerator can't break generators.generator.
- Position
- Below the diagonal: generators.countriesGenerator uses a module listed above it, which is the healthy direction.
27→17 generators.countriesGenerator uses models.stream✕
- Connections
- 1 pair of types, where a type in generators.countriesGenerator uses a type in models.stream.
- The types involved
scripts.generators.countriesGenerator.CountriesGenerator→scripts.models.stream.Stream
- Direction
- generators.countriesGenerator uses models.stream, so a change to models.stream can break generators.countriesGenerator, while a change to generators.countriesGenerator can't break models.stream.
- Position
- Below the diagonal: generators.countriesGenerator uses a module listed above it, which is the healthy direction.
28→12 generators.indexCategoryGenerator uses generators.generator✕
- Connections
- 1 pair of types, where a type in generators.indexCategoryGenerator uses a type in generators.generator.
- The types involved
scripts.generators.indexCategoryGenerator.IndexCategoryGenerator→scripts.generators.generator.Generator
- Direction
- generators.indexCategoryGenerator uses generators.generator, so a change to generators.generator can break generators.indexCategoryGenerator, while a change to generators.indexCategoryGenerator can't break generators.generator.
- Position
- Below the diagonal: generators.indexCategoryGenerator uses a module listed above it, which is the healthy direction.
28→17 generators.indexCategoryGenerator uses models.stream✕
- Connections
- 1 pair of types, where a type in generators.indexCategoryGenerator uses a type in models.stream.
- The types involved
scripts.generators.indexCategoryGenerator.IndexCategoryGenerator→scripts.models.stream.Stream
- Direction
- generators.indexCategoryGenerator uses models.stream, so a change to models.stream can break generators.indexCategoryGenerator, while a change to generators.indexCategoryGenerator can't break models.stream.
- Position
- Below the diagonal: generators.indexCategoryGenerator uses a module listed above it, which is the healthy direction.
29→12 generators.indexCountryGenerator uses generators.generator✕
- Connections
- 1 pair of types, where a type in generators.indexCountryGenerator uses a type in generators.generator.
- The types involved
scripts.generators.indexCountryGenerator.IndexCountryGenerator→scripts.generators.generator.Generator
- Direction
- generators.indexCountryGenerator uses generators.generator, so a change to generators.generator can break generators.indexCountryGenerator, while a change to generators.indexCountryGenerator can't break generators.generator.
- Position
- Below the diagonal: generators.indexCountryGenerator uses a module listed above it, which is the healthy direction.
29→17 generators.indexCountryGenerator uses models.stream✕
- Connections
- 1 pair of types, where a type in generators.indexCountryGenerator uses a type in models.stream.
- The types involved
scripts.generators.indexCountryGenerator.IndexCountryGenerator→scripts.models.stream.Stream
- Direction
- generators.indexCountryGenerator uses models.stream, so a change to models.stream can break generators.indexCountryGenerator, while a change to generators.indexCountryGenerator can't break models.stream.
- Position
- Below the diagonal: generators.indexCountryGenerator uses a module listed above it, which is the healthy direction.
30→12 generators.indexGenerator uses generators.generator✕
- Connections
- 1 pair of types, where a type in generators.indexGenerator uses a type in generators.generator.
- The types involved
scripts.generators.indexGenerator.IndexGenerator→scripts.generators.generator.Generator
- Direction
- generators.indexGenerator uses generators.generator, so a change to generators.generator can break generators.indexGenerator, while a change to generators.indexGenerator can't break generators.generator.
- Position
- Below the diagonal: generators.indexGenerator uses a module listed above it, which is the healthy direction.
30→17 generators.indexGenerator uses models.stream✕
- Connections
- 1 pair of types, where a type in generators.indexGenerator uses a type in models.stream.
- The types involved
scripts.generators.indexGenerator.IndexGenerator→scripts.models.stream.Stream
- Direction
- generators.indexGenerator uses models.stream, so a change to models.stream can break generators.indexGenerator, while a change to generators.indexGenerator can't break models.stream.
- Position
- Below the diagonal: generators.indexGenerator uses a module listed above it, which is the healthy direction.
31→12 generators.indexLanguageGenerator uses generators.generator✕
- Connections
- 1 pair of types, where a type in generators.indexLanguageGenerator uses a type in generators.generator.
- The types involved
scripts.generators.indexLanguageGenerator.IndexLanguageGenerator→scripts.generators.generator.Generator
- Direction
- generators.indexLanguageGenerator uses generators.generator, so a change to generators.generator can break generators.indexLanguageGenerator, while a change to generators.indexLanguageGenerator can't break generators.generator.
- Position
- Below the diagonal: generators.indexLanguageGenerator uses a module listed above it, which is the healthy direction.
31→17 generators.indexLanguageGenerator uses models.stream✕
- Connections
- 1 pair of types, where a type in generators.indexLanguageGenerator uses a type in models.stream.
- The types involved
scripts.generators.indexLanguageGenerator.IndexLanguageGenerator→scripts.models.stream.Stream
- Direction
- generators.indexLanguageGenerator uses models.stream, so a change to models.stream can break generators.indexLanguageGenerator, while a change to generators.indexLanguageGenerator can't break models.stream.
- Position
- Below the diagonal: generators.indexLanguageGenerator uses a module listed above it, which is the healthy direction.
32→12 generators.languagesGenerator uses generators.generator✕
- Connections
- 1 pair of types, where a type in generators.languagesGenerator uses a type in generators.generator.
- The types involved
scripts.generators.languagesGenerator.LanguagesGenerator→scripts.generators.generator.Generator
- Direction
- generators.languagesGenerator uses generators.generator, so a change to generators.generator can break generators.languagesGenerator, while a change to generators.languagesGenerator can't break generators.generator.
- Position
- Below the diagonal: generators.languagesGenerator uses a module listed above it, which is the healthy direction.
32→17 generators.languagesGenerator uses models.stream✕
- Connections
- 1 pair of types, where a type in generators.languagesGenerator uses a type in models.stream.
- The types involved
scripts.generators.languagesGenerator.LanguagesGenerator→scripts.models.stream.Stream
- Direction
- generators.languagesGenerator uses models.stream, so a change to models.stream can break generators.languagesGenerator, while a change to generators.languagesGenerator can't break models.stream.
- Position
- Below the diagonal: generators.languagesGenerator uses a module listed above it, which is the healthy direction.
33→12 generators.rawGenerator uses generators.generator✕
- Connections
- 1 pair of types, where a type in generators.rawGenerator uses a type in generators.generator.
- The types involved
scripts.generators.rawGenerator.RawGenerator→scripts.generators.generator.Generator
- Direction
- generators.rawGenerator uses generators.generator, so a change to generators.generator can break generators.rawGenerator, while a change to generators.rawGenerator can't break generators.generator.
- Position
- Below the diagonal: generators.rawGenerator uses a module listed above it, which is the healthy direction.
33→17 generators.rawGenerator uses models.stream✕
- Connections
- 1 pair of types, where a type in generators.rawGenerator uses a type in models.stream.
- The types involved
scripts.generators.rawGenerator.RawGenerator→scripts.models.stream.Stream
- Direction
- generators.rawGenerator uses models.stream, so a change to models.stream can break generators.rawGenerator, while a change to generators.rawGenerator can't break models.stream.
- Position
- Below the diagonal: generators.rawGenerator uses a module listed above it, which is the healthy direction.
34→12 generators.regionsGenerator uses generators.generator✕
- Connections
- 1 pair of types, where a type in generators.regionsGenerator uses a type in generators.generator.
- The types involved
scripts.generators.regionsGenerator.RegionsGenerator→scripts.generators.generator.Generator
- Direction
- generators.regionsGenerator uses generators.generator, so a change to generators.generator can break generators.regionsGenerator, while a change to generators.regionsGenerator can't break generators.generator.
- Position
- Below the diagonal: generators.regionsGenerator uses a module listed above it, which is the healthy direction.
34→17 generators.regionsGenerator uses models.stream✕
- Connections
- 1 pair of types, where a type in generators.regionsGenerator uses a type in models.stream.
- The types involved
scripts.generators.regionsGenerator.RegionsGenerator→scripts.models.stream.Stream
- Direction
- generators.regionsGenerator uses models.stream, so a change to models.stream can break generators.regionsGenerator, while a change to generators.regionsGenerator can't break models.stream.
- Position
- Below the diagonal: generators.regionsGenerator uses a module listed above it, which is the healthy direction.
35→12 generators.sourcesGenerator uses generators.generator✕
- Connections
- 1 pair of types, where a type in generators.sourcesGenerator uses a type in generators.generator.
- The types involved
scripts.generators.sourcesGenerator.SourcesGenerator→scripts.generators.generator.Generator
- Direction
- generators.sourcesGenerator uses generators.generator, so a change to generators.generator can break generators.sourcesGenerator, while a change to generators.sourcesGenerator can't break generators.generator.
- Position
- Below the diagonal: generators.sourcesGenerator uses a module listed above it, which is the healthy direction.
35→17 generators.sourcesGenerator uses models.stream✕
- Connections
- 1 pair of types, where a type in generators.sourcesGenerator uses a type in models.stream.
- The types involved
scripts.generators.sourcesGenerator.SourcesGenerator→scripts.models.stream.Stream
- Direction
- generators.sourcesGenerator uses models.stream, so a change to models.stream can break generators.sourcesGenerator, while a change to generators.sourcesGenerator can't break models.stream.
- Position
- Below the diagonal: generators.sourcesGenerator uses a module listed above it, which is the healthy direction.
36→12 generators.subdivisionsGenerator uses generators.generator✕
- Connections
- 1 pair of types, where a type in generators.subdivisionsGenerator uses a type in generators.generator.
- The types involved
scripts.generators.subdivisionsGenerator.SubdivisionsGenerator→scripts.generators.generator.Generator
- Direction
- generators.subdivisionsGenerator uses generators.generator, so a change to generators.generator can break generators.subdivisionsGenerator, while a change to generators.subdivisionsGenerator can't break generators.generator.
- Position
- Below the diagonal: generators.subdivisionsGenerator uses a module listed above it, which is the healthy direction.
36→17 generators.subdivisionsGenerator uses models.stream✕
- Connections
- 1 pair of types, where a type in generators.subdivisionsGenerator uses a type in models.stream.
- The types involved
scripts.generators.subdivisionsGenerator.SubdivisionsGenerator→scripts.models.stream.Stream
- Direction
- generators.subdivisionsGenerator uses models.stream, so a change to models.stream can break generators.subdivisionsGenerator, while a change to generators.subdivisionsGenerator can't break models.stream.
- Position
- Below the diagonal: generators.subdivisionsGenerator uses a module listed above it, which is the healthy direction.
37→17 models.playlist uses models.stream✕
- Connections
- 1 pair of types, where a type in models.playlist uses a type in models.stream.
- The types involved
scripts.models.playlist.Playlist→scripts.models.stream.Stream
- Direction
- models.playlist uses models.stream, so a change to models.stream can break models.playlist, while a change to models.playlist can't break models.stream.
- Position
- Below the diagonal: models.playlist uses a module listed above it, which is the healthy direction.
38→16 utils uses models.issue✕
- Connections
- 1 pair of types, where a type in utils uses a type in models.issue.
- The types involved
scripts.utils.LogThread→scripts.models.issue.Issue
- Direction
- utils uses models.issue, so a change to models.issue can break utils, while a change to utils can't break models.issue.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
39→6 scripts uses core.dataSet✕
- Connections
- 1 pair of types, where a type in scripts uses a type in core.dataSet.
- The types involved
scripts.utils→scripts.core.dataSet.DataSet
- Direction
- scripts uses core.dataSet, so a change to core.dataSet can break scripts, while a change to scripts can't break core.dataSet.
- Position
- Below the diagonal: scripts uses a module listed above it, which is the healthy direction.
39→15 scripts uses models.discussion✕
- Connections
- 1 pair of types, where a type in scripts uses a type in models.discussion.
- The types involved
scripts.utils→scripts.models.discussion.Discussion
- Direction
- scripts uses models.discussion, so a change to models.discussion can break scripts, while a change to scripts can't break models.discussion.
- Position
- Below the diagonal: scripts uses a module listed above it, which is the healthy direction.
39→16 scripts uses models.issue✕
- Connections
- 1 pair of types, where a type in scripts uses a type in models.issue.
- The types involved
scripts.utils→scripts.models.issue.Issue
- Direction
- scripts uses models.issue, so a change to models.issue can break scripts, while a change to scripts can't break models.issue.
- Position
- Below the diagonal: scripts uses a module listed above it, which is the healthy direction.
39→38 scripts uses utils✕
- Connections
- 1 pair of types, where a type in scripts uses a type in utils.
- The types involved
scripts.utils→scripts.utils.LogThread
- Direction
- scripts uses utils, so a change to utils can break scripts, while a change to scripts can't break utils.
- Position
- Below the diagonal: scripts 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 |
|---|---|---|
| A07:2025 — Authentication Failures | 827 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | High / Critical |
| A05:2025 — Injection | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 3 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (3); Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing; Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with package.json (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (3). | +2.5 pts | Low | Dependency Hygiene |
| Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with package.json (2). | +2.2 pts | Low | Dependency Hygiene |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +2.4 pts | Medium | Security & performance tooling |
| 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. | +1.9 pts | Medium | Deployment & Rollback |
| Resolve the 1 No assertions finding(s) in Test Quality — start with validate.test.ts. | +0.9 pts | Low | Test Quality |
| TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants. | +1.6 pts | Medium | Async & latency hygiene |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.8 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. | +1.1 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.5 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 40 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 891 of 917 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
- D20 ADR Quality — 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. The ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a package.json `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository. Read, stating neither a host nor a published package: `package.json`.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and no container it models, or knows cannot hold a captive, was found in this repository's source, 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.
- 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.
- C2 Access Controls — 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 authorization 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 authorization controls.
- C3 Audit Trail — 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 audit 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 audit controls.
- C4 Data Retention — 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 retention 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 retention controls.
- C5 Data-Subject Rights — 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 data-subject rights 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 data-subject rights controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found 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.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found 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.
- 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.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- 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.
- X1 Async 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, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust 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.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, 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.
- X13 Undrained process stream — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, 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.
- X14 Bypassable address classification — 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, Scala, Rust, Swift, Ruby, Dart, PHP, Python and Go source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, Rust, Swift, Ruby, Dart, PHP, Python or Go 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.
- X15 Unvalidated length from an untrusted reader — 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, Scala, PHP, Ruby, Python, Go, Rust and Dart source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust or Dart 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.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python 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.
- X21 Side-effecting pattern 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# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Kotlin, Ruby, PHP, Python, Dart, Rust and Scala source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Ruby, PHP, Python, Dart, Rust or Scala 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — 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, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- X25 Inert configuration knob — 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, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby 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 and no Java, Kotlin, Scala, Go, Swift, Python or Ruby 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.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no Java, Rust, Erlang, F#, Python, 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.
- X28 Index access outside its own emptiness 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 F#, Scala, JavaScript, TypeScript, Python, Ruby, Go, Java, Kotlin, Swift, Dart, PHP, Rust, Elixir and Erlang source only, and no C# was loaded and no Visual Basic, F#, Scala, JavaScript, TypeScript, Python, Ruby, Go, Java, Kotlin, Swift, Dart, PHP, Rust, Elixir or Erlang 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.
- 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.
- X30 Support guard that admits what it rejects — 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 Scala, JavaScript/TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart and Ruby source only, and no C# was loaded and no Scala, JavaScript, TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart or Ruby 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.
- X4 Structured logging — 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, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala 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.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded and no 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.
- X6 Hand-rolled structured-format parsing — 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 Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages 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.
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
- 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.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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 REDACTED Scanning: REDACTED 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.
- 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.
- 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.
- 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".
Dimensions
D3 · God Classes
0 god class(es) detected.
D6 · Cohesion (LCOM4)
0 of 4 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 40 tests.
What to do
- Resolve the 1 No assertions finding(s) in Test Quality — start with validate.test.ts. — One of this dimension's main actionable groups (1 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `npm ci --ignore-scripts` in the repository root (40 tests)): measured (0 flaky).
D12 · Dependency Hygiene
21 outdated direct production npm dependency(ies) of 41 graded, 0 pinning defect(s), across 1 package.json (1 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 2 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What to do
- Resolve the 3 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (3). — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with package.json (2). — One of this dimension's main actionable groups (2 warning-level).
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 324 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 324 package(s) this repository's committed lockfile installs for a consumer — its 41 production, optional and peer dependency(ies), across 1 product package.json manifest(s), and everything those install in turn. Its 0 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: scripts/commands/report/create.ts (2×39=78); scripts/commands/playlist/validate.ts (3×25=75); scripts/commands/playlist/update.ts (3×17=51) Repeated repair below the complexity floor: scripts/utils.ts (11 of 13 changes were fixes)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with create.ts, validate.ts, update.ts. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with utils.ts. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is scripts/commands/playlist/update.ts. Counted over 15 of the 51 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 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
0 deducted task-comment markers across 3704 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 11 document(s) read across 1 unit(s).
D28 · Secrets (history)
826 finding(s): 0 critical, 826 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 826 REDACTED finding(s) in Secrets (history) — start with REDACTED (156), REDACTED (155), REDACTED (149). — One of this dimension's main actionable groups (826 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
4 finding(s): 0 critical, 1 high, 3 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 15 of the 51 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.
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 0 platform declaration(s) and 41 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
AX6 · Interface segregation
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- 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
- Nothing in the layout marks which files are the product and which are its tooling: no production source was found set apart in a directory of its own.
M4 · Documentation accuracy
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Run the test suite in CI via an explicit runner step (`npm test` for the toolchain this pipeline already uses) and gate merges on it.
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 6 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/check.yml:4
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, 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 entry to the `updates:` list. — REDACTED:2
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry 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
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.
PF3 · Async & latency hygiene
- `storage.existsSync` in `parse` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/core/playlistParser.ts:21
- `fs.readFileSync` in `getStreamInfo` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — scripts/utils.ts:140, scripts/utils.ts:145
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
R10 · Code Duplication
- scripts/tables/categoriesTable.ts:10 · scripts/tables/languagesTable.ts:10 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — scripts/tables/categoriesTable.ts:10
- scripts/commands/playlist/update.ts:108 · scripts/commands/playlist/update.ts:188 — the two spans are one implementation copied and then locally edited — 244 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — scripts/commands/playlist/update.ts:108
- scripts/generators/citiesGenerator.ts:8 · scripts/generators/regionsGenerator.ts:8 · scripts/generators/subdivisionsGenerator.ts:8 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — scripts/generators/citiesGenerator.ts:8
- scripts/generators/citiesGenerator.ts:5 · scripts/generators/countriesGenerator.ts:5 · scripts/generators/regionsGenerator.ts:5 · scripts/generators/subdivisionsGenerator.ts:5 — the 4 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — scripts/generators/citiesGenerator.ts:5
- scripts/generators/indexCategoryGenerator.ts:24 · scripts/generators/indexLanguageGenerator.ts:24 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — scripts/generators/indexCategoryGenerator.ts:24
- scripts/commands/playlist/format.ts:13 · scripts/commands/playlist/test.ts:34 — the two spans are one implementation copied and then locally edited — 178 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — scripts/commands/playlist/format.ts:13
- scripts/generators/rawGenerator.ts:7 · scripts/generators/sourcesGenerator.ts:7 — the two spans are one implementation copied and then locally edited — 213 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — scripts/generators/rawGenerator.ts:7
- scripts/generators/indexCountryGenerator.ts:8 · scripts/generators/indexLanguageGenerator.ts:8 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/generators/indexCountryGenerator.ts:8
- scripts/commands/report/create.ts:85 · scripts/commands/report/create.ts:117 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/commands/report/create.ts:85
- scripts/generators/indexCategoryGenerator.ts:8 · scripts/generators/indexCountryGenerator.ts:8 · scripts/generators/indexLanguageGenerator.ts:8 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/generators/indexCategoryGenerator.ts:8
- scripts/generators/indexGenerator.ts:7 · scripts/generators/rawGenerator.ts:7 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/generators/indexGenerator.ts:7
- scripts/commands/playlist/export.ts:8 · scripts/commands/playlist/generate.ts:23 — the two spans are one implementation copied and then locally edited — 76 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — scripts/commands/playlist/export.ts:8
- scripts/commands/discussion/validate.ts:29 · scripts/commands/report/create.ts:28 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — scripts/commands/discussion/validate.ts:29
- scripts/core/streamTester.ts:38 · scripts/utils.ts:164 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — scripts/core/streamTester.ts:38
- scripts/commands/playlist/generate.ts:31 · scripts/commands/playlist/update.ts:77 — the two spans are one implementation copied and then locally edited — 72 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — scripts/commands/playlist/generate.ts:31
- scripts/generators/categoriesGenerator.ts:32 · scripts/generators/indexGenerator.ts:25 · scripts/generators/rawGenerator.ts:27 · scripts/generators/sourcesGenerator.ts:31 — the 4 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — scripts/generators/categoriesGenerator.ts:32
- scripts/tables/countriesTable.ts:81 · scripts/tables/countriesTable.ts:102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — scripts/tables/countriesTable.ts:81
- scripts/utils.ts:289 · scripts/utils.ts:375 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/utils.ts:289
- scripts/generators/languagesGenerator.ts:36 · scripts/generators/languagesGenerator.ts:48 — the two spans are one implementation copied and then locally edited — 86 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — scripts/generators/languagesGenerator.ts:36
- scripts/commands/issue/validate.ts:130 · scripts/commands/playlist/update.ts:220 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/commands/issue/validate.ts:130
- scripts/commands/playlist/format.ts:124 · scripts/commands/playlist/update.ts:65 — the two spans are one implementation copied and then locally edited — 66 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — scripts/commands/playlist/format.ts:124
- scripts/tables/countriesTable.ts:15 · scripts/tables/regionsTable.ts:13 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/tables/countriesTable.ts:15
- scripts/commands/report/create.ts:146 · scripts/commands/report/create.ts:158 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/commands/report/create.ts:146
- scripts/tables/countriesTable.ts:101 · scripts/tables/regionsTable.ts:24 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/tables/countriesTable.ts:101
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- scripts/core/cliTable.ts:1 imports console-table-printer/dist/src/models/external-table, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — scripts/core/cliTable.ts:1
- scripts/core/streamTester.ts:58 imports tests/__data__/input/playlist_test/results.js, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/core/streamTester.ts:58
- scripts/utils.ts:251 imports tests/__data__/input/issues.js, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/utils.ts:251
- scripts/utils.ts:324 imports tests/__data__/input/discussions.js, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/utils.ts:324
What to do
- Fix the listed violations: move the shared test helper into a source directory production code may depend on (3 rows); import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (1 row).
R2 · Cyclomatic Complexity
- main has cyclomatic complexity 18 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/commands/discussion/validate.ts:28
- addStream has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/commands/playlist/update.ts:188
- main has cyclomatic complexity 14 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/commands/issue/validate.ts:22
- updateWithIssue has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/models/stream.ts:44
- (anonymous) has cyclomatic complexity 13 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/commands/report/create.ts:162
- test has cyclomatic complexity 12 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/core/streamTester.ts:56
- getStreamInfo has cyclomatic complexity 11 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/utils.ts:128
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/models/stream.ts:205
- parseStreamInfo has cyclomatic complexity 11 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/utils.ts:190
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — scripts/commands/report/create.ts:86, scripts/utils.ts:292
R3 · Large Files
- scripts/models/stream.ts has 438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — scripts/models/stream.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R5 · Dependency Freshness
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- Nothing ultimately consumes this binding: its only referrer is the re-export in scripts/core/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in scripts/core/index.ts in the same commit, or the barrel will import a name that no longer exists. — scripts/core/numberParser.ts:1
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — tests/commands/discussion/validate.test.ts:4
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
- Only test files import it (first: tests/commands/playlist/format.test.ts:5) — move it to devDependencies. — package.json:59
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- scripts/core/index.ts → scripts/core/playlistParser.ts → scripts/models/index.ts → scripts/models/discussion.ts → scripts/core/index.ts (one verified cycle inside a mutually-dependent group of 9 files) — scripts/core/index.ts:7
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 69% | Adequate — gated by R10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 72% | Adequate — gated by R11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 61% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 56% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 61% | Checked 3 of 9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit 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 audit 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.
- C4 Data Retention — Not assessed: these retention 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 retention 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.
- C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 82 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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
- 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.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — Not assessed: these authorization 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 authorization 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.
- D1 Cyclomatic Complexity — cyclomatic complexity does not apply: all 155 method(s) the analysis read sit in demonstration, test, vendored or generated trees, so this repository has no authored production method to measure. Not scored.
- 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 does not apply: all 155 method(s) the analysis read sit in demonstration, test, vendored or generated trees, so this repository has no authored production method to measure. Not scored.
- D20 ADR Quality — Repository kind not determined
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (329 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- 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 — Too few judgeable comments (4 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (3704 LoC, 45 module-visible types across 11 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
- 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.
- D36 Supply-chain Provenance & Signing — 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).
- 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.
- D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- 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.
- D5 Coupling — Not applicable — this npm 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 MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- 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 tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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.
- R4 Test Coverage — no production JavaScript/TypeScript files to cover (20 test file(s) present) — nothing to measure
- 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async 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
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X14 Bypassable address classification — 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
- X15 Unvalidated length from an untrusted reader — 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
- 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 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
- 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 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 — 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
- 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 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
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X23 Unguarded diagnostic materialisation — 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
- 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
- X25 Inert configuration knob — 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 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
- X28 Index access outside its own emptiness 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
- 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
- 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 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
- 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 — 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
- 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 — 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
- 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 — 830 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
- Unlisted import 'fs-extra' tests/commands/discussion/validate.test.ts:4
- Import cycle (4 files) scripts/core/index.ts:7
Serious — 56 finding(s)
- Boundary violation [package:third-party-deep-import] scripts/core/cliTable.ts:1
- Boundary violation [package:test-suite-dependency] scripts/core/streamTester.ts:58
- Boundary violation [package:test-suite-dependency] scripts/utils.ts:251
- Boundary violation [package:test-suite-dependency] scripts/utils.ts:324
- Hotspot: scripts/commands/report/create.ts scripts/commands/report/create.ts:23
- Hotspot: scripts/commands/playlist/validate.ts scripts/commands/playlist/validate.ts:25
- Hotspot: scripts/commands/playlist/update.ts scripts/commands/playlist/update.ts:188
- REDACTED
- REDACTED
- REDACTED
- Sync-over-async blocking scripts/core/playlistParser.ts:21
- Sync-over-async blocking scripts/utils.ts:140
- Sync-over-async blocking scripts/utils.ts:145
- Deprecated: eslint package.json:58
- Deprecated: glob package.json:59
- Duplicated block with local edits (31 matched lines × 2 locations) scripts/commands/playlist/format.ts:13
- Duplicated block with local edits (31 matched lines × 2 locations) scripts/generators/rawGenerator.ts:7
- Duplicated block (14 lines × 2 locations) scripts/commands/report/create.ts:85
- Duplicated block (14 lines × 2 locations) scripts/generators/indexGenerator.ts:7
- Duplicated block (11 lines × 2 locations) scripts/commands/discussion/validate.ts:29
- Duplicated block (11 lines × 2 locations) scripts/core/streamTester.ts:38
- Duplicated block (10 lines × 2 locations) scripts/tables/countriesTable.ts:81
- Duplicated block (10 lines × 2 locations) scripts/utils.ts:289
- Duplicated block (8 lines × 2 locations) scripts/commands/issue/validate.ts:130
- Duplicated block (8 lines × 2 locations) scripts/tables/countriesTable.ts:15
- Duplicated block (6 lines × 2 locations) scripts/commands/report/create.ts:146
- Duplicated block (6 lines × 2 locations) scripts/tables/countriesTable.ts:101
- Complex function (anonymous) (cyclomatic 11, cognitive 11) scripts/commands/report/create.ts:86
- Complex function (anonymous) (cyclomatic 11, cognitive 11) scripts/utils.ts:292
- No assertions: skip the file if it does not exist tests/commands/playlist/validate.test.ts:106
- Repeated repair: scripts/utils.ts scripts/utils.ts:272
- Coverage not measured — JavaScript/TypeScript suite
- Duplicated block (53 lines × 2 locations) scripts/tables/categoriesTable.ts:10
- Duplicated block with local edits (42 matched lines × 2 locations) scripts/commands/playlist/update.ts:108
- Duplicated block (39 lines × 3 locations) scripts/generators/citiesGenerator.ts:8
- Duplicated block (39 lines × 4 locations) scripts/generators/citiesGenerator.ts:5
- Duplicated block (32 lines × 2 locations) scripts/generators/indexCategoryGenerator.ts:24
- Duplicated block (30 lines × 2 locations) scripts/generators/indexCountryGenerator.ts:8
- Duplicated block (14 lines × 3 locations) scripts/generators/indexCategoryGenerator.ts:8
- Duplicated block with local edits (12 matched lines × 2 locations) scripts/commands/playlist/export.ts:8
- Duplicated block with local edits (10 matched lines × 2 locations) scripts/commands/playlist/generate.ts:31
- Duplicated block (10 lines × 4 locations) scripts/generators/categoriesGenerator.ts:32
- Duplicated block with local edits (9 matched lines × 2 locations) scripts/generators/languagesGenerator.ts:36
- Duplicated block with local edits (8 matched lines × 2 locations) scripts/commands/playlist/format.ts:124
- Complex function main (cyclomatic 18, cognitive 19) scripts/commands/discussion/validate.ts:28
- Complex function addStream (cyclomatic 15, cognitive 17) scripts/commands/playlist/update.ts:188
- Complex function main (cyclomatic 14, cognitive 28) scripts/commands/issue/validate.ts:22
- Complex function updateWithIssue (cyclomatic 13, cognitive 13) scripts/models/stream.ts:44
- Complex function (anonymous) (cyclomatic 13, cognitive 10) scripts/commands/report/create.ts:162
- Complex function test (cyclomatic 12, cognitive 24) scripts/core/streamTester.ts:56
- Complex function getStreamInfo (cyclomatic 11, cognitive 17) scripts/utils.ts:128
- Complex function (anonymous) (cyclomatic 11, cognitive 16) scripts/models/stream.ts:205
- Complex function parseStreamInfo (cyclomatic 11, cognitive 15) scripts/utils.ts:190
- scripts/models/stream.ts: 438 lines of code scripts/models/stream.ts:1
- No typecheck script
- Unused dependency '@octokit/types'
Minor — 13 finding(s)
- Outdated (npm): @octokit/plugin-paginate-rest package.json:39
- Outdated (npm): @octokit/types package.json:41
- Outdated (npm): glob package.json:59
- Off-boarding risk: anonymized user #1
- REDACTED
- No ADRs
- No src/ separation
- CI build step not evidenced
- No SAST .github/workflows/check.yml:4
- Dependabot does not watch npm REDACTED:2
- Unused export 'default' scripts/core/numberParser.ts:1
- Test-only dependency 'glob' in production deps package.json:59
- Duplicated predicate scripts/core/streamTester.ts:41
Minor — 18 finding(s)
- Outdated (npm): @eslint/js
- Outdated (npm): @freearhey/core
- Outdated (npm): @freearhey/storage-js
- Outdated (npm): @inquirer/prompts
- Outdated (npm): @octokit/plugin-rest-endpoint-methods
- Outdated (npm): @stylistic/eslint-plugin
- Outdated (npm): @typescript-eslint/eslint-plugin
- Outdated (npm): @typescript-eslint/parser
- Outdated (npm): axios
- Outdated (npm): chalk
- Outdated (npm): commander
- Outdated (npm): es-toolkit
- Outdated (npm): eslint
- Outdated (npm): globals
- Outdated (npm): mpd-parser
- Outdated (npm): normalize-url
- Outdated (npm): socks-proxy-agent
- Outdated (npm): vitest
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-f3b738275afb4420866e5d298aee04a4/history.json --exit-code 0 --source . | 3504 | 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-f3b738275afb4420866e5d298aee04a4/tree.json --exit-code 0 --source . | 13 | 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 . | 1 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 4 | artifacts/raw/trivy-fs.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 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — 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). | 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |