Executive summary
iminashi/Rocksmith2014.NET falls short of our standard for production, in part because it has passwords or keys in the code's history. It scores 53 out of 100 and is rated Adequate, and all 12 of its critical findings are security problems.
Security and Compliance, at 48, is the weakest lens and counts most in the score. The best first steps are replacing the six passwords or keys found in the code's history and improving the documentation, each worth about 4 points. Raising Security and Compliance to 70 would lift the score to about 58.
Six passwords or keys are open to anyone who can read the repository. Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Replacing each exposed password or key and pinning each tool to an exact version would close both risks.
The product code is 29,892 lines, about €52,000 to rebuild.
If Security and Compliance rose from 48 to 70, the lowest score rated Strong, the score would rise from 53 to about 58.
New since the last survey: 4 findings
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Stateful singletons · Process-global static state: InstrumentalArrangement src/Rocksmith2014.XML/InstrumentalArrangement.cs
Fixed since the last survey: 1 finding
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €52,000 · Estimate
| Cost to rebuild | €17,000 to €87,000, for 287 to 916 hours of work, about 0.4 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.7 at a score of 53. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 29,892 lines of product code |
| Comment lines | The estimate prices 28,819 lines. Comment lines count towards the size of 29,892 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Rocksmith2014.Common | 2 Rocksmith2014.Common.Manifest | 3 Rocksmith2014.DD.DataExtractor | 4 Rocksmith2014.DD.Types | 5 Rocksmith2014.DLCProject.ArrangementPropertiesOverride | 6 Rocksmith2014.EOF.ImportTypes | 7 Rocksmith2014.XML.Extension | 8 Rocksmith2014.XML.Processing.Types | 9 Rocksmith2014.DD.EntityChooser | 10 Rocksmith2014.DD.Generator | 11 Rocksmith2014.DD.LevelCounter | 12 Rocksmith2014.DD.NoteScorer | 13 Rocksmith2014.DD.PhraseCombiner | 14 Rocksmith2014.DLCProject | 15 Rocksmith2014.EOF.EOFTypes | 16 Rocksmith2014.PSARC | 17 Rocksmith2014.SNG | 18 BeatWriter | 19 EventConverter | 20 Rocksmith2014.Conversion | 21 Rocksmith2014.Conversion.ConvertInstrumental | 22 Rocksmith2014.Conversion.SngToXml | 23 Rocksmith2014.DLCProject.AggregateGraph | 24 Rocksmith2014.DLCProject.DLCProjectModule | 25 Rocksmith2014.DLCProject.GraphItemModule | 26 Rocksmith2014.DLCProject.Manifest.AttributesCreation | 27 Rocksmith2014.DLCProject.PackageBuilder | 28 Rocksmith2014.DLCProject.PhraseLevelComparer | 29 Rocksmith2014.DLCProject.PsarcImportTypes | 30 Rocksmith2014.DLCProject.PsarcImportUtils | 31 Rocksmith2014.DLCProject.XBlock | 32 Rocksmith2014.EOF.EOFProjectWriter | 33 Rocksmith2014.EOF.ProGuitarWriter | 34 Rocksmith2014.PSARC.Utils | 35 Rocksmith2014.SNG.SNGModule | 36 VocalsWriter | 37 Rocksmith2014.Conversion.ConvertVocals | 38 Rocksmith2014.Conversion.XmlToSng | 39 Rocksmith2014.Conversion.XmlToSngLevel | 40 Rocksmith2014.Conversion.XmlToSngNote |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Rocksmith2014.Common | ||||||||||||||||||||||||||||||||||||||||
| 2 Rocksmith2014.Common.Manifest | ||||||||||||||||||||||||||||||||||||||||
| 3 Rocksmith2014.DD.DataExtractor | ||||||||||||||||||||||||||||||||||||||||
| 4 Rocksmith2014.DD.Types | ||||||||||||||||||||||||||||||||||||||||
| 5 Rocksmith2014.DLCProject.ArrangementPropertiesOverride | ||||||||||||||||||||||||||||||||||||||||
| 6 Rocksmith2014.EOF.ImportTypes | ||||||||||||||||||||||||||||||||||||||||
| 7 Rocksmith2014.XML.Extension | ||||||||||||||||||||||||||||||||||||||||
| 8 Rocksmith2014.XML.Processing.Types | ||||||||||||||||||||||||||||||||||||||||
| 9 Rocksmith2014.DD.EntityChooser | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 Rocksmith2014.DD.Generator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 Rocksmith2014.DD.LevelCounter | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 Rocksmith2014.DD.NoteScorer | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 Rocksmith2014.DD.PhraseCombiner | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 Rocksmith2014.DLCProject | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 Rocksmith2014.EOF.EOFTypes | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 Rocksmith2014.PSARC | 4 | |||||||||||||||||||||||||||||||||||||||
| 17 Rocksmith2014.SNG | 78 | |||||||||||||||||||||||||||||||||||||||
| 18 BeatWriter | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 EventConverter | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Rocksmith2014.Conversion | 6 | |||||||||||||||||||||||||||||||||||||||
| 21 Rocksmith2014.Conversion.ConvertInstrumental | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 Rocksmith2014.Conversion.SngToXml | 1 | 19 | ||||||||||||||||||||||||||||||||||||||
| 23 Rocksmith2014.DLCProject.AggregateGraph | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 24 Rocksmith2014.DLCProject.DLCProjectModule | 3 | 1 | 1 | 6 | ||||||||||||||||||||||||||||||||||||
| 25 Rocksmith2014.DLCProject.GraphItemModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Rocksmith2014.DLCProject.Manifest.AttributesCreation | 6 | 5 | 3 | |||||||||||||||||||||||||||||||||||||
| 27 Rocksmith2014.DLCProject.PackageBuilder | 4 | 1 | 4 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 28 Rocksmith2014.DLCProject.PhraseLevelComparer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 Rocksmith2014.DLCProject.PsarcImportTypes | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Rocksmith2014.DLCProject.PsarcImportUtils | 2 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 Rocksmith2014.DLCProject.XBlock | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 Rocksmith2014.EOF.EOFProjectWriter | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 Rocksmith2014.EOF.ProGuitarWriter | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 34 Rocksmith2014.PSARC.Utils | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 Rocksmith2014.SNG.SNGModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 VocalsWriter | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 Rocksmith2014.Conversion.ConvertVocals | 1 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 Rocksmith2014.Conversion.XmlToSng | 1 | 19 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 Rocksmith2014.Conversion.XmlToSngLevel | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 Rocksmith2014.Conversion.XmlToSngNote | 7 | 1 |
9→4 Rocksmith2014.DD.EntityChooser uses Rocksmith2014.DD.Types✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DD.EntityChooser uses a type in Rocksmith2014.DD.Types.
- The types involved
Rocksmith2014.DD.EntityChooser.EntityChooser→Rocksmith2014.DD.Types.DifficultyRange
- Direction
- Rocksmith2014.DD.EntityChooser uses Rocksmith2014.DD.Types, so a change to Rocksmith2014.DD.Types can break Rocksmith2014.DD.EntityChooser, while a change to Rocksmith2014.DD.EntityChooser can't break Rocksmith2014.DD.Types.
- Position
- Below the diagonal: Rocksmith2014.DD.EntityChooser uses a module listed above it, which is the healthy direction.
9→7 Rocksmith2014.DD.EntityChooser uses Rocksmith2014.XML.Extension✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DD.EntityChooser uses a type in Rocksmith2014.XML.Extension.
- The types involved
Rocksmith2014.DD.EntityChooser.EntityChooser→Rocksmith2014.XML.Extension.XmlEntity
- Direction
- Rocksmith2014.DD.EntityChooser uses Rocksmith2014.XML.Extension, so a change to Rocksmith2014.XML.Extension can break Rocksmith2014.DD.EntityChooser, while a change to Rocksmith2014.DD.EntityChooser can't break Rocksmith2014.XML.Extension.
- Position
- Below the diagonal: Rocksmith2014.DD.EntityChooser uses a module listed above it, which is the healthy direction.
10→3 Rocksmith2014.DD.Generator uses Rocksmith2014.DD.DataExtractor✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DD.Generator uses a type in Rocksmith2014.DD.DataExtractor.
- The types involved
Rocksmith2014.DD.Generator.Generator→Rocksmith2014.DD.DataExtractor.PhraseData
- Direction
- Rocksmith2014.DD.Generator uses Rocksmith2014.DD.DataExtractor, so a change to Rocksmith2014.DD.DataExtractor can break Rocksmith2014.DD.Generator, while a change to Rocksmith2014.DD.Generator can't break Rocksmith2014.DD.DataExtractor.
- Position
- Below the diagonal: Rocksmith2014.DD.Generator uses a module listed above it, which is the healthy direction.
10→4 Rocksmith2014.DD.Generator uses Rocksmith2014.DD.Types✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DD.Generator uses a type in Rocksmith2014.DD.Types.
- The types involved
Rocksmith2014.DD.Generator.Generator→Rocksmith2014.DD.Types.GeneratorConfig
- Direction
- Rocksmith2014.DD.Generator uses Rocksmith2014.DD.Types, so a change to Rocksmith2014.DD.Types can break Rocksmith2014.DD.Generator, while a change to Rocksmith2014.DD.Generator can't break Rocksmith2014.DD.Types.
- Position
- Below the diagonal: Rocksmith2014.DD.Generator uses a module listed above it, which is the healthy direction.
11→3 Rocksmith2014.DD.LevelCounter uses Rocksmith2014.DD.DataExtractor✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DD.LevelCounter uses a type in Rocksmith2014.DD.DataExtractor.
- The types involved
Rocksmith2014.DD.LevelCounter.LevelCounter→Rocksmith2014.DD.DataExtractor.PhraseData
- Direction
- Rocksmith2014.DD.LevelCounter uses Rocksmith2014.DD.DataExtractor, so a change to Rocksmith2014.DD.DataExtractor can break Rocksmith2014.DD.LevelCounter, while a change to Rocksmith2014.DD.LevelCounter can't break Rocksmith2014.DD.DataExtractor.
- Position
- Below the diagonal: Rocksmith2014.DD.LevelCounter uses a module listed above it, which is the healthy direction.
11→4 Rocksmith2014.DD.LevelCounter uses Rocksmith2014.DD.Types✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DD.LevelCounter uses a type in Rocksmith2014.DD.Types.
- The types involved
Rocksmith2014.DD.LevelCounter.LevelCounter→Rocksmith2014.DD.Types.DifficultyRange
- Direction
- Rocksmith2014.DD.LevelCounter uses Rocksmith2014.DD.Types, so a change to Rocksmith2014.DD.Types can break Rocksmith2014.DD.LevelCounter, while a change to Rocksmith2014.DD.LevelCounter can't break Rocksmith2014.DD.Types.
- Position
- Below the diagonal: Rocksmith2014.DD.LevelCounter uses a module listed above it, which is the healthy direction.
12→3 Rocksmith2014.DD.NoteScorer uses Rocksmith2014.DD.DataExtractor✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DD.NoteScorer uses a type in Rocksmith2014.DD.DataExtractor.
- The types involved
Rocksmith2014.DD.NoteScorer.NoteScorer→Rocksmith2014.DD.DataExtractor.PhraseData
- Direction
- Rocksmith2014.DD.NoteScorer uses Rocksmith2014.DD.DataExtractor, so a change to Rocksmith2014.DD.DataExtractor can break Rocksmith2014.DD.NoteScorer, while a change to Rocksmith2014.DD.NoteScorer can't break Rocksmith2014.DD.DataExtractor.
- Position
- Below the diagonal: Rocksmith2014.DD.NoteScorer uses a module listed above it, which is the healthy direction.
12→4 Rocksmith2014.DD.NoteScorer uses Rocksmith2014.DD.Types✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DD.NoteScorer uses a type in Rocksmith2014.DD.Types.
- The types involved
Rocksmith2014.DD.NoteScorer.NoteScorer→Rocksmith2014.DD.Types.DifficultyRange
- Direction
- Rocksmith2014.DD.NoteScorer uses Rocksmith2014.DD.Types, so a change to Rocksmith2014.DD.Types can break Rocksmith2014.DD.NoteScorer, while a change to Rocksmith2014.DD.NoteScorer can't break Rocksmith2014.DD.Types.
- Position
- Below the diagonal: Rocksmith2014.DD.NoteScorer uses a module listed above it, which is the healthy direction.
12→7 Rocksmith2014.DD.NoteScorer uses Rocksmith2014.XML.Extension✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DD.NoteScorer uses a type in Rocksmith2014.XML.Extension.
- The types involved
Rocksmith2014.DD.NoteScorer.NoteScorer→Rocksmith2014.XML.Extension.XmlEntity
- Direction
- Rocksmith2014.DD.NoteScorer uses Rocksmith2014.XML.Extension, so a change to Rocksmith2014.XML.Extension can break Rocksmith2014.DD.NoteScorer, while a change to Rocksmith2014.DD.NoteScorer can't break Rocksmith2014.XML.Extension.
- Position
- Below the diagonal: Rocksmith2014.DD.NoteScorer uses a module listed above it, which is the healthy direction.
13→3 Rocksmith2014.DD.PhraseCombiner uses Rocksmith2014.DD.DataExtractor✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DD.PhraseCombiner uses a type in Rocksmith2014.DD.DataExtractor.
- The types involved
Rocksmith2014.DD.PhraseCombiner.PhraseCombiner→Rocksmith2014.DD.DataExtractor.PhraseData
- Direction
- Rocksmith2014.DD.PhraseCombiner uses Rocksmith2014.DD.DataExtractor, so a change to Rocksmith2014.DD.DataExtractor can break Rocksmith2014.DD.PhraseCombiner, while a change to Rocksmith2014.DD.PhraseCombiner can't break Rocksmith2014.DD.DataExtractor.
- Position
- Below the diagonal: Rocksmith2014.DD.PhraseCombiner uses a module listed above it, which is the healthy direction.
13→4 Rocksmith2014.DD.PhraseCombiner uses Rocksmith2014.DD.Types✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DD.PhraseCombiner uses a type in Rocksmith2014.DD.Types.
- The types involved
Rocksmith2014.DD.PhraseCombiner.PhraseCombiner→Rocksmith2014.DD.Types.GeneratorConfig
- Direction
- Rocksmith2014.DD.PhraseCombiner uses Rocksmith2014.DD.Types, so a change to Rocksmith2014.DD.Types can break Rocksmith2014.DD.PhraseCombiner, while a change to Rocksmith2014.DD.PhraseCombiner can't break Rocksmith2014.DD.Types.
- Position
- Below the diagonal: Rocksmith2014.DD.PhraseCombiner uses a module listed above it, which is the healthy direction.
14→1 Rocksmith2014.DLCProject uses Rocksmith2014.Common✕
- Connections
- 2 pairs of types, where a type in Rocksmith2014.DLCProject uses a type in Rocksmith2014.Common.
- The types involved
Rocksmith2014.DLCProject.DLCProject→Rocksmith2014.Common.AudioFileRocksmith2014.DLCProject.Instrumental→Rocksmith2014.Common.AudioFile
- Direction
- Rocksmith2014.DLCProject uses Rocksmith2014.Common, so a change to Rocksmith2014.Common can break Rocksmith2014.DLCProject, while a change to Rocksmith2014.DLCProject can't break Rocksmith2014.Common.
- Position
- Below the diagonal: Rocksmith2014.DLCProject uses a module listed above it, which is the healthy direction.
14→2 Rocksmith2014.DLCProject uses Rocksmith2014.Common.Manifest✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject uses a type in Rocksmith2014.Common.Manifest.
- The types involved
Rocksmith2014.DLCProject.DLCProject→Rocksmith2014.Common.Manifest.Tone
- Direction
- Rocksmith2014.DLCProject uses Rocksmith2014.Common.Manifest, so a change to Rocksmith2014.Common.Manifest can break Rocksmith2014.DLCProject, while a change to Rocksmith2014.DLCProject can't break Rocksmith2014.Common.Manifest.
- Position
- Below the diagonal: Rocksmith2014.DLCProject uses a module listed above it, which is the healthy direction.
14→5 Rocksmith2014.DLCProject uses Rocksmith2014.DLCProject.ArrangementPropertiesOverride✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject uses a type in Rocksmith2014.DLCProject.ArrangementPropertiesOverride.
- The types involved
Rocksmith2014.DLCProject.Instrumental→Rocksmith2014.DLCProject.ArrangementPropertiesOverride.ArrPropFlags
- Direction
- Rocksmith2014.DLCProject uses Rocksmith2014.DLCProject.ArrangementPropertiesOverride, so a change to Rocksmith2014.DLCProject.ArrangementPropertiesOverride can break Rocksmith2014.DLCProject, while a change to Rocksmith2014.DLCProject can't break Rocksmith2014.DLCProject.ArrangementPropertiesOverride.
- Position
- Below the diagonal: Rocksmith2014.DLCProject uses a module listed above it, which is the healthy direction.
15→6 Rocksmith2014.EOF.EOFTypes uses Rocksmith2014.EOF.ImportTypes✕
- Connections
- 2 pairs of types, where a type in Rocksmith2014.EOF.EOFTypes uses a type in Rocksmith2014.EOF.ImportTypes.
- The types involved
Rocksmith2014.EOF.EOFTypes.EOFTrack→Rocksmith2014.EOF.ImportTypes.ImportedVocalsRocksmith2014.EOF.EOFTypes.ProGuitarTrack→Rocksmith2014.EOF.ImportTypes.ImportedArrangement
- Direction
- Rocksmith2014.EOF.EOFTypes uses Rocksmith2014.EOF.ImportTypes, so a change to Rocksmith2014.EOF.ImportTypes can break Rocksmith2014.EOF.EOFTypes, while a change to Rocksmith2014.EOF.EOFTypes can't break Rocksmith2014.EOF.ImportTypes.
- Position
- Below the diagonal: Rocksmith2014.EOF.EOFTypes uses a module listed above it, which is the healthy direction.
16→1 Rocksmith2014.PSARC uses Rocksmith2014.Common✕
- Connections
- 4 pairs of types, where a type in Rocksmith2014.PSARC uses a type in Rocksmith2014.Common.
- The types involved
Rocksmith2014.PSARC.Entry→Rocksmith2014.Common.IBinaryReaderRocksmith2014.PSARC.Entry→Rocksmith2014.Common.IBinaryWriterRocksmith2014.PSARC.Header→Rocksmith2014.Common.IBinaryReaderRocksmith2014.PSARC.Header→Rocksmith2014.Common.IBinaryWriter
- Direction
- Rocksmith2014.PSARC uses Rocksmith2014.Common, so a change to Rocksmith2014.Common can break Rocksmith2014.PSARC, while a change to Rocksmith2014.PSARC can't break Rocksmith2014.Common.
- Position
- Below the diagonal: Rocksmith2014.PSARC uses a module listed above it, which is the healthy direction.
17→1 Rocksmith2014.SNG uses Rocksmith2014.Common✕
- Connections
- 78 pairs of types, where a type in Rocksmith2014.SNG uses a type in Rocksmith2014.Common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Rocksmith2014.SNG.Action→Rocksmith2014.Common.IBinaryReaderRocksmith2014.SNG.Action→Rocksmith2014.Common.IBinaryWritableRocksmith2014.SNG.Action→Rocksmith2014.Common.IBinaryWriterRocksmith2014.SNG.Anchor→Rocksmith2014.Common.IBinaryReaderRocksmith2014.SNG.Anchor→Rocksmith2014.Common.IBinaryWritableRocksmith2014.SNG.Anchor→Rocksmith2014.Common.IBinaryWriterRocksmith2014.SNG.AnchorExtension→Rocksmith2014.Common.IBinaryReaderRocksmith2014.SNG.AnchorExtension→Rocksmith2014.Common.IBinaryWritableRocksmith2014.SNG.AnchorExtension→Rocksmith2014.Common.IBinaryWriterRocksmith2014.SNG.Beat→Rocksmith2014.Common.IBinaryReaderRocksmith2014.SNG.Beat→Rocksmith2014.Common.IBinaryWritableRocksmith2014.SNG.Beat→Rocksmith2014.Common.IBinaryWriterRocksmith2014.SNG.BendData32→Rocksmith2014.Common.IBinaryReaderRocksmith2014.SNG.BendData32→Rocksmith2014.Common.IBinaryWritableRocksmith2014.SNG.BendData32→Rocksmith2014.Common.IBinaryWriterRocksmith2014.SNG.BendValue→Rocksmith2014.Common.IBinaryReaderRocksmith2014.SNG.BendValue→Rocksmith2014.Common.IBinaryWritableRocksmith2014.SNG.BendValue→Rocksmith2014.Common.IBinaryWriterRocksmith2014.SNG.Chord→Rocksmith2014.Common.IBinaryReaderRocksmith2014.SNG.Chord→Rocksmith2014.Common.IBinaryWritableRocksmith2014.SNG.Chord→Rocksmith2014.Common.IBinaryWriterRocksmith2014.SNG.ChordNotes→Rocksmith2014.Common.IBinaryReaderRocksmith2014.SNG.ChordNotes→Rocksmith2014.Common.IBinaryWritableRocksmith2014.SNG.ChordNotes→Rocksmith2014.Common.IBinaryWriterRocksmith2014.SNG.DNA→Rocksmith2014.Common.IBinaryReader
- Direction
- Rocksmith2014.SNG uses Rocksmith2014.Common, so a change to Rocksmith2014.Common can break Rocksmith2014.SNG, while a change to Rocksmith2014.SNG can't break Rocksmith2014.Common.
- Position
- Below the diagonal: Rocksmith2014.SNG uses a module listed above it, which is the healthy direction.
18→15 BeatWriter uses Rocksmith2014.EOF.EOFTypes✕
- Connections
- 1 pair of types, where a type in BeatWriter uses a type in Rocksmith2014.EOF.EOFTypes.
- The types involved
BeatWriter.BeatWriter→Rocksmith2014.EOF.EOFTypes.EOFEvent
- Direction
- BeatWriter uses Rocksmith2014.EOF.EOFTypes, so a change to Rocksmith2014.EOF.EOFTypes can break BeatWriter, while a change to BeatWriter can't break Rocksmith2014.EOF.EOFTypes.
- Position
- Below the diagonal: BeatWriter uses a module listed above it, which is the healthy direction.
19→15 EventConverter uses Rocksmith2014.EOF.EOFTypes✕
- Connections
- 1 pair of types, where a type in EventConverter uses a type in Rocksmith2014.EOF.EOFTypes.
- The types involved
EventConverter.EventConverter→Rocksmith2014.EOF.EOFTypes.EOFEvent
- Direction
- EventConverter uses Rocksmith2014.EOF.EOFTypes, so a change to Rocksmith2014.EOF.EOFTypes can break EventConverter, while a change to EventConverter can't break Rocksmith2014.EOF.EOFTypes.
- Position
- Below the diagonal: EventConverter uses a module listed above it, which is the healthy direction.
20→17 Rocksmith2014.Conversion uses Rocksmith2014.SNG✕
- Connections
- 6 pairs of types, where a type in Rocksmith2014.Conversion uses a type in Rocksmith2014.SNG.
- The types involved
Rocksmith2014.Conversion.AccuData→Rocksmith2014.SNG.AnchorExtensionRocksmith2014.Conversion.AccuData→Rocksmith2014.SNG.ChordNotesRocksmith2014.Conversion.AccuData→Rocksmith2014.SNG.NoteCountsRocksmith2014.Conversion.AccuData→Rocksmith2014.SNG.SNGRocksmith2014.Conversion.InstrumentalArrangementExtension→Rocksmith2014.SNG.SNGRocksmith2014.Conversion.NoteCountsMutable→Rocksmith2014.SNG.NoteCounts
- Direction
- Rocksmith2014.Conversion uses Rocksmith2014.SNG, so a change to Rocksmith2014.SNG can break Rocksmith2014.Conversion, while a change to Rocksmith2014.Conversion can't break Rocksmith2014.SNG.
- Position
- Below the diagonal: Rocksmith2014.Conversion uses a module listed above it, which is the healthy direction.
21→1 Rocksmith2014.Conversion.ConvertInstrumental uses Rocksmith2014.Common✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.Conversion.ConvertInstrumental uses a type in Rocksmith2014.Common.
- The types involved
Rocksmith2014.Conversion.ConvertInstrumental.ConvertInstrumental→Rocksmith2014.Common.Platform
- Direction
- Rocksmith2014.Conversion.ConvertInstrumental uses Rocksmith2014.Common, so a change to Rocksmith2014.Common can break Rocksmith2014.Conversion.ConvertInstrumental, while a change to Rocksmith2014.Conversion.ConvertInstrumental can't break Rocksmith2014.Common.
- Position
- Below the diagonal: Rocksmith2014.Conversion.ConvertInstrumental uses a module listed above it, which is the healthy direction.
21→2 Rocksmith2014.Conversion.ConvertInstrumental uses Rocksmith2014.Common.Manifest✕
- Connections
- 2 pairs of types, where a type in Rocksmith2014.Conversion.ConvertInstrumental uses a type in Rocksmith2014.Common.Manifest.
- The types involved
Rocksmith2014.Conversion.ConvertInstrumental.ConvertInstrumental→Rocksmith2014.Common.Manifest.ArrangementPropertiesRocksmith2014.Conversion.ConvertInstrumental.ConvertInstrumental→Rocksmith2014.Common.Manifest.Attributes
- Direction
- Rocksmith2014.Conversion.ConvertInstrumental uses Rocksmith2014.Common.Manifest, so a change to Rocksmith2014.Common.Manifest can break Rocksmith2014.Conversion.ConvertInstrumental, while a change to Rocksmith2014.Conversion.ConvertInstrumental can't break Rocksmith2014.Common.Manifest.
- Position
- Below the diagonal: Rocksmith2014.Conversion.ConvertInstrumental uses a module listed above it, which is the healthy direction.
21→17 Rocksmith2014.Conversion.ConvertInstrumental uses Rocksmith2014.SNG✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.Conversion.ConvertInstrumental uses a type in Rocksmith2014.SNG.
- The types involved
Rocksmith2014.Conversion.ConvertInstrumental.ConvertInstrumental→Rocksmith2014.SNG.SNG
- Direction
- Rocksmith2014.Conversion.ConvertInstrumental uses Rocksmith2014.SNG, so a change to Rocksmith2014.SNG can break Rocksmith2014.Conversion.ConvertInstrumental, while a change to Rocksmith2014.Conversion.ConvertInstrumental can't break Rocksmith2014.SNG.
- Position
- Below the diagonal: Rocksmith2014.Conversion.ConvertInstrumental uses a module listed above it, which is the healthy direction.
22→2 Rocksmith2014.Conversion.SngToXml uses Rocksmith2014.Common.Manifest✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.Conversion.SngToXml uses a type in Rocksmith2014.Common.Manifest.
- The types involved
Rocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.Common.Manifest.Attributes
- Direction
- Rocksmith2014.Conversion.SngToXml uses Rocksmith2014.Common.Manifest, so a change to Rocksmith2014.Common.Manifest can break Rocksmith2014.Conversion.SngToXml, while a change to Rocksmith2014.Conversion.SngToXml can't break Rocksmith2014.Common.Manifest.
- Position
- Below the diagonal: Rocksmith2014.Conversion.SngToXml uses a module listed above it, which is the healthy direction.
22→17 Rocksmith2014.Conversion.SngToXml uses Rocksmith2014.SNG✕
- Connections
- 19 pairs of types, where a type in Rocksmith2014.Conversion.SngToXml uses a type in Rocksmith2014.SNG.
- The types involved
Rocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.AnchorRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.BeatRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.BendData32Rocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.BendValueRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.ChordRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.EventRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.FingerPrintRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.LevelRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.NewLinkedDifficultyRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.NoteRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.NoteMaskRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.PhraseRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.PhraseExtraInfoRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.PhraseIterationRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.SNGRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.SectionRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.SymbolDefinitionRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.ToneRocksmith2014.Conversion.SngToXml.SngToXml→Rocksmith2014.SNG.Vocal
- Direction
- Rocksmith2014.Conversion.SngToXml uses Rocksmith2014.SNG, so a change to Rocksmith2014.SNG can break Rocksmith2014.Conversion.SngToXml, while a change to Rocksmith2014.Conversion.SngToXml can't break Rocksmith2014.SNG.
- Position
- Below the diagonal: Rocksmith2014.Conversion.SngToXml uses a module listed above it, which is the healthy direction.
23→1 Rocksmith2014.DLCProject.AggregateGraph uses Rocksmith2014.Common✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.AggregateGraph uses a type in Rocksmith2014.Common.
- The types involved
Rocksmith2014.DLCProject.AggregateGraph.AggregateGraph→Rocksmith2014.Common.Platform
- Direction
- Rocksmith2014.DLCProject.AggregateGraph uses Rocksmith2014.Common, so a change to Rocksmith2014.Common can break Rocksmith2014.DLCProject.AggregateGraph, while a change to Rocksmith2014.DLCProject.AggregateGraph can't break Rocksmith2014.Common.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.AggregateGraph uses a module listed above it, which is the healthy direction.
23→14 Rocksmith2014.DLCProject.AggregateGraph uses Rocksmith2014.DLCProject✕
- Connections
- 2 pairs of types, where a type in Rocksmith2014.DLCProject.AggregateGraph uses a type in Rocksmith2014.DLCProject.
- The types involved
Rocksmith2014.DLCProject.AggregateGraph.AggregateGraph→Rocksmith2014.DLCProject.DLCProjectRocksmith2014.DLCProject.AggregateGraph.Graph→Rocksmith2014.DLCProject.GraphItem
- Direction
- Rocksmith2014.DLCProject.AggregateGraph uses Rocksmith2014.DLCProject, so a change to Rocksmith2014.DLCProject can break Rocksmith2014.DLCProject.AggregateGraph, while a change to Rocksmith2014.DLCProject.AggregateGraph can't break Rocksmith2014.DLCProject.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.AggregateGraph uses a module listed above it, which is the healthy direction.
24→1 Rocksmith2014.DLCProject.DLCProjectModule uses Rocksmith2014.Common✕
- Connections
- 3 pairs of types, where a type in Rocksmith2014.DLCProject.DLCProjectModule uses a type in Rocksmith2014.Common.
- The types involved
Rocksmith2014.DLCProject.DLCProjectModule.DLCProjectModule→Rocksmith2014.Common.AudioFileRocksmith2014.DLCProject.DLCProjectModule.Dto→Rocksmith2014.Common.AudioFileRocksmith2014.DLCProject.DLCProjectModule.InstrumentalDto→Rocksmith2014.Common.AudioFile
- Direction
- Rocksmith2014.DLCProject.DLCProjectModule uses Rocksmith2014.Common, so a change to Rocksmith2014.Common can break Rocksmith2014.DLCProject.DLCProjectModule, while a change to Rocksmith2014.DLCProject.DLCProjectModule can't break Rocksmith2014.Common.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.DLCProjectModule uses a module listed above it, which is the healthy direction.
24→2 Rocksmith2014.DLCProject.DLCProjectModule uses Rocksmith2014.Common.Manifest✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.DLCProjectModule uses a type in Rocksmith2014.Common.Manifest.
- The types involved
Rocksmith2014.DLCProject.DLCProjectModule.Dto→Rocksmith2014.Common.Manifest.ToneDto
- Direction
- Rocksmith2014.DLCProject.DLCProjectModule uses Rocksmith2014.Common.Manifest, so a change to Rocksmith2014.Common.Manifest can break Rocksmith2014.DLCProject.DLCProjectModule, while a change to Rocksmith2014.DLCProject.DLCProjectModule can't break Rocksmith2014.Common.Manifest.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.DLCProjectModule uses a module listed above it, which is the healthy direction.
24→5 Rocksmith2014.DLCProject.DLCProjectModule uses Rocksmith2014.DLCProject.ArrangementPropertiesOverride✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.DLCProjectModule uses a type in Rocksmith2014.DLCProject.ArrangementPropertiesOverride.
- The types involved
Rocksmith2014.DLCProject.DLCProjectModule.InstrumentalDto→Rocksmith2014.DLCProject.ArrangementPropertiesOverride.ArrPropFlags
- Direction
- Rocksmith2014.DLCProject.DLCProjectModule uses Rocksmith2014.DLCProject.ArrangementPropertiesOverride, so a change to Rocksmith2014.DLCProject.ArrangementPropertiesOverride can break Rocksmith2014.DLCProject.DLCProjectModule, while a change to Rocksmith2014.DLCProject.DLCProjectModule can't break Rocksmith2014.DLCProject.ArrangementPropertiesOverride.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.DLCProjectModule uses a module listed above it, which is the healthy direction.
24→14 Rocksmith2014.DLCProject.DLCProjectModule uses Rocksmith2014.DLCProject✕
- Connections
- 6 pairs of types, where a type in Rocksmith2014.DLCProject.DLCProjectModule uses a type in Rocksmith2014.DLCProject.
- The types involved
Rocksmith2014.DLCProject.DLCProjectModule.DLCProjectModule→Rocksmith2014.DLCProject.ArrangementRocksmith2014.DLCProject.DLCProjectModule.DLCProjectModule→Rocksmith2014.DLCProject.DLCProjectRocksmith2014.DLCProject.DLCProjectModule.Dto→Rocksmith2014.DLCProject.SortableStringRocksmith2014.DLCProject.DLCProjectModule.InstrumentalDto→Rocksmith2014.DLCProject.ArrangementNameRocksmith2014.DLCProject.DLCProjectModule.InstrumentalDto→Rocksmith2014.DLCProject.ArrangementPriorityRocksmith2014.DLCProject.DLCProjectModule.InstrumentalDto→Rocksmith2014.DLCProject.RouteMask
- Direction
- Rocksmith2014.DLCProject.DLCProjectModule uses Rocksmith2014.DLCProject, so a change to Rocksmith2014.DLCProject can break Rocksmith2014.DLCProject.DLCProjectModule, while a change to Rocksmith2014.DLCProject.DLCProjectModule can't break Rocksmith2014.DLCProject.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.DLCProjectModule uses a module listed above it, which is the healthy direction.
25→1 Rocksmith2014.DLCProject.GraphItemModule uses Rocksmith2014.Common✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.GraphItemModule uses a type in Rocksmith2014.Common.
- The types involved
Rocksmith2014.DLCProject.GraphItemModule.GraphItemModule→Rocksmith2014.Common.Platform
- Direction
- Rocksmith2014.DLCProject.GraphItemModule uses Rocksmith2014.Common, so a change to Rocksmith2014.Common can break Rocksmith2014.DLCProject.GraphItemModule, while a change to Rocksmith2014.DLCProject.GraphItemModule can't break Rocksmith2014.Common.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.GraphItemModule uses a module listed above it, which is the healthy direction.
25→14 Rocksmith2014.DLCProject.GraphItemModule uses Rocksmith2014.DLCProject✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.GraphItemModule uses a type in Rocksmith2014.DLCProject.
- The types involved
Rocksmith2014.DLCProject.GraphItemModule.GraphItemModule→Rocksmith2014.DLCProject.GraphItem
- Direction
- Rocksmith2014.DLCProject.GraphItemModule uses Rocksmith2014.DLCProject, so a change to Rocksmith2014.DLCProject can break Rocksmith2014.DLCProject.GraphItemModule, while a change to Rocksmith2014.DLCProject.GraphItemModule can't break Rocksmith2014.DLCProject.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.GraphItemModule uses a module listed above it, which is the healthy direction.
26→2 Rocksmith2014.DLCProject.Manifest.AttributesCreation uses Rocksmith2014.Common.Manifest✕
- Connections
- 6 pairs of types, where a type in Rocksmith2014.DLCProject.Manifest.AttributesCreation uses a type in Rocksmith2014.Common.Manifest.
- The types involved
Rocksmith2014.DLCProject.Manifest.AttributesCreation.AttributesCreation→Rocksmith2014.Common.Manifest.ArrangementPropertiesRocksmith2014.DLCProject.Manifest.AttributesCreation.AttributesCreation→Rocksmith2014.Common.Manifest.AttributesRocksmith2014.DLCProject.Manifest.AttributesCreation.AttributesCreation→Rocksmith2014.Common.Manifest.ChordTemplateRocksmith2014.DLCProject.Manifest.AttributesCreation.AttributesCreation→Rocksmith2014.Common.Manifest.PhraseRocksmith2014.DLCProject.Manifest.AttributesCreation.AttributesCreation→Rocksmith2014.Common.Manifest.PhraseIterationRocksmith2014.DLCProject.Manifest.AttributesCreation.AttributesCreation→Rocksmith2014.Common.Manifest.Section
- Direction
- Rocksmith2014.DLCProject.Manifest.AttributesCreation uses Rocksmith2014.Common.Manifest, so a change to Rocksmith2014.Common.Manifest can break Rocksmith2014.DLCProject.Manifest.AttributesCreation, while a change to Rocksmith2014.DLCProject.Manifest.AttributesCreation can't break Rocksmith2014.Common.Manifest.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.Manifest.AttributesCreation uses a module listed above it, which is the healthy direction.
26→14 Rocksmith2014.DLCProject.Manifest.AttributesCreation uses Rocksmith2014.DLCProject✕
- Connections
- 5 pairs of types, where a type in Rocksmith2014.DLCProject.Manifest.AttributesCreation uses a type in Rocksmith2014.DLCProject.
- The types involved
Rocksmith2014.DLCProject.Manifest.AttributesCreation.AttributesConversion→Rocksmith2014.DLCProject.InstrumentalRocksmith2014.DLCProject.Manifest.AttributesCreation.AttributesConversion→Rocksmith2014.DLCProject.VocalsRocksmith2014.DLCProject.Manifest.AttributesCreation.AttributesCreation→Rocksmith2014.DLCProject.ArrangementRocksmith2014.DLCProject.Manifest.AttributesCreation.AttributesCreation→Rocksmith2014.DLCProject.DLCProjectRocksmith2014.DLCProject.Manifest.AttributesCreation.AttributesCreation→Rocksmith2014.DLCProject.Instrumental
- Direction
- Rocksmith2014.DLCProject.Manifest.AttributesCreation uses Rocksmith2014.DLCProject, so a change to Rocksmith2014.DLCProject can break Rocksmith2014.DLCProject.Manifest.AttributesCreation, while a change to Rocksmith2014.DLCProject.Manifest.AttributesCreation can't break Rocksmith2014.DLCProject.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.Manifest.AttributesCreation uses a module listed above it, which is the healthy direction.
26→17 Rocksmith2014.DLCProject.Manifest.AttributesCreation uses Rocksmith2014.SNG✕
- Connections
- 3 pairs of types, where a type in Rocksmith2014.DLCProject.Manifest.AttributesCreation uses a type in Rocksmith2014.SNG.
- The types involved
Rocksmith2014.DLCProject.Manifest.AttributesCreation.AttributesConversion→Rocksmith2014.SNG.SNGRocksmith2014.DLCProject.Manifest.AttributesCreation.AttributesCreation→Rocksmith2014.SNG.NoteRocksmith2014.DLCProject.Manifest.AttributesCreation.AttributesCreation→Rocksmith2014.SNG.SNG
- Direction
- Rocksmith2014.DLCProject.Manifest.AttributesCreation uses Rocksmith2014.SNG, so a change to Rocksmith2014.SNG can break Rocksmith2014.DLCProject.Manifest.AttributesCreation, while a change to Rocksmith2014.DLCProject.Manifest.AttributesCreation can't break Rocksmith2014.SNG.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.Manifest.AttributesCreation uses a module listed above it, which is the healthy direction.
27→1 Rocksmith2014.DLCProject.PackageBuilder uses Rocksmith2014.Common✕
- Connections
- 4 pairs of types, where a type in Rocksmith2014.DLCProject.PackageBuilder uses a type in Rocksmith2014.Common.
- The types involved
Rocksmith2014.DLCProject.PackageBuilder.BuildConfig→Rocksmith2014.Common.AppIdRocksmith2014.DLCProject.PackageBuilder.BuildConfig→Rocksmith2014.Common.PlatformRocksmith2014.DLCProject.PackageBuilder.BuildData→Rocksmith2014.Common.AppIdRocksmith2014.DLCProject.PackageBuilder.PackageBuilder→Rocksmith2014.Common.Platform
- Direction
- Rocksmith2014.DLCProject.PackageBuilder uses Rocksmith2014.Common, so a change to Rocksmith2014.Common can break Rocksmith2014.DLCProject.PackageBuilder, while a change to Rocksmith2014.DLCProject.PackageBuilder can't break Rocksmith2014.Common.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.PackageBuilder uses a module listed above it, which is the healthy direction.
27→4 Rocksmith2014.DLCProject.PackageBuilder uses Rocksmith2014.DD.Types✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.PackageBuilder uses a type in Rocksmith2014.DD.Types.
- The types involved
Rocksmith2014.DLCProject.PackageBuilder.BuildConfig→Rocksmith2014.DD.Types.GeneratorConfig
- Direction
- Rocksmith2014.DLCProject.PackageBuilder uses Rocksmith2014.DD.Types, so a change to Rocksmith2014.DD.Types can break Rocksmith2014.DLCProject.PackageBuilder, while a change to Rocksmith2014.DLCProject.PackageBuilder can't break Rocksmith2014.DD.Types.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.PackageBuilder uses a module listed above it, which is the healthy direction.
27→14 Rocksmith2014.DLCProject.PackageBuilder uses Rocksmith2014.DLCProject✕
- Connections
- 4 pairs of types, where a type in Rocksmith2014.DLCProject.PackageBuilder uses a type in Rocksmith2014.DLCProject.
- The types involved
Rocksmith2014.DLCProject.PackageBuilder.PackageBuilder→Rocksmith2014.DLCProject.ArrangementRocksmith2014.DLCProject.PackageBuilder.PackageBuilder→Rocksmith2014.DLCProject.ArrangementIdRocksmith2014.DLCProject.PackageBuilder.PackageBuilder→Rocksmith2014.DLCProject.DLCProjectRocksmith2014.DLCProject.PackageBuilder.PackageBuilder→Rocksmith2014.DLCProject.Instrumental
- Direction
- Rocksmith2014.DLCProject.PackageBuilder uses Rocksmith2014.DLCProject, so a change to Rocksmith2014.DLCProject can break Rocksmith2014.DLCProject.PackageBuilder, while a change to Rocksmith2014.DLCProject.PackageBuilder can't break Rocksmith2014.DLCProject.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.PackageBuilder uses a module listed above it, which is the healthy direction.
27→16 Rocksmith2014.DLCProject.PackageBuilder uses Rocksmith2014.PSARC✕
- Connections
- 2 pairs of types, where a type in Rocksmith2014.DLCProject.PackageBuilder uses a type in Rocksmith2014.PSARC.
- The types involved
Rocksmith2014.DLCProject.PackageBuilder.BuildData→Rocksmith2014.PSARC.DisposableList`1Rocksmith2014.DLCProject.PackageBuilder.PackageBuilder→Rocksmith2014.PSARC.DisposableList`1
- Direction
- Rocksmith2014.DLCProject.PackageBuilder uses Rocksmith2014.PSARC, so a change to Rocksmith2014.PSARC can break Rocksmith2014.DLCProject.PackageBuilder, while a change to Rocksmith2014.DLCProject.PackageBuilder can't break Rocksmith2014.PSARC.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.PackageBuilder uses a module listed above it, which is the healthy direction.
27→17 Rocksmith2014.DLCProject.PackageBuilder uses Rocksmith2014.SNG✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.PackageBuilder uses a type in Rocksmith2014.SNG.
- The types involved
Rocksmith2014.DLCProject.PackageBuilder.PackageBuilder→Rocksmith2014.SNG.SNG
- Direction
- Rocksmith2014.DLCProject.PackageBuilder uses Rocksmith2014.SNG, so a change to Rocksmith2014.SNG can break Rocksmith2014.DLCProject.PackageBuilder, while a change to Rocksmith2014.DLCProject.PackageBuilder can't break Rocksmith2014.SNG.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.PackageBuilder uses a module listed above it, which is the healthy direction.
28→14 Rocksmith2014.DLCProject.PhraseLevelComparer uses Rocksmith2014.DLCProject✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.PhraseLevelComparer uses a type in Rocksmith2014.DLCProject.
- The types involved
Rocksmith2014.DLCProject.PhraseLevelComparer.PhraseLevelComparer→Rocksmith2014.DLCProject.ArrangementId
- Direction
- Rocksmith2014.DLCProject.PhraseLevelComparer uses Rocksmith2014.DLCProject, so a change to Rocksmith2014.DLCProject can break Rocksmith2014.DLCProject.PhraseLevelComparer, while a change to Rocksmith2014.DLCProject.PhraseLevelComparer can't break Rocksmith2014.DLCProject.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.PhraseLevelComparer uses a module listed above it, which is the healthy direction.
28→17 Rocksmith2014.DLCProject.PhraseLevelComparer uses Rocksmith2014.SNG✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.PhraseLevelComparer uses a type in Rocksmith2014.SNG.
- The types involved
Rocksmith2014.DLCProject.PhraseLevelComparer.PhraseLevelComparer→Rocksmith2014.SNG.Phrase
- Direction
- Rocksmith2014.DLCProject.PhraseLevelComparer uses Rocksmith2014.SNG, so a change to Rocksmith2014.SNG can break Rocksmith2014.DLCProject.PhraseLevelComparer, while a change to Rocksmith2014.DLCProject.PhraseLevelComparer can't break Rocksmith2014.SNG.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.PhraseLevelComparer uses a module listed above it, which is the healthy direction.
29→1 Rocksmith2014.DLCProject.PsarcImportTypes uses Rocksmith2014.Common✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.PsarcImportTypes uses a type in Rocksmith2014.Common.
- The types involved
Rocksmith2014.DLCProject.PsarcImportTypes.PsarcImportResult→Rocksmith2014.Common.AppId
- Direction
- Rocksmith2014.DLCProject.PsarcImportTypes uses Rocksmith2014.Common, so a change to Rocksmith2014.Common can break Rocksmith2014.DLCProject.PsarcImportTypes, while a change to Rocksmith2014.DLCProject.PsarcImportTypes can't break Rocksmith2014.Common.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.PsarcImportTypes uses a module listed above it, which is the healthy direction.
29→14 Rocksmith2014.DLCProject.PsarcImportTypes uses Rocksmith2014.DLCProject✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.PsarcImportTypes uses a type in Rocksmith2014.DLCProject.
- The types involved
Rocksmith2014.DLCProject.PsarcImportTypes.PsarcImportResult→Rocksmith2014.DLCProject.DLCProject
- Direction
- Rocksmith2014.DLCProject.PsarcImportTypes uses Rocksmith2014.DLCProject, so a change to Rocksmith2014.DLCProject can break Rocksmith2014.DLCProject.PsarcImportTypes, while a change to Rocksmith2014.DLCProject.PsarcImportTypes can't break Rocksmith2014.DLCProject.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.PsarcImportTypes uses a module listed above it, which is the healthy direction.
30→1 Rocksmith2014.DLCProject.PsarcImportUtils uses Rocksmith2014.Common✕
- Connections
- 2 pairs of types, where a type in Rocksmith2014.DLCProject.PsarcImportUtils uses a type in Rocksmith2014.Common.
- The types involved
Rocksmith2014.DLCProject.PsarcImportUtils.PsarcImportUtils→Rocksmith2014.Common.AudioFileRocksmith2014.DLCProject.PsarcImportUtils.PsarcImportUtils→Rocksmith2014.Common.Platform
- Direction
- Rocksmith2014.DLCProject.PsarcImportUtils uses Rocksmith2014.Common, so a change to Rocksmith2014.Common can break Rocksmith2014.DLCProject.PsarcImportUtils, while a change to Rocksmith2014.DLCProject.PsarcImportUtils can't break Rocksmith2014.Common.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.PsarcImportUtils uses a module listed above it, which is the healthy direction.
30→2 Rocksmith2014.DLCProject.PsarcImportUtils uses Rocksmith2014.Common.Manifest✕
- Connections
- 3 pairs of types, where a type in Rocksmith2014.DLCProject.PsarcImportUtils uses a type in Rocksmith2014.Common.Manifest.
- The types involved
Rocksmith2014.DLCProject.PsarcImportUtils.PsarcImportUtils→Rocksmith2014.Common.Manifest.AttributesRocksmith2014.DLCProject.PsarcImportUtils.PsarcImportUtils→Rocksmith2014.Common.Manifest.ToneRocksmith2014.DLCProject.PsarcImportUtils.PsarcImportUtils→Rocksmith2014.Common.Manifest.ToneDto
- Direction
- Rocksmith2014.DLCProject.PsarcImportUtils uses Rocksmith2014.Common.Manifest, so a change to Rocksmith2014.Common.Manifest can break Rocksmith2014.DLCProject.PsarcImportUtils, while a change to Rocksmith2014.DLCProject.PsarcImportUtils can't break Rocksmith2014.Common.Manifest.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.PsarcImportUtils uses a module listed above it, which is the healthy direction.
30→16 Rocksmith2014.DLCProject.PsarcImportUtils uses Rocksmith2014.PSARC✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.PsarcImportUtils uses a type in Rocksmith2014.PSARC.
- The types involved
Rocksmith2014.DLCProject.PsarcImportUtils.PsarcImportUtils→Rocksmith2014.PSARC.PSARC
- Direction
- Rocksmith2014.DLCProject.PsarcImportUtils uses Rocksmith2014.PSARC, so a change to Rocksmith2014.PSARC can break Rocksmith2014.DLCProject.PsarcImportUtils, while a change to Rocksmith2014.DLCProject.PsarcImportUtils can't break Rocksmith2014.PSARC.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.PsarcImportUtils uses a module listed above it, which is the healthy direction.
30→17 Rocksmith2014.DLCProject.PsarcImportUtils uses Rocksmith2014.SNG✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.PsarcImportUtils uses a type in Rocksmith2014.SNG.
- The types involved
Rocksmith2014.DLCProject.PsarcImportUtils.PsarcImportUtils→Rocksmith2014.SNG.SNG
- Direction
- Rocksmith2014.DLCProject.PsarcImportUtils uses Rocksmith2014.SNG, so a change to Rocksmith2014.SNG can break Rocksmith2014.DLCProject.PsarcImportUtils, while a change to Rocksmith2014.DLCProject.PsarcImportUtils can't break Rocksmith2014.SNG.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.PsarcImportUtils uses a module listed above it, which is the healthy direction.
31→1 Rocksmith2014.DLCProject.XBlock uses Rocksmith2014.Common✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.XBlock uses a type in Rocksmith2014.Common.
- The types involved
Rocksmith2014.DLCProject.XBlock.XBlock→Rocksmith2014.Common.Platform
- Direction
- Rocksmith2014.DLCProject.XBlock uses Rocksmith2014.Common, so a change to Rocksmith2014.Common can break Rocksmith2014.DLCProject.XBlock, while a change to Rocksmith2014.DLCProject.XBlock can't break Rocksmith2014.Common.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.XBlock uses a module listed above it, which is the healthy direction.
31→14 Rocksmith2014.DLCProject.XBlock uses Rocksmith2014.DLCProject✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.DLCProject.XBlock uses a type in Rocksmith2014.DLCProject.
- The types involved
Rocksmith2014.DLCProject.XBlock.XBlock→Rocksmith2014.DLCProject.DLCProject
- Direction
- Rocksmith2014.DLCProject.XBlock uses Rocksmith2014.DLCProject, so a change to Rocksmith2014.DLCProject can break Rocksmith2014.DLCProject.XBlock, while a change to Rocksmith2014.DLCProject.XBlock can't break Rocksmith2014.DLCProject.
- Position
- Below the diagonal: Rocksmith2014.DLCProject.XBlock uses a module listed above it, which is the healthy direction.
32→6 Rocksmith2014.EOF.EOFProjectWriter uses Rocksmith2014.EOF.ImportTypes✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.EOF.EOFProjectWriter uses a type in Rocksmith2014.EOF.ImportTypes.
- The types involved
Rocksmith2014.EOF.EOFProjectWriter.EOFProjectWriter→Rocksmith2014.EOF.ImportTypes.EOFProTracks
- Direction
- Rocksmith2014.EOF.EOFProjectWriter uses Rocksmith2014.EOF.ImportTypes, so a change to Rocksmith2014.EOF.ImportTypes can break Rocksmith2014.EOF.EOFProjectWriter, while a change to Rocksmith2014.EOF.EOFProjectWriter can't break Rocksmith2014.EOF.ImportTypes.
- Position
- Below the diagonal: Rocksmith2014.EOF.EOFProjectWriter uses a module listed above it, which is the healthy direction.
32→15 Rocksmith2014.EOF.EOFProjectWriter uses Rocksmith2014.EOF.EOFTypes✕
- Connections
- 2 pairs of types, where a type in Rocksmith2014.EOF.EOFProjectWriter uses a type in Rocksmith2014.EOF.EOFTypes.
- The types involved
Rocksmith2014.EOF.EOFProjectWriter.EOFProjectWriter→Rocksmith2014.EOF.EOFTypes.EOFEventRocksmith2014.EOF.EOFProjectWriter.EOFProjectWriter→Rocksmith2014.EOF.EOFTypes.EOFTrack
- Direction
- Rocksmith2014.EOF.EOFProjectWriter uses Rocksmith2014.EOF.EOFTypes, so a change to Rocksmith2014.EOF.EOFTypes can break Rocksmith2014.EOF.EOFProjectWriter, while a change to Rocksmith2014.EOF.EOFProjectWriter can't break Rocksmith2014.EOF.EOFTypes.
- Position
- Below the diagonal: Rocksmith2014.EOF.EOFProjectWriter uses a module listed above it, which is the healthy direction.
33→6 Rocksmith2014.EOF.ProGuitarWriter uses Rocksmith2014.EOF.ImportTypes✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.EOF.ProGuitarWriter uses a type in Rocksmith2014.EOF.ImportTypes.
- The types involved
Rocksmith2014.EOF.ProGuitarWriter.ProGuitarWriter→Rocksmith2014.EOF.ImportTypes.ImportedArrangement
- Direction
- Rocksmith2014.EOF.ProGuitarWriter uses Rocksmith2014.EOF.ImportTypes, so a change to Rocksmith2014.EOF.ImportTypes can break Rocksmith2014.EOF.ProGuitarWriter, while a change to Rocksmith2014.EOF.ProGuitarWriter can't break Rocksmith2014.EOF.ImportTypes.
- Position
- Below the diagonal: Rocksmith2014.EOF.ProGuitarWriter uses a module listed above it, which is the healthy direction.
33→15 Rocksmith2014.EOF.ProGuitarWriter uses Rocksmith2014.EOF.EOFTypes✕
- Connections
- 3 pairs of types, where a type in Rocksmith2014.EOF.ProGuitarWriter uses a type in Rocksmith2014.EOF.EOFTypes.
- The types involved
Rocksmith2014.EOF.ProGuitarWriter.ProGuitarWriter→Rocksmith2014.EOF.EOFTypes.EOFNoteRocksmith2014.EOF.ProGuitarWriter.ProGuitarWriter→Rocksmith2014.EOF.EOFTypes.EOFSectionRocksmith2014.EOF.ProGuitarWriter.ProGuitarWriter→Rocksmith2014.EOF.EOFTypes.HsResult
- Direction
- Rocksmith2014.EOF.ProGuitarWriter uses Rocksmith2014.EOF.EOFTypes, so a change to Rocksmith2014.EOF.EOFTypes can break Rocksmith2014.EOF.ProGuitarWriter, while a change to Rocksmith2014.EOF.ProGuitarWriter can't break Rocksmith2014.EOF.EOFTypes.
- Position
- Below the diagonal: Rocksmith2014.EOF.ProGuitarWriter uses a module listed above it, which is the healthy direction.
34→1 Rocksmith2014.PSARC.Utils uses Rocksmith2014.Common✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.PSARC.Utils uses a type in Rocksmith2014.Common.
- The types involved
Rocksmith2014.PSARC.Utils.Utils→Rocksmith2014.Common.IBinaryReader
- Direction
- Rocksmith2014.PSARC.Utils uses Rocksmith2014.Common, so a change to Rocksmith2014.Common can break Rocksmith2014.PSARC.Utils, while a change to Rocksmith2014.PSARC.Utils can't break Rocksmith2014.Common.
- Position
- Below the diagonal: Rocksmith2014.PSARC.Utils uses a module listed above it, which is the healthy direction.
34→16 Rocksmith2014.PSARC.Utils uses Rocksmith2014.PSARC✕
- Connections
- 2 pairs of types, where a type in Rocksmith2014.PSARC.Utils uses a type in Rocksmith2014.PSARC.
- The types involved
Rocksmith2014.PSARC.Utils.Utils→Rocksmith2014.PSARC.HeaderRocksmith2014.PSARC.Utils.Utils→Rocksmith2014.PSARC.NamedEntry
- Direction
- Rocksmith2014.PSARC.Utils uses Rocksmith2014.PSARC, so a change to Rocksmith2014.PSARC can break Rocksmith2014.PSARC.Utils, while a change to Rocksmith2014.PSARC.Utils can't break Rocksmith2014.PSARC.
- Position
- Below the diagonal: Rocksmith2014.PSARC.Utils uses a module listed above it, which is the healthy direction.
35→1 Rocksmith2014.SNG.SNGModule uses Rocksmith2014.Common✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.SNG.SNGModule uses a type in Rocksmith2014.Common.
- The types involved
Rocksmith2014.SNG.SNGModule.SNGModule→Rocksmith2014.Common.Platform
- Direction
- Rocksmith2014.SNG.SNGModule uses Rocksmith2014.Common, so a change to Rocksmith2014.Common can break Rocksmith2014.SNG.SNGModule, while a change to Rocksmith2014.SNG.SNGModule can't break Rocksmith2014.Common.
- Position
- Below the diagonal: Rocksmith2014.SNG.SNGModule uses a module listed above it, which is the healthy direction.
35→17 Rocksmith2014.SNG.SNGModule uses Rocksmith2014.SNG✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.SNG.SNGModule uses a type in Rocksmith2014.SNG.
- The types involved
Rocksmith2014.SNG.SNGModule.SNGModule→Rocksmith2014.SNG.SNG
- Direction
- Rocksmith2014.SNG.SNGModule uses Rocksmith2014.SNG, so a change to Rocksmith2014.SNG can break Rocksmith2014.SNG.SNGModule, while a change to Rocksmith2014.SNG.SNGModule can't break Rocksmith2014.SNG.
- Position
- Below the diagonal: Rocksmith2014.SNG.SNGModule uses a module listed above it, which is the healthy direction.
36→6 VocalsWriter uses Rocksmith2014.EOF.ImportTypes✕
- Connections
- 1 pair of types, where a type in VocalsWriter uses a type in Rocksmith2014.EOF.ImportTypes.
- The types involved
VocalsWriter.VocalsWriter→Rocksmith2014.EOF.ImportTypes.ImportedVocals
- Direction
- VocalsWriter uses Rocksmith2014.EOF.ImportTypes, so a change to Rocksmith2014.EOF.ImportTypes can break VocalsWriter, while a change to VocalsWriter can't break Rocksmith2014.EOF.ImportTypes.
- Position
- Below the diagonal: VocalsWriter uses a module listed above it, which is the healthy direction.
36→15 VocalsWriter uses Rocksmith2014.EOF.EOFTypes✕
- Connections
- 1 pair of types, where a type in VocalsWriter uses a type in Rocksmith2014.EOF.EOFTypes.
- The types involved
VocalsWriter.VocalsWriter→Rocksmith2014.EOF.EOFTypes.NoteGroup
- Direction
- VocalsWriter uses Rocksmith2014.EOF.EOFTypes, so a change to Rocksmith2014.EOF.EOFTypes can break VocalsWriter, while a change to VocalsWriter can't break Rocksmith2014.EOF.EOFTypes.
- Position
- Below the diagonal: VocalsWriter uses a module listed above it, which is the healthy direction.
37→1 Rocksmith2014.Conversion.ConvertVocals uses Rocksmith2014.Common✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.Conversion.ConvertVocals uses a type in Rocksmith2014.Common.
- The types involved
Rocksmith2014.Conversion.ConvertVocals.ConvertVocals→Rocksmith2014.Common.Platform
- Direction
- Rocksmith2014.Conversion.ConvertVocals uses Rocksmith2014.Common, so a change to Rocksmith2014.Common can break Rocksmith2014.Conversion.ConvertVocals, while a change to Rocksmith2014.Conversion.ConvertVocals can't break Rocksmith2014.Common.
- Position
- Below the diagonal: Rocksmith2014.Conversion.ConvertVocals uses a module listed above it, which is the healthy direction.
37→17 Rocksmith2014.Conversion.ConvertVocals uses Rocksmith2014.SNG✕
- Connections
- 5 pairs of types, where a type in Rocksmith2014.Conversion.ConvertVocals uses a type in Rocksmith2014.SNG.
- The types involved
Rocksmith2014.Conversion.ConvertVocals.ConvertVocals→Rocksmith2014.SNG.SNGRocksmith2014.Conversion.ConvertVocals.ConvertVocals→Rocksmith2014.SNG.SymbolDefinitionRocksmith2014.Conversion.ConvertVocals.ConvertVocals→Rocksmith2014.SNG.SymbolsHeaderRocksmith2014.Conversion.ConvertVocals.ConvertVocals→Rocksmith2014.SNG.SymbolsTextureRocksmith2014.Conversion.ConvertVocals.ConvertVocals→Rocksmith2014.SNG.Vocal
- Direction
- Rocksmith2014.Conversion.ConvertVocals uses Rocksmith2014.SNG, so a change to Rocksmith2014.SNG can break Rocksmith2014.Conversion.ConvertVocals, while a change to Rocksmith2014.Conversion.ConvertVocals can't break Rocksmith2014.SNG.
- Position
- Below the diagonal: Rocksmith2014.Conversion.ConvertVocals uses a module listed above it, which is the healthy direction.
37→20 Rocksmith2014.Conversion.ConvertVocals uses Rocksmith2014.Conversion✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.Conversion.ConvertVocals uses a type in Rocksmith2014.Conversion.
- The types involved
Rocksmith2014.Conversion.ConvertVocals.ConvertVocals→Rocksmith2014.Conversion.FontOption
- Direction
- Rocksmith2014.Conversion.ConvertVocals uses Rocksmith2014.Conversion, so a change to Rocksmith2014.Conversion can break Rocksmith2014.Conversion.ConvertVocals, while a change to Rocksmith2014.Conversion.ConvertVocals can't break Rocksmith2014.Conversion.
- Position
- Below the diagonal: Rocksmith2014.Conversion.ConvertVocals uses a module listed above it, which is the healthy direction.
38→7 Rocksmith2014.Conversion.XmlToSng uses Rocksmith2014.XML.Extension✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.Conversion.XmlToSng uses a type in Rocksmith2014.XML.Extension.
- The types involved
Rocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.XML.Extension.XmlEntity
- Direction
- Rocksmith2014.Conversion.XmlToSng uses Rocksmith2014.XML.Extension, so a change to Rocksmith2014.XML.Extension can break Rocksmith2014.Conversion.XmlToSng, while a change to Rocksmith2014.Conversion.XmlToSng can't break Rocksmith2014.XML.Extension.
- Position
- Below the diagonal: Rocksmith2014.Conversion.XmlToSng uses a module listed above it, which is the healthy direction.
38→17 Rocksmith2014.Conversion.XmlToSng uses Rocksmith2014.SNG✕
- Connections
- 19 pairs of types, where a type in Rocksmith2014.Conversion.XmlToSng uses a type in Rocksmith2014.SNG.
- The types involved
Rocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.AnchorRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.BeatRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.BendValueRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.ChordRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.DNARocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.EventRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.FingerPrintRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.LevelRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.MetaDataRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.NewLinkedDifficultyRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.NoteRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.PhraseRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.PhraseExtraInfoRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.PhraseIterationRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.SNGRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.SectionRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.SymbolDefinitionRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.ToneRocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.SNG.Vocal
- Direction
- Rocksmith2014.Conversion.XmlToSng uses Rocksmith2014.SNG, so a change to Rocksmith2014.SNG can break Rocksmith2014.Conversion.XmlToSng, while a change to Rocksmith2014.Conversion.XmlToSng can't break Rocksmith2014.SNG.
- Position
- Below the diagonal: Rocksmith2014.Conversion.XmlToSng uses a module listed above it, which is the healthy direction.
38→20 Rocksmith2014.Conversion.XmlToSng uses Rocksmith2014.Conversion✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.Conversion.XmlToSng uses a type in Rocksmith2014.Conversion.
- The types involved
Rocksmith2014.Conversion.XmlToSng.XmlToSng→Rocksmith2014.Conversion.AccuData
- Direction
- Rocksmith2014.Conversion.XmlToSng uses Rocksmith2014.Conversion, so a change to Rocksmith2014.Conversion can break Rocksmith2014.Conversion.XmlToSng, while a change to Rocksmith2014.Conversion.XmlToSng can't break Rocksmith2014.Conversion.
- Position
- Below the diagonal: Rocksmith2014.Conversion.XmlToSng uses a module listed above it, which is the healthy direction.
39→17 Rocksmith2014.Conversion.XmlToSngLevel uses Rocksmith2014.SNG✕
- Connections
- 3 pairs of types, where a type in Rocksmith2014.Conversion.XmlToSngLevel uses a type in Rocksmith2014.SNG.
- The types involved
Rocksmith2014.Conversion.XmlToSngLevel.XmlToSngLevel→Rocksmith2014.SNG.LevelRocksmith2014.Conversion.XmlToSngLevel.XmlToSngLevel→Rocksmith2014.SNG.PhraseExtraInfoRocksmith2014.Conversion.XmlToSngLevel.XmlToSngLevel→Rocksmith2014.SNG.SNG
- Direction
- Rocksmith2014.Conversion.XmlToSngLevel uses Rocksmith2014.SNG, so a change to Rocksmith2014.SNG can break Rocksmith2014.Conversion.XmlToSngLevel, while a change to Rocksmith2014.Conversion.XmlToSngLevel can't break Rocksmith2014.SNG.
- Position
- Below the diagonal: Rocksmith2014.Conversion.XmlToSngLevel uses a module listed above it, which is the healthy direction.
39→20 Rocksmith2014.Conversion.XmlToSngLevel uses Rocksmith2014.Conversion✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.Conversion.XmlToSngLevel uses a type in Rocksmith2014.Conversion.
- The types involved
Rocksmith2014.Conversion.XmlToSngLevel.XmlToSngLevel→Rocksmith2014.Conversion.AccuData
- Direction
- Rocksmith2014.Conversion.XmlToSngLevel uses Rocksmith2014.Conversion, so a change to Rocksmith2014.Conversion can break Rocksmith2014.Conversion.XmlToSngLevel, while a change to Rocksmith2014.Conversion.XmlToSngLevel can't break Rocksmith2014.Conversion.
- Position
- Below the diagonal: Rocksmith2014.Conversion.XmlToSngLevel uses a module listed above it, which is the healthy direction.
40→17 Rocksmith2014.Conversion.XmlToSngNote uses Rocksmith2014.SNG✕
- Connections
- 7 pairs of types, where a type in Rocksmith2014.Conversion.XmlToSngNote uses a type in Rocksmith2014.SNG.
- The types involved
Rocksmith2014.Conversion.XmlToSngNote.XmlToSngNote→Rocksmith2014.SNG.BeatRocksmith2014.Conversion.XmlToSngNote.XmlToSngNote→Rocksmith2014.SNG.BendData32Rocksmith2014.Conversion.XmlToSngNote.XmlToSngNote→Rocksmith2014.SNG.ChordRocksmith2014.Conversion.XmlToSngNote.XmlToSngNote→Rocksmith2014.SNG.FingerPrintRocksmith2014.Conversion.XmlToSngNote.XmlToSngNote→Rocksmith2014.SNG.NoteRocksmith2014.Conversion.XmlToSngNote.XmlToSngNote→Rocksmith2014.SNG.NoteMaskRocksmith2014.Conversion.XmlToSngNote.XmlToSngNote→Rocksmith2014.SNG.SNG
- Direction
- Rocksmith2014.Conversion.XmlToSngNote uses Rocksmith2014.SNG, so a change to Rocksmith2014.SNG can break Rocksmith2014.Conversion.XmlToSngNote, while a change to Rocksmith2014.Conversion.XmlToSngNote can't break Rocksmith2014.SNG.
- Position
- Below the diagonal: Rocksmith2014.Conversion.XmlToSngNote uses a module listed above it, which is the healthy direction.
40→20 Rocksmith2014.Conversion.XmlToSngNote uses Rocksmith2014.Conversion✕
- Connections
- 1 pair of types, where a type in Rocksmith2014.Conversion.XmlToSngNote uses a type in Rocksmith2014.Conversion.
- The types involved
Rocksmith2014.Conversion.XmlToSngNote.XmlToSngNote→Rocksmith2014.Conversion.AccuData
- Direction
- Rocksmith2014.Conversion.XmlToSngNote uses Rocksmith2014.Conversion, so a change to Rocksmith2014.Conversion can break Rocksmith2014.Conversion.XmlToSngNote, while a change to Rocksmith2014.Conversion.XmlToSngNote can't break Rocksmith2014.Conversion.
- Position
- Below the diagonal: Rocksmith2014.Conversion.XmlToSngNote uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 8 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
| A07:2025 — Authentication Failures | 7 | High / Critical |
Roadmap
Top priorities: Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED; Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. | +4.4 pts | Low | Secrets (history) |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +3.6 pts | Low | Documentation Quality |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +2.8 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). | +1.6 pts | Low | Secrets (history) |
| 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. | +3.1 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.4 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.4 pts | Low | Supply-chain Provenance & Signing |
| Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible. | +2.8 pts | Medium | Deployment & Rollback |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/Rocksmith2014.Common/BinaryReaders.fs | 4.9 | Mixed | Code Duplication: Duplicated block (11 lines × 2) |
| src/Rocksmith2014.XML/Note.cs | 5.1 | Mixed | Cyclomatic Complexity: Note.WriteXml (cyclomatic 46) |
| src/Rocksmith2014.XML/ChordTemplate.cs | 5.5 | Mixed | Cyclomatic Complexity: ChordTemplate.WriteXml (cyclomatic 25) |
| REDACTED | 5.7 | Mixed | Secrets (history): REDACTED: REDACTED |
| src/Rocksmith2014.XML/Chord.cs | 5.9 | Mixed | Cyclomatic Complexity: Chord.WriteXml (cyclomatic 18) |
| src/Rocksmith2014.XML/InstrumentalArrangement.cs | 6.0 | Mixed | Explicit Debt: HackComment |
| src/Rocksmith2014.Conversion/XmlToSngNote.fs | 7.0 | Mixed | Cyclomatic Complexity: XmlToSngNote.createMaskForNote (cyclomatic 25) |
| src/Rocksmith2014.Common/BinaryWriters.fs | 7.0 | Mixed | Code Duplication: Duplicated block (6 lines × 2) |
| src/Rocksmith2014.XML.Processing/Checkers/InstrumentalChecker.fs | 7.1 | Mixed | Cyclomatic Complexity: InstrumentalChecker.checkNotes (cyclomatic 51) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| src/Rocksmith2014.DLCProject/Manifest/Techniques.fs | 7.4 | Mixed | Cyclomatic Complexity: Techniques.getTechniques (cyclomatic 49) |
| src/Rocksmith2014.XML.Processing/PhraseGenerator.fs | 7.4 | Mixed | Cyclomatic Complexity: Helpers.findGoodPhraseTime (cyclomatic 23) |
| samples/DLCBuilder/Modals/AbnormalExitMessage.fs | 7.4 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
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
Watchdog 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. 64 of 64 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 64 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, 129 of 141 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 23 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 94 test source file(s) (.fs) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- D12 Dependency Hygiene — not measured this run — Watchdog 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 2405 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 3 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/Rocksmith2014.SNG/Rocksmith2014.SNG.fsproj' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 1 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (25,981 lines, 87% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D23 Boundary Type-Coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (29,892 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D39 IL Efficiency — not measured this run — Watchdog 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. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog 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. Subject: a native UI project (samples/DLCBuilder/Styles.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
18 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was InstrumentalChecker.checkNotes at 51. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Types.issueCode at 43 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Rocksmith2014.XML.Processing/Types.fs (Types.issueCode at 43), src/Rocksmith2014.DLCProject/Manifest/AttributesCreation.fs (AttributesCreation.getSectionUIName at 33), src/Rocksmith2014.DLCProject/StringValidator.fs (StringValidator.tryGetOfficialArtistNameSortValue at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 18 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with InstrumentalChecker.checkNotes (cyclomatic 51), Techniques.getTechniques (cyclomatic 49), Note.WriteXml (cyclomatic 46). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 18 together lifts Cyclomatic Complexity from 7.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
33 method(s) exceeded the cognitive complexity threshold of 15; the worst was Techniques.getTechniques at 89.
What to do
- Bring the 33 bodies over 15 down to 15 or less in Cognitive Complexity — start with Techniques.getTechniques (cognitive 89), EntityChooser.choose (cognitive 88), InstrumentalChecker.checkNotes (cognitive 85). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 33 together lifts Cognitive Complexity from 5.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with InstrumentalArrangement.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
34 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 14 of the 36 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 11 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with BinaryWriters.fs (8), Cryptography.fs, Techniques.fs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 5 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with BinaryReaders.fs (3), BinaryWriters.fs, XmlToSngNote.fs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with InstrumentalDetails.fs (2), Chord.cs, Program.fs. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
3 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
2 of 39 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with BinaryReaders.fs (2). — One of this dimension's main actionable groups (2 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D8 · Code Coverage
Line coverage 64.3% — 6 file(s) below 50% · 9 method(s) over the CRAP-30 risk line.
What to do
- Resolve the 6 Low coverage finding(s) in Code Coverage — start with LinkedDiff.cs, NewLinkedDiff.cs, PhraseProperty.cs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 CRAP 260 finding(s) in Code Coverage — start with Note.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 CRAP 169 finding(s) in Code Coverage — start with InstrumentalArrangement.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
23 test methods: 23 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 23 tests. Measured on the C# suite only — at least 94 test source file(s) (.fs) went unread, so its test quality is unmeasured and is not in these counts.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 198 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 34 direct `PackageReference`(s), and 164 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
1 deducted debt markers + unmeasured dead symbols across 3953 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (87% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with InstrumentalArrangement.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 1 document(s) read across 3 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 3 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
94 % of calls cross a namespace and 2 % go through an interface, but 17 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
132 finding(s): 0 critical, 132 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 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 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)
8 finding(s): 0 critical, 6 high, 2 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 92 of the 186 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 38 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
- `InstrumentalArrangement` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (UseAbridgedXml; e.g. `UseAbridgedXml` at line 111). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rocksmith2014.XML/InstrumentalArrangement.cs:16
What to do
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). — src/Rocksmith2014.XML/Utils.cs:18
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 3 of 3 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 1149 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Directory.Packages.props:6
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- No release automation was found in CI — neither a deploy stage (Helm/Kubernetes/compose manifests, an orchestrated rollout) nor a publish job that ships the built artifact. Releases appear to be run by hand, which is slower, less repeatable and harder to reverse.
What to do
- Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 0/2 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×2) — src/Rocksmith2014.XML/InstrumentalArrangement.cs:283, src/Rocksmith2014.XML/InstrumentalArrangement.cs:335
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 79% | Strong | Solid. |
| Architecture | 68% | Adequate — gated by D26, AX2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 54% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 51% | Adequate — gated by P3, P4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 48% | Weak — gated by D28, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 55 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.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
- D24 Comment Value — D24 reads C# and Visual Basic comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 107 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one; a Domain/Aggregates/ValueObjects layer; a domain structure with no aggregate, domain event or strongly-typed id in it: a CRUD / clean-architecture model, measured but not claimed as DDD; a top-level samples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
- 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
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's F# source (11 module(s), 155 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage data present for 91 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 12 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 115 finding(s)
- Duplicated block (5 lines × 2) src/Rocksmith2014.Common/BinaryWriters.fs:18
- Duplicated block (5 lines × 2) src/Rocksmith2014.Common/BinaryWriters.fs:24
- Duplicated block (5 lines × 2) src/Rocksmith2014.Common/BinaryWriters.fs:30
- Duplicated block (5 lines × 2) src/Rocksmith2014.Common/BinaryWriters.fs:36
- Duplicated block (5 lines × 2) src/Rocksmith2014.Common/BinaryWriters.fs:42
- Duplicated block (5 lines × 2) src/Rocksmith2014.Common/BinaryWriters.fs:48
- Duplicated block (5 lines × 2) src/Rocksmith2014.Common/BinaryWriters.fs:54
- Duplicated block (5 lines × 2) src/Rocksmith2014.Common/BinaryWriters.fs:60
- Duplicated block (5 lines × 2) src/Rocksmith2014.SNG/Cryptography.fs:38
- Duplicated block (5 lines × 2) src/Rocksmith2014.DLCProject/Manifest/Techniques.fs:9
- Duplicated block (5 lines × 2) samples/DLCBuilder/Controls/FixedComboBox.fs:39
- Low coverage: src/Rocksmith2014.XML/LinkedDiff.cs src/Rocksmith2014.XML/LinkedDiff.cs:1
- Low coverage: src/Rocksmith2014.XML/NewLinkedDiff.cs src/Rocksmith2014.XML/NewLinkedDiff.cs:1
- Low coverage: src/Rocksmith2014.XML/PhraseProperty.cs src/Rocksmith2014.XML/PhraseProperty.cs:1
- Low coverage: src/Rocksmith2014.XML/RSXmlComment.cs src/Rocksmith2014.XML/RSXmlComment.cs:1
- Low coverage: src/Rocksmith2014.XML/ShowLight.cs src/Rocksmith2014.XML/ShowLight.cs:1
- Low coverage: src/Rocksmith2014.XML/ShowLights.cs src/Rocksmith2014.XML/ShowLights.cs:1
- Duplicated block (6 lines × 2) src/Rocksmith2014.Common/BinaryReaders.fs:11
- Duplicated block (6 lines × 2) src/Rocksmith2014.Common/BinaryWriters.fs:11
- Duplicated block (6 lines × 2) src/Rocksmith2014.Conversion/XmlToSngNote.fs:39
- Duplicated block (6 lines × 2) src/Rocksmith2014.Common/BinaryReaders.fs:26
- Duplicated block (6 lines × 2) src/Rocksmith2014.Common/BinaryReaders.fs:46
- Duplicated block (9 lines × 2) src/Rocksmith2014.XML/Chord.cs:296
- Duplicated block (9 lines × 2) samples/DLCBuilder/Views/InstrumentalDetails.fs:300
- Duplicated block (9 lines × 2) samples/DLCBuilder/Views/InstrumentalDetails.fs:325
- Duplicated block (9 lines × 2) samples/Testing/Program.fs:64
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/Rocksmith2014.XML/BendValue.cs:1
- Members sharing a duplicated core (4 members, 50+ identical tokens) samples/DLCBuilder/Modals/AbnormalExitMessage.fs:1
- Low cohesion: LittleEndianBinaryReader (LCOM4 11) src/Rocksmith2014.Common/BinaryReaders.fs:10
- Low cohesion: BigEndianBinaryReader (LCOM4 11) src/Rocksmith2014.Common/BinaryReaders.fs:84
- Async method without CancellationToken: GenerateTranscriptionTrack src/Rocksmith2014.XML/InstrumentalArrangement.cs:283
- Async method without CancellationToken: RemoveDD src/Rocksmith2014.XML/InstrumentalArrangement.cs:335
- Process-global static state: InstrumentalArrangement src/Rocksmith2014.XML/InstrumentalArrangement.cs:16
- InstrumentalChecker.checkNotes (cyclomatic 51) src/Rocksmith2014.XML.Processing/Checkers/InstrumentalChecker.fs:142
- Techniques.getTechniques (cyclomatic 49) src/Rocksmith2014.DLCProject/Manifest/Techniques.fs:103
- Note.WriteXml (cyclomatic 46) src/Rocksmith2014.XML/Note.cs:534
- EntityChooser.choose (cyclomatic 46) src/Rocksmith2014.DD/EntityChooser.fs:194
- InstrumentalChecker.checkChords (cyclomatic 39) src/Rocksmith2014.XML.Processing/Checkers/InstrumentalChecker.fs:329
- Note.ReadXml (cyclomatic 31) src/Rocksmith2014.XML/Note.cs:432
- ChordTemplate.WriteXml (cyclomatic 25) src/Rocksmith2014.XML/ChordTemplate.cs:185
- XmlToSngNote.createMaskForNote (cyclomatic 25) src/Rocksmith2014.Conversion/XmlToSngNote.fs:55
- ArrangementPropertiesOverride.fromArrangementProperties (cyclomatic 24) src/Rocksmith2014.DLCProject/ArrangementPropertiesOverride.fs:36
- MetaData.Read (cyclomatic 23) src/Rocksmith2014.XML/MetaData.cs:108
- Helpers.findGoodPhraseTime (cyclomatic 23) src/Rocksmith2014.XML.Processing/PhraseGenerator.fs:147
- XmlToSngNote.createMaskForChordNote (cyclomatic 20) src/Rocksmith2014.Conversion/XmlToSngNote.fs:24
- CustomEvents.improve (cyclomatic 19) src/Rocksmith2014.XML.Processing/Improvers/CustomEvents.fs:9
- Chord.WriteXml (cyclomatic 18) src/Rocksmith2014.XML/Chord.cs:291
- InstrumentalArrangement.FixHighDensity (cyclomatic 18) src/Rocksmith2014.XML/InstrumentalArrangement.cs:200
- ArrangementModule.fromFile (cyclomatic 18) src/Rocksmith2014.DLCProject/Arrangement.fs:187
- XmlToSngNote.convertNote (cyclomatic 18) src/Rocksmith2014.Conversion/XmlToSngNote.fs:184
- ProGuitarWriter.writeProTrack (cyclomatic 18) src/Rocksmith2014.EOF/ProGuitarWriter.fs:102
- HackComment src/Rocksmith2014.XML/InstrumentalArrangement.cs:267
- Techniques.getTechniques (cognitive 89) src/Rocksmith2014.DLCProject/Manifest/Techniques.fs:103
- EntityChooser.choose (cognitive 88) src/Rocksmith2014.DD/EntityChooser.fs:194
- InstrumentalChecker.checkNotes (cognitive 85) src/Rocksmith2014.XML.Processing/Checkers/InstrumentalChecker.fs:142
- InstrumentalChecker.checkChords (cognitive 69) src/Rocksmith2014.XML.Processing/Checkers/InstrumentalChecker.fs:329
- XmlToSngNote.createMaskForNote (cognitive 61) src/Rocksmith2014.Conversion/XmlToSngNote.fs:55
- Helpers.findGoodPhraseTime (cognitive 55) src/Rocksmith2014.XML.Processing/PhraseGenerator.fs:147
- XmlToSngNote.createMaskForChordNote (cognitive 49) src/Rocksmith2014.Conversion/XmlToSngNote.fs:24
- Note.WriteXml (cognitive 45) src/Rocksmith2014.XML/Note.cs:534
- InstrumentalArrangement.FixHighDensity (cognitive 43) src/Rocksmith2014.XML/InstrumentalArrangement.cs:200
- SngToXml.convertNoteMask (cognitive 41) src/Rocksmith2014.Conversion/SngToXml.fs:112
- XmlToSngNote.convertNote (cognitive 35) src/Rocksmith2014.Conversion/XmlToSngNote.fs:184
- BasicFixes.fixLinkNexts (cognitive 35) src/Rocksmith2014.XML.Processing/Improvers/BasicFixes.fs:42
- XmlToSngNote.createMaskForChord (cognitive 32) src/Rocksmith2014.Conversion/XmlToSngNote.fs:90
- CustomEvents.improve (cognitive 29) src/Rocksmith2014.XML.Processing/Improvers/CustomEvents.fs:9
- ArrangementModule.fromFile (cognitive 27) src/Rocksmith2014.DLCProject/Arrangement.fs:187
- UnncessaryNoteRemover.improve (cognitive 27) src/Rocksmith2014.XML.Processing/Improvers/UnnecessaryNoteRemover.fs:6
- ChordTemplate.WriteXml (cognitive 24) src/Rocksmith2014.XML/ChordTemplate.cs:185
- Helpers.createPhrasesAndSections (cognitive 24) src/Rocksmith2014.XML.Processing/PhraseGenerator.fs:230
- ArrangementPropertiesOverride.fromArrangementProperties (cognitive 23) src/Rocksmith2014.DLCProject/ArrangementPropertiesOverride.fs:36
- HandShapeAdjuster.shortenHandshapes (cognitive 23) src/Rocksmith2014.XML.Processing/Improvers/HandShapeAdjuster.fs:90
- InstrumentalChecker.checkLinkNext (cognitive 22) src/Rocksmith2014.XML.Processing/Checkers/InstrumentalChecker.fs:72
- SngToXml.convertChordMask (cognitive 20) src/Rocksmith2014.Conversion/SngToXml.fs:160
- ProGuitarWriter.writeProTrack (cognitive 20) src/Rocksmith2014.EOF/ProGuitarWriter.fs:102
- Chord.WriteXml (cognitive 18) src/Rocksmith2014.XML/Chord.cs:291
- HandShapeAdjuster.lengthenHandshapes (cognitive 18) src/Rocksmith2014.XML.Processing/Improvers/HandShapeAdjuster.fs:29
- EOFFixes.fixPhraseStartAnchors (cognitive 18) src/Rocksmith2014.XML.Processing/Improvers/EOFFixes.fs:61
- TechNotes.combineTechNotes (cognitive 18) src/Rocksmith2014.EOF/TechNotes.fs:41
- InstrumentalArrangement.RemoveDD (cognitive 17) src/Rocksmith2014.XML/InstrumentalArrangement.cs:335
- Generator.generateLevels (cognitive 17) src/Rocksmith2014.DD/Generator.fs:6
- AudioFader.NAudio.Wave.ISampleProvider.Read (cognitive 16) src/Rocksmith2014.Audio/AudioFader.fs:16
- ToneModule.getPedal (cognitive 16) REDACTED:102
- PhraseCombiner.combineSamePhrases (cognitive 16) src/Rocksmith2014.DD/PhraseCombiner.fs:95
- InstrumentalChecker.checkPhrases (cognitive 16) src/Rocksmith2014.XML.Processing/Checkers/InstrumentalChecker.fs:528
- MethodTooLong: InstrumentalArrangement.ReadXml src/Rocksmith2014.XML/InstrumentalArrangement.cs:403
- REDACTED
- Duplicated block (25–28 lines × 2) src/Rocksmith2014.DLCProject/DLCProject.fs:252
- Duplicated block (17–19 lines × 2) src/Rocksmith2014.DLCProject/SoundBank/SoundBank.fs:126
- Duplicated block (15 lines × 4) src/Rocksmith2014.XML/BendValue.cs:38
- Duplicated block (11 lines × 2) src/Rocksmith2014.Common/BinaryReaders.fs:72
- Duplicated block (7 lines × 2) src/Rocksmith2014.DLCProject/Manifest/AttributesCreation.fs:257
- Duplicated block (20 lines × 2) samples/DLCBuilder.Domain/Utils.fs:40
- Duplicated block (19 lines × 2) samples/DLCBuilder/Modals/AbnormalExitMessage.fs:3
- Duplicated block (16 lines × 2) samples/DLCBuilder/Controls/FixedAutoCompleteBox.fs:33
- Duplicated block (13 lines × 4) samples/DLCBuilder/Modals/AbnormalExitMessage.fs:12
- Duplicated block (9–11 lines × 2) samples/Testing/Program.fs:41
- Duplicated block (8–9 lines × 2) samples/DLCBuilder/Controls/FuncUIExtensions.fs:17
- Duplicated block (7–8 lines × 2) samples/DLCBuilder.ToneCollection/Database.fs:107
- Duplicated block (8 lines × 2) samples/DLCBuilder/Controls/FixedAutoCompleteBox.fs:51
- Duplicated block (14 lines × 2) samples/DLCBuilder/Views/Main.fs:153
- CRAP 260: Note.WriteXml src/Rocksmith2014.XML/Note.cs:534
- CRAP 169: InstrumentalArrangement.ReadXml src/Rocksmith2014.XML/InstrumentalArrangement.cs:403
- CRAP 128: Note.ReadXml src/Rocksmith2014.XML/Note.cs:432
- CRAP 90: ChordTemplate.WriteXml src/Rocksmith2014.XML/ChordTemplate.cs:185
- CRAP 52: Chord.WriteXml src/Rocksmith2014.XML/Chord.cs:291
- CRAP 48: RSXmlComment.CommentType.get src/Rocksmith2014.XML/RSXmlComment.cs:55
- CRAP 47: InstrumentalArrangement.FixHighDensity src/Rocksmith2014.XML/InstrumentalArrangement.cs:200
- CRAP 43: ChordTemplate.ReadXml src/Rocksmith2014.XML/ChordTemplate.cs:126
- No deployment automation
Minor — 14 finding(s)
- Documentation: no build, run or usage example README.md:1
- Projects may be oversized for their cohesion
- Scattered collaborators
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Commented-out code src/Rocksmith2014.XML/Utils.cs:18
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:6
- No dependency-update automation Directory.Packages.props:6
- Not all async methods take a CancellationToken
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-75b1bf788db14507a535836f9c83cabe/history.json --exit-code 0 --source . | 219 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-75b1bf788db14507a535836f9c83cabe/tree.json --exit-code 0 --source . | 45 | 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/watchdog-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 . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |