Executive summary
ramsey/uuid meets our standard for production. It scores 78 out of 100 and is rated Strong, and its one critical finding is a security problem in its automatic dependency updates.
Maturity, at 69, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 8 points.
One automatic update takes new releases before a bad one can be spotted. Setting a waiting period for automatic updates would close this risk.
The product code is 8,549 lines, about €32,000 to rebuild.
If Maturity rose from 69 to 70, the lowest score rated Strong, the score would rise from 78 to about 78.
New since the last survey: 7 findings
- Code Duplication · Edited copy of a member (28 corresponding lines) src/Converter/Time/GenericTimeConverter.php
- Code Duplication · Edited copy of a member (12 corresponding lines) src/DeprecatedUuidMethodsTrait.php
- Code Duplication · Edited copy of a member (11 corresponding lines) src/Nonstandard/UuidV6.php
- Code Duplication · Edited copy of a member (13 corresponding lines) src/Converter/Time/GenericTimeConverter.php
- Code Duplication · Edited copy of a member (20 corresponding lines) src/Provider/Dce/SystemDceSecurityProvider.php
- Code Duplication · Edited copy of a member (4 corresponding lines) src/Rfc4122/Validator.php
- Code Duplication · Edited copy of a member (8 corresponding lines) src/Guid/Fields.php
Fixed since the last survey: 26 findings
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: watchdog-privileged-trigger-secret-to-unpinned-action REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: watchdog-secret-into-unpinned-action REDACTED
- Static Analysis (SAST) · Medium: watchdog-floating-toolchain-version-in-setup-action REDACTED
- Static Analysis (SAST) · Medium: watchdog-floating-toolchain-version-in-setup-action REDACTED
- Static Analysis (SAST) · Medium: watchdog-floating-toolchain-version-in-setup-action REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing · Unpinned build actions
Rebuild cost: about €32,000 · Estimate
| Cost to rebuild | €10,000 to €53,000, for 174 to 553 hours of work, about 0.2 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 | ×1.2 at a score of 78. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 8,549 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 Ramsey.Uuid.Exception | 2 Ramsey.Uuid.Fields | 3 Ramsey.Uuid.Type | 4 Ramsey.Uuid.Validator | 5 docs | 6 Ramsey.Uuid.Codec | 7 Ramsey.Uuid.Converter | 8 Ramsey.Uuid.Math | 9 Ramsey.Uuid.Provider | 10 src | 11 Ramsey.Uuid.Converter.Number | 12 Ramsey.Uuid.Converter.Time | 13 Ramsey.Uuid.Generator | 14 Ramsey.Uuid.Nonstandard | 15 Ramsey.Uuid.Provider.Dce | 16 Ramsey.Uuid.Provider.Node | 17 Ramsey.Uuid.Provider.Time | 18 Ramsey.Uuid.Rfc4122 | 19 Ramsey.Uuid.Builder | 20 Ramsey.Uuid | 21 Ramsey.Uuid.Guid | 22 Ramsey.Uuid.Lazy |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Ramsey.Uuid.Exception | ||||||||||||||||||||||
| 2 Ramsey.Uuid.Fields | ||||||||||||||||||||||
| 3 Ramsey.Uuid.Type | ||||||||||||||||||||||
| 4 Ramsey.Uuid.Validator | ||||||||||||||||||||||
| 5 docs | ||||||||||||||||||||||
| 6 Ramsey.Uuid.Codec | 1 | 5 | ||||||||||||||||||||
| 7 Ramsey.Uuid.Converter | 2 | |||||||||||||||||||||
| 8 Ramsey.Uuid.Math | 6 | |||||||||||||||||||||
| 9 Ramsey.Uuid.Provider | 3 | |||||||||||||||||||||
| 10 src | 2 | |||||||||||||||||||||
| 11 Ramsey.Uuid.Converter.Number | 2 | 1 | ||||||||||||||||||||
| 12 Ramsey.Uuid.Converter.Time | 8 | 4 | 3 | |||||||||||||||||||
| 13 Ramsey.Uuid.Generator | 4 | 4 | 5 | 3 | ||||||||||||||||||
| 14 Ramsey.Uuid.Nonstandard | 1 | 3 | 6 | 5 | 1 | 3 | ||||||||||||||||
| 15 Ramsey.Uuid.Provider.Dce | 1 | 1 | ||||||||||||||||||||
| 16 Ramsey.Uuid.Provider.Node | 4 | 4 | ||||||||||||||||||||
| 17 Ramsey.Uuid.Provider.Time | 2 | 2 | ||||||||||||||||||||
| 18 Ramsey.Uuid.Rfc4122 | 1 | 3 | 1 | 8 | 16 | 1 | 1 | 11 | ||||||||||||||
| 19 Ramsey.Uuid.Builder | 3 | 2 | 1 | 3 | ||||||||||||||||||
| 20 Ramsey.Uuid | 2 | 8 | 3 | 3 | 8 | 1 | 4 | 8 | 1 | 2 | ||||||||||||
| 21 Ramsey.Uuid.Guid | 1 | 2 | 4 | 1 | 1 | 2 | ||||||||||||||||
| 22 Ramsey.Uuid.Lazy | 1 | 2 | 1 | 2 | 1 |
6→19 Ramsey.Uuid.Codec uses Ramsey.Uuid.Builder part of a loop✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Codec uses a type in Ramsey.Uuid.Builder.
- The types involved
Ramsey.Uuid.Codec.StringCodec→Ramsey.Uuid.Builder.UuidBuilderInterface
- Direction
- Ramsey.Uuid.Codec uses Ramsey.Uuid.Builder, so a change to Ramsey.Uuid.Builder can break Ramsey.Uuid.Codec, while a change to Ramsey.Uuid.Codec can't break Ramsey.Uuid.Builder.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→20 Ramsey.Uuid.Codec uses Ramsey.Uuid part of a loop✕
- Connections
- 5 pairs of types, where a type in Ramsey.Uuid.Codec uses a type in Ramsey.Uuid.
- The types involved
Ramsey.Uuid.Codec.CodecInterface→Ramsey.Uuid.UuidInterfaceRamsey.Uuid.Codec.GuidStringCodec→Ramsey.Uuid.UuidInterfaceRamsey.Uuid.Codec.OrderedTimeCodec→Ramsey.Uuid.UuidInterfaceRamsey.Uuid.Codec.StringCodec→Ramsey.Uuid.UuidInterfaceRamsey.Uuid.Codec.TimestampFirstCombCodec→Ramsey.Uuid.UuidInterface
- Direction
- Ramsey.Uuid.Codec uses Ramsey.Uuid, so a change to Ramsey.Uuid can break Ramsey.Uuid.Codec, while a change to Ramsey.Uuid.Codec can't break Ramsey.Uuid.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→3 Ramsey.Uuid.Converter uses Ramsey.Uuid.Type✕
- Connections
- 2 pairs of types, where a type in Ramsey.Uuid.Converter uses a type in Ramsey.Uuid.Type.
- The types involved
Ramsey.Uuid.Converter.TimeConverterInterface→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Converter.TimeConverterInterface→Ramsey.Uuid.Type.Time
- Direction
- Ramsey.Uuid.Converter uses Ramsey.Uuid.Type, so a change to Ramsey.Uuid.Type can break Ramsey.Uuid.Converter, while a change to Ramsey.Uuid.Converter can't break Ramsey.Uuid.Type.
- Position
- Below the diagonal: Ramsey.Uuid.Converter uses a module listed above it, which is the healthy direction.
8→3 Ramsey.Uuid.Math uses Ramsey.Uuid.Type✕
- Connections
- 6 pairs of types, where a type in Ramsey.Uuid.Math uses a type in Ramsey.Uuid.Type.
- The types involved
Ramsey.Uuid.Math.BrickMathCalculator→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Math.BrickMathCalculator→Ramsey.Uuid.Type.IntegerRamsey.Uuid.Math.BrickMathCalculator→Ramsey.Uuid.Type.NumberInterfaceRamsey.Uuid.Math.CalculatorInterface→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Math.CalculatorInterface→Ramsey.Uuid.Type.IntegerRamsey.Uuid.Math.CalculatorInterface→Ramsey.Uuid.Type.NumberInterface
- Direction
- Ramsey.Uuid.Math uses Ramsey.Uuid.Type, so a change to Ramsey.Uuid.Type can break Ramsey.Uuid.Math, while a change to Ramsey.Uuid.Math can't break Ramsey.Uuid.Type.
- Position
- Below the diagonal: Ramsey.Uuid.Math uses a module listed above it, which is the healthy direction.
9→3 Ramsey.Uuid.Provider uses Ramsey.Uuid.Type✕
- Connections
- 3 pairs of types, where a type in Ramsey.Uuid.Provider uses a type in Ramsey.Uuid.Type.
- The types involved
Ramsey.Uuid.Provider.DceSecurityProviderInterface→Ramsey.Uuid.Type.IntegerRamsey.Uuid.Provider.NodeProviderInterface→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Provider.TimeProviderInterface→Ramsey.Uuid.Type.Time
- Direction
- Ramsey.Uuid.Provider uses Ramsey.Uuid.Type, so a change to Ramsey.Uuid.Type can break Ramsey.Uuid.Provider, while a change to Ramsey.Uuid.Provider can't break Ramsey.Uuid.Type.
- Position
- Below the diagonal: Ramsey.Uuid.Provider uses a module listed above it, which is the healthy direction.
10→3 src uses Ramsey.Uuid.Type✕
- Connections
- 2 pairs of types, where a type in src uses a type in Ramsey.Uuid.Type.
- The types involved
src.functions→Ramsey.Uuid.Type.Hexadecimalsrc.functions→Ramsey.Uuid.Type.Integer
- Direction
- src uses Ramsey.Uuid.Type, so a change to Ramsey.Uuid.Type can break src, while a change to src can't break Ramsey.Uuid.Type.
- Position
- Below the diagonal: src uses a module listed above it, which is the healthy direction.
11→7 Ramsey.Uuid.Converter.Number uses Ramsey.Uuid.Converter✕
- Connections
- 2 pairs of types, where a type in Ramsey.Uuid.Converter.Number uses a type in Ramsey.Uuid.Converter.
- The types involved
Ramsey.Uuid.Converter.Number.BigNumberConverter→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Converter.Number.GenericNumberConverter→Ramsey.Uuid.Converter.NumberConverterInterface
- Direction
- Ramsey.Uuid.Converter.Number uses Ramsey.Uuid.Converter, so a change to Ramsey.Uuid.Converter can break Ramsey.Uuid.Converter.Number, while a change to Ramsey.Uuid.Converter.Number can't break Ramsey.Uuid.Converter.
- Position
- Below the diagonal: Ramsey.Uuid.Converter.Number uses a module listed above it, which is the healthy direction.
11→8 Ramsey.Uuid.Converter.Number uses Ramsey.Uuid.Math✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Converter.Number uses a type in Ramsey.Uuid.Math.
- The types involved
Ramsey.Uuid.Converter.Number.GenericNumberConverter→Ramsey.Uuid.Math.CalculatorInterface
- Direction
- Ramsey.Uuid.Converter.Number uses Ramsey.Uuid.Math, so a change to Ramsey.Uuid.Math can break Ramsey.Uuid.Converter.Number, while a change to Ramsey.Uuid.Converter.Number can't break Ramsey.Uuid.Math.
- Position
- Below the diagonal: Ramsey.Uuid.Converter.Number uses a module listed above it, which is the healthy direction.
12→3 Ramsey.Uuid.Converter.Time uses Ramsey.Uuid.Type✕
- Connections
- 8 pairs of types, where a type in Ramsey.Uuid.Converter.Time uses a type in Ramsey.Uuid.Type.
- The types involved
Ramsey.Uuid.Converter.Time.BigNumberTimeConverter→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Converter.Time.BigNumberTimeConverter→Ramsey.Uuid.Type.TimeRamsey.Uuid.Converter.Time.GenericTimeConverter→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Converter.Time.GenericTimeConverter→Ramsey.Uuid.Type.TimeRamsey.Uuid.Converter.Time.PhpTimeConverter→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Converter.Time.PhpTimeConverter→Ramsey.Uuid.Type.TimeRamsey.Uuid.Converter.Time.UnixTimeConverter→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Converter.Time.UnixTimeConverter→Ramsey.Uuid.Type.Time
- Direction
- Ramsey.Uuid.Converter.Time uses Ramsey.Uuid.Type, so a change to Ramsey.Uuid.Type can break Ramsey.Uuid.Converter.Time, while a change to Ramsey.Uuid.Converter.Time can't break Ramsey.Uuid.Type.
- Position
- Below the diagonal: Ramsey.Uuid.Converter.Time uses a module listed above it, which is the healthy direction.
12→7 Ramsey.Uuid.Converter.Time uses Ramsey.Uuid.Converter✕
- Connections
- 4 pairs of types, where a type in Ramsey.Uuid.Converter.Time uses a type in Ramsey.Uuid.Converter.
- The types involved
Ramsey.Uuid.Converter.Time.BigNumberTimeConverter→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Converter.Time.GenericTimeConverter→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Converter.Time.PhpTimeConverter→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Converter.Time.UnixTimeConverter→Ramsey.Uuid.Converter.TimeConverterInterface
- Direction
- Ramsey.Uuid.Converter.Time uses Ramsey.Uuid.Converter, so a change to Ramsey.Uuid.Converter can break Ramsey.Uuid.Converter.Time, while a change to Ramsey.Uuid.Converter.Time can't break Ramsey.Uuid.Converter.
- Position
- Below the diagonal: Ramsey.Uuid.Converter.Time uses a module listed above it, which is the healthy direction.
12→8 Ramsey.Uuid.Converter.Time uses Ramsey.Uuid.Math✕
- Connections
- 3 pairs of types, where a type in Ramsey.Uuid.Converter.Time uses a type in Ramsey.Uuid.Math.
- The types involved
Ramsey.Uuid.Converter.Time.GenericTimeConverter→Ramsey.Uuid.Math.CalculatorInterfaceRamsey.Uuid.Converter.Time.PhpTimeConverter→Ramsey.Uuid.Math.CalculatorInterfaceRamsey.Uuid.Converter.Time.UnixTimeConverter→Ramsey.Uuid.Math.CalculatorInterface
- Direction
- Ramsey.Uuid.Converter.Time uses Ramsey.Uuid.Math, so a change to Ramsey.Uuid.Math can break Ramsey.Uuid.Converter.Time, while a change to Ramsey.Uuid.Converter.Time can't break Ramsey.Uuid.Math.
- Position
- Below the diagonal: Ramsey.Uuid.Converter.Time uses a module listed above it, which is the healthy direction.
13→3 Ramsey.Uuid.Generator uses Ramsey.Uuid.Type✕
- Connections
- 4 pairs of types, where a type in Ramsey.Uuid.Generator uses a type in Ramsey.Uuid.Type.
- The types involved
Ramsey.Uuid.Generator.DceSecurityGenerator→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Generator.DceSecurityGenerator→Ramsey.Uuid.Type.IntegerRamsey.Uuid.Generator.DceSecurityGeneratorInterface→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Generator.DceSecurityGeneratorInterface→Ramsey.Uuid.Type.Integer
- Direction
- Ramsey.Uuid.Generator uses Ramsey.Uuid.Type, so a change to Ramsey.Uuid.Type can break Ramsey.Uuid.Generator, while a change to Ramsey.Uuid.Generator can't break Ramsey.Uuid.Type.
- Position
- Below the diagonal: Ramsey.Uuid.Generator uses a module listed above it, which is the healthy direction.
13→7 Ramsey.Uuid.Generator uses Ramsey.Uuid.Converter✕
- Connections
- 4 pairs of types, where a type in Ramsey.Uuid.Generator uses a type in Ramsey.Uuid.Converter.
- The types involved
Ramsey.Uuid.Generator.CombGenerator→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Generator.DceSecurityGenerator→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Generator.DefaultTimeGenerator→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Generator.TimeGeneratorFactory→Ramsey.Uuid.Converter.TimeConverterInterface
- Direction
- Ramsey.Uuid.Generator uses Ramsey.Uuid.Converter, so a change to Ramsey.Uuid.Converter can break Ramsey.Uuid.Generator, while a change to Ramsey.Uuid.Generator can't break Ramsey.Uuid.Converter.
- Position
- Below the diagonal: Ramsey.Uuid.Generator uses a module listed above it, which is the healthy direction.
13→9 Ramsey.Uuid.Generator uses Ramsey.Uuid.Provider✕
- Connections
- 5 pairs of types, where a type in Ramsey.Uuid.Generator uses a type in Ramsey.Uuid.Provider.
- The types involved
Ramsey.Uuid.Generator.DceSecurityGenerator→Ramsey.Uuid.Provider.DceSecurityProviderInterfaceRamsey.Uuid.Generator.DefaultTimeGenerator→Ramsey.Uuid.Provider.NodeProviderInterfaceRamsey.Uuid.Generator.DefaultTimeGenerator→Ramsey.Uuid.Provider.TimeProviderInterfaceRamsey.Uuid.Generator.TimeGeneratorFactory→Ramsey.Uuid.Provider.NodeProviderInterfaceRamsey.Uuid.Generator.TimeGeneratorFactory→Ramsey.Uuid.Provider.TimeProviderInterface
- Direction
- Ramsey.Uuid.Generator uses Ramsey.Uuid.Provider, so a change to Ramsey.Uuid.Provider can break Ramsey.Uuid.Generator, while a change to Ramsey.Uuid.Generator can't break Ramsey.Uuid.Provider.
- Position
- Below the diagonal: Ramsey.Uuid.Generator uses a module listed above it, which is the healthy direction.
13→20 Ramsey.Uuid.Generator uses Ramsey.Uuid part of a loop✕
- Connections
- 3 pairs of types, where a type in Ramsey.Uuid.Generator uses a type in Ramsey.Uuid.
- The types involved
Ramsey.Uuid.Generator.DefaultNameGenerator→Ramsey.Uuid.UuidInterfaceRamsey.Uuid.Generator.NameGeneratorInterface→Ramsey.Uuid.UuidInterfaceRamsey.Uuid.Generator.PeclUuidNameGenerator→Ramsey.Uuid.UuidInterface
- Direction
- Ramsey.Uuid.Generator uses Ramsey.Uuid, so a change to Ramsey.Uuid can break Ramsey.Uuid.Generator, while a change to Ramsey.Uuid.Generator can't break Ramsey.Uuid.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→3 Ramsey.Uuid.Nonstandard uses Ramsey.Uuid.Type✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Nonstandard uses a type in Ramsey.Uuid.Type.
- The types involved
Ramsey.Uuid.Nonstandard.Fields→Ramsey.Uuid.Type.Hexadecimal
- Direction
- Ramsey.Uuid.Nonstandard uses Ramsey.Uuid.Type, so a change to Ramsey.Uuid.Type can break Ramsey.Uuid.Nonstandard, while a change to Ramsey.Uuid.Nonstandard can't break Ramsey.Uuid.Type.
- Position
- Below the diagonal: Ramsey.Uuid.Nonstandard uses a module listed above it, which is the healthy direction.
14→6 Ramsey.Uuid.Nonstandard uses Ramsey.Uuid.Codec✕
- Connections
- 3 pairs of types, where a type in Ramsey.Uuid.Nonstandard uses a type in Ramsey.Uuid.Codec.
- The types involved
Ramsey.Uuid.Nonstandard.Uuid→Ramsey.Uuid.Codec.CodecInterfaceRamsey.Uuid.Nonstandard.UuidBuilder→Ramsey.Uuid.Codec.CodecInterfaceRamsey.Uuid.Nonstandard.UuidV6→Ramsey.Uuid.Codec.CodecInterface
- Direction
- Ramsey.Uuid.Nonstandard uses Ramsey.Uuid.Codec, so a change to Ramsey.Uuid.Codec can break Ramsey.Uuid.Nonstandard, while a change to Ramsey.Uuid.Nonstandard can't break Ramsey.Uuid.Codec.
- Position
- Below the diagonal: Ramsey.Uuid.Nonstandard uses a module listed above it, which is the healthy direction.
14→7 Ramsey.Uuid.Nonstandard uses Ramsey.Uuid.Converter✕
- Connections
- 6 pairs of types, where a type in Ramsey.Uuid.Nonstandard uses a type in Ramsey.Uuid.Converter.
- The types involved
Ramsey.Uuid.Nonstandard.Uuid→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Nonstandard.Uuid→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Nonstandard.UuidBuilder→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Nonstandard.UuidBuilder→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Nonstandard.UuidV6→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Nonstandard.UuidV6→Ramsey.Uuid.Converter.TimeConverterInterface
- Direction
- Ramsey.Uuid.Nonstandard uses Ramsey.Uuid.Converter, so a change to Ramsey.Uuid.Converter can break Ramsey.Uuid.Nonstandard, while a change to Ramsey.Uuid.Nonstandard can't break Ramsey.Uuid.Converter.
- Position
- Below the diagonal: Ramsey.Uuid.Nonstandard uses a module listed above it, which is the healthy direction.
14→18 Ramsey.Uuid.Nonstandard uses Ramsey.Uuid.Rfc4122 part of a loop✕
- Connections
- 5 pairs of types, where a type in Ramsey.Uuid.Nonstandard uses a type in Ramsey.Uuid.Rfc4122.
- The types involved
Ramsey.Uuid.Nonstandard.Fields→Ramsey.Uuid.Rfc4122.FieldsInterfaceRamsey.Uuid.Nonstandard.UuidV6→Ramsey.Uuid.Rfc4122.FieldsInterfaceRamsey.Uuid.Nonstandard.UuidV6→Ramsey.Uuid.Rfc4122.UuidInterfaceRamsey.Uuid.Nonstandard.UuidV6→Ramsey.Uuid.Rfc4122.UuidV1Ramsey.Uuid.Nonstandard.UuidV6→Ramsey.Uuid.Rfc4122.UuidV6
- Direction
- Ramsey.Uuid.Nonstandard uses Ramsey.Uuid.Rfc4122, so a change to Ramsey.Uuid.Rfc4122 can break Ramsey.Uuid.Nonstandard, while a change to Ramsey.Uuid.Nonstandard can't break Ramsey.Uuid.Rfc4122.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→19 Ramsey.Uuid.Nonstandard uses Ramsey.Uuid.Builder part of a loop✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Nonstandard uses a type in Ramsey.Uuid.Builder.
- The types involved
Ramsey.Uuid.Nonstandard.UuidBuilder→Ramsey.Uuid.Builder.UuidBuilderInterface
- Direction
- Ramsey.Uuid.Nonstandard uses Ramsey.Uuid.Builder, so a change to Ramsey.Uuid.Builder can break Ramsey.Uuid.Nonstandard, while a change to Ramsey.Uuid.Nonstandard can't break Ramsey.Uuid.Builder.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→20 Ramsey.Uuid.Nonstandard uses Ramsey.Uuid part of a loop✕
- Connections
- 3 pairs of types, where a type in Ramsey.Uuid.Nonstandard uses a type in Ramsey.Uuid.
- The types involved
Ramsey.Uuid.Nonstandard.Uuid→Ramsey.Uuid.UuidRamsey.Uuid.Nonstandard.UuidBuilder→Ramsey.Uuid.UuidInterfaceRamsey.Uuid.Nonstandard.UuidV6→Ramsey.Uuid.Uuid
- Direction
- Ramsey.Uuid.Nonstandard uses Ramsey.Uuid, so a change to Ramsey.Uuid can break Ramsey.Uuid.Nonstandard, while a change to Ramsey.Uuid.Nonstandard can't break Ramsey.Uuid.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→3 Ramsey.Uuid.Provider.Dce uses Ramsey.Uuid.Type✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Provider.Dce uses a type in Ramsey.Uuid.Type.
- The types involved
Ramsey.Uuid.Provider.Dce.SystemDceSecurityProvider→Ramsey.Uuid.Type.Integer
- Direction
- Ramsey.Uuid.Provider.Dce uses Ramsey.Uuid.Type, so a change to Ramsey.Uuid.Type can break Ramsey.Uuid.Provider.Dce, while a change to Ramsey.Uuid.Provider.Dce can't break Ramsey.Uuid.Type.
- Position
- Below the diagonal: Ramsey.Uuid.Provider.Dce uses a module listed above it, which is the healthy direction.
15→9 Ramsey.Uuid.Provider.Dce uses Ramsey.Uuid.Provider✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Provider.Dce uses a type in Ramsey.Uuid.Provider.
- The types involved
Ramsey.Uuid.Provider.Dce.SystemDceSecurityProvider→Ramsey.Uuid.Provider.DceSecurityProviderInterface
- Direction
- Ramsey.Uuid.Provider.Dce uses Ramsey.Uuid.Provider, so a change to Ramsey.Uuid.Provider can break Ramsey.Uuid.Provider.Dce, while a change to Ramsey.Uuid.Provider.Dce can't break Ramsey.Uuid.Provider.
- Position
- Below the diagonal: Ramsey.Uuid.Provider.Dce uses a module listed above it, which is the healthy direction.
16→3 Ramsey.Uuid.Provider.Node uses Ramsey.Uuid.Type✕
- Connections
- 4 pairs of types, where a type in Ramsey.Uuid.Provider.Node uses a type in Ramsey.Uuid.Type.
- The types involved
Ramsey.Uuid.Provider.Node.FallbackNodeProvider→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Provider.Node.RandomNodeProvider→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Provider.Node.StaticNodeProvider→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Provider.Node.SystemNodeProvider→Ramsey.Uuid.Type.Hexadecimal
- Direction
- Ramsey.Uuid.Provider.Node uses Ramsey.Uuid.Type, so a change to Ramsey.Uuid.Type can break Ramsey.Uuid.Provider.Node, while a change to Ramsey.Uuid.Provider.Node can't break Ramsey.Uuid.Type.
- Position
- Below the diagonal: Ramsey.Uuid.Provider.Node uses a module listed above it, which is the healthy direction.
16→9 Ramsey.Uuid.Provider.Node uses Ramsey.Uuid.Provider✕
- Connections
- 4 pairs of types, where a type in Ramsey.Uuid.Provider.Node uses a type in Ramsey.Uuid.Provider.
- The types involved
Ramsey.Uuid.Provider.Node.FallbackNodeProvider→Ramsey.Uuid.Provider.NodeProviderInterfaceRamsey.Uuid.Provider.Node.RandomNodeProvider→Ramsey.Uuid.Provider.NodeProviderInterfaceRamsey.Uuid.Provider.Node.StaticNodeProvider→Ramsey.Uuid.Provider.NodeProviderInterfaceRamsey.Uuid.Provider.Node.SystemNodeProvider→Ramsey.Uuid.Provider.NodeProviderInterface
- Direction
- Ramsey.Uuid.Provider.Node uses Ramsey.Uuid.Provider, so a change to Ramsey.Uuid.Provider can break Ramsey.Uuid.Provider.Node, while a change to Ramsey.Uuid.Provider.Node can't break Ramsey.Uuid.Provider.
- Position
- Below the diagonal: Ramsey.Uuid.Provider.Node uses a module listed above it, which is the healthy direction.
17→3 Ramsey.Uuid.Provider.Time uses Ramsey.Uuid.Type✕
- Connections
- 2 pairs of types, where a type in Ramsey.Uuid.Provider.Time uses a type in Ramsey.Uuid.Type.
- The types involved
Ramsey.Uuid.Provider.Time.FixedTimeProvider→Ramsey.Uuid.Type.TimeRamsey.Uuid.Provider.Time.SystemTimeProvider→Ramsey.Uuid.Type.Time
- Direction
- Ramsey.Uuid.Provider.Time uses Ramsey.Uuid.Type, so a change to Ramsey.Uuid.Type can break Ramsey.Uuid.Provider.Time, while a change to Ramsey.Uuid.Provider.Time can't break Ramsey.Uuid.Type.
- Position
- Below the diagonal: Ramsey.Uuid.Provider.Time uses a module listed above it, which is the healthy direction.
17→9 Ramsey.Uuid.Provider.Time uses Ramsey.Uuid.Provider✕
- Connections
- 2 pairs of types, where a type in Ramsey.Uuid.Provider.Time uses a type in Ramsey.Uuid.Provider.
- The types involved
Ramsey.Uuid.Provider.Time.FixedTimeProvider→Ramsey.Uuid.Provider.TimeProviderInterfaceRamsey.Uuid.Provider.Time.SystemTimeProvider→Ramsey.Uuid.Provider.TimeProviderInterface
- Direction
- Ramsey.Uuid.Provider.Time uses Ramsey.Uuid.Provider, so a change to Ramsey.Uuid.Provider can break Ramsey.Uuid.Provider.Time, while a change to Ramsey.Uuid.Provider.Time can't break Ramsey.Uuid.Provider.
- Position
- Below the diagonal: Ramsey.Uuid.Provider.Time uses a module listed above it, which is the healthy direction.
18→2 Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid.Fields✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Rfc4122 uses a type in Ramsey.Uuid.Fields.
- The types involved
Ramsey.Uuid.Rfc4122.FieldsInterface→Ramsey.Uuid.Fields.FieldsInterface
- Direction
- Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid.Fields, so a change to Ramsey.Uuid.Fields can break Ramsey.Uuid.Rfc4122, while a change to Ramsey.Uuid.Rfc4122 can't break Ramsey.Uuid.Fields.
- Position
- Below the diagonal: Ramsey.Uuid.Rfc4122 uses a module listed above it, which is the healthy direction.
18→3 Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid.Type✕
- Connections
- 3 pairs of types, where a type in Ramsey.Uuid.Rfc4122 uses a type in Ramsey.Uuid.Type.
- The types involved
Ramsey.Uuid.Rfc4122.Fields→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Rfc4122.FieldsInterface→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Rfc4122.UuidV2→Ramsey.Uuid.Type.Integer
- Direction
- Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid.Type, so a change to Ramsey.Uuid.Type can break Ramsey.Uuid.Rfc4122, while a change to Ramsey.Uuid.Rfc4122 can't break Ramsey.Uuid.Type.
- Position
- Below the diagonal: Ramsey.Uuid.Rfc4122 uses a module listed above it, which is the healthy direction.
18→4 Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid.Validator✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Rfc4122 uses a type in Ramsey.Uuid.Validator.
- The types involved
Ramsey.Uuid.Rfc4122.Validator→Ramsey.Uuid.Validator.ValidatorInterface
- Direction
- Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid.Validator, so a change to Ramsey.Uuid.Validator can break Ramsey.Uuid.Rfc4122, while a change to Ramsey.Uuid.Rfc4122 can't break Ramsey.Uuid.Validator.
- Position
- Below the diagonal: Ramsey.Uuid.Rfc4122 uses a module listed above it, which is the healthy direction.
18→6 Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid.Codec✕
- Connections
- 8 pairs of types, where a type in Ramsey.Uuid.Rfc4122 uses a type in Ramsey.Uuid.Codec.
- The types involved
Ramsey.Uuid.Rfc4122.UuidBuilder→Ramsey.Uuid.Codec.CodecInterfaceRamsey.Uuid.Rfc4122.UuidV1→Ramsey.Uuid.Codec.CodecInterfaceRamsey.Uuid.Rfc4122.UuidV2→Ramsey.Uuid.Codec.CodecInterfaceRamsey.Uuid.Rfc4122.UuidV3→Ramsey.Uuid.Codec.CodecInterfaceRamsey.Uuid.Rfc4122.UuidV4→Ramsey.Uuid.Codec.CodecInterfaceRamsey.Uuid.Rfc4122.UuidV5→Ramsey.Uuid.Codec.CodecInterfaceRamsey.Uuid.Rfc4122.UuidV7→Ramsey.Uuid.Codec.CodecInterfaceRamsey.Uuid.Rfc4122.UuidV8→Ramsey.Uuid.Codec.CodecInterface
- Direction
- Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid.Codec, so a change to Ramsey.Uuid.Codec can break Ramsey.Uuid.Rfc4122, while a change to Ramsey.Uuid.Rfc4122 can't break Ramsey.Uuid.Codec.
- Position
- Below the diagonal: Ramsey.Uuid.Rfc4122 uses a module listed above it, which is the healthy direction.
18→7 Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid.Converter✕
- Connections
- 16 pairs of types, where a type in Ramsey.Uuid.Rfc4122 uses a type in Ramsey.Uuid.Converter.
- The types involved
Ramsey.Uuid.Rfc4122.UuidBuilder→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Rfc4122.UuidBuilder→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Rfc4122.UuidV1→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Rfc4122.UuidV1→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Rfc4122.UuidV2→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Rfc4122.UuidV2→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Rfc4122.UuidV3→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Rfc4122.UuidV3→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Rfc4122.UuidV4→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Rfc4122.UuidV4→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Rfc4122.UuidV5→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Rfc4122.UuidV5→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Rfc4122.UuidV7→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Rfc4122.UuidV7→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Rfc4122.UuidV8→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Rfc4122.UuidV8→Ramsey.Uuid.Converter.TimeConverterInterface
- Direction
- Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid.Converter, so a change to Ramsey.Uuid.Converter can break Ramsey.Uuid.Rfc4122, while a change to Ramsey.Uuid.Rfc4122 can't break Ramsey.Uuid.Converter.
- Position
- Below the diagonal: Ramsey.Uuid.Rfc4122 uses a module listed above it, which is the healthy direction.
18→14 Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid.Nonstandard✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Rfc4122 uses a type in Ramsey.Uuid.Nonstandard.
- The types involved
Ramsey.Uuid.Rfc4122.UuidV6→Ramsey.Uuid.Nonstandard.UuidV6
- Direction
- Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid.Nonstandard, so a change to Ramsey.Uuid.Nonstandard can break Ramsey.Uuid.Rfc4122, while a change to Ramsey.Uuid.Rfc4122 can't break Ramsey.Uuid.Nonstandard.
- Position
- Below the diagonal: Ramsey.Uuid.Rfc4122 uses a module listed above it, which is the healthy direction.
18→19 Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid.Builder part of a loop✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Rfc4122 uses a type in Ramsey.Uuid.Builder.
- The types involved
Ramsey.Uuid.Rfc4122.UuidBuilder→Ramsey.Uuid.Builder.UuidBuilderInterface
- Direction
- Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid.Builder, so a change to Ramsey.Uuid.Builder can break Ramsey.Uuid.Rfc4122, while a change to Ramsey.Uuid.Rfc4122 can't break Ramsey.Uuid.Builder.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→20 Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid part of a loop✕
- Connections
- 11 pairs of types, where a type in Ramsey.Uuid.Rfc4122 uses a type in Ramsey.Uuid.
- The types involved
Ramsey.Uuid.Rfc4122.MaxUuid→Ramsey.Uuid.UuidRamsey.Uuid.Rfc4122.NilUuid→Ramsey.Uuid.UuidRamsey.Uuid.Rfc4122.UuidBuilder→Ramsey.Uuid.UuidInterfaceRamsey.Uuid.Rfc4122.UuidInterface→Ramsey.Uuid.UuidInterfaceRamsey.Uuid.Rfc4122.UuidV1→Ramsey.Uuid.UuidRamsey.Uuid.Rfc4122.UuidV2→Ramsey.Uuid.UuidRamsey.Uuid.Rfc4122.UuidV3→Ramsey.Uuid.UuidRamsey.Uuid.Rfc4122.UuidV4→Ramsey.Uuid.UuidRamsey.Uuid.Rfc4122.UuidV5→Ramsey.Uuid.UuidRamsey.Uuid.Rfc4122.UuidV7→Ramsey.Uuid.UuidRamsey.Uuid.Rfc4122.UuidV8→Ramsey.Uuid.Uuid
- Direction
- Ramsey.Uuid.Rfc4122 uses Ramsey.Uuid, so a change to Ramsey.Uuid can break Ramsey.Uuid.Rfc4122, while a change to Ramsey.Uuid.Rfc4122 can't break Ramsey.Uuid.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→6 Ramsey.Uuid.Builder uses Ramsey.Uuid.Codec✕
- Connections
- 3 pairs of types, where a type in Ramsey.Uuid.Builder uses a type in Ramsey.Uuid.Codec.
- The types involved
Ramsey.Uuid.Builder.DegradedUuidBuilder→Ramsey.Uuid.Codec.CodecInterfaceRamsey.Uuid.Builder.FallbackBuilder→Ramsey.Uuid.Codec.CodecInterfaceRamsey.Uuid.Builder.UuidBuilderInterface→Ramsey.Uuid.Codec.CodecInterface
- Direction
- Ramsey.Uuid.Builder uses Ramsey.Uuid.Codec, so a change to Ramsey.Uuid.Codec can break Ramsey.Uuid.Builder, while a change to Ramsey.Uuid.Builder can't break Ramsey.Uuid.Codec.
- Position
- Below the diagonal: Ramsey.Uuid.Builder uses a module listed above it, which is the healthy direction.
19→7 Ramsey.Uuid.Builder uses Ramsey.Uuid.Converter✕
- Connections
- 2 pairs of types, where a type in Ramsey.Uuid.Builder uses a type in Ramsey.Uuid.Converter.
- The types involved
Ramsey.Uuid.Builder.DegradedUuidBuilder→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Builder.DegradedUuidBuilder→Ramsey.Uuid.Converter.TimeConverterInterface
- Direction
- Ramsey.Uuid.Builder uses Ramsey.Uuid.Converter, so a change to Ramsey.Uuid.Converter can break Ramsey.Uuid.Builder, while a change to Ramsey.Uuid.Builder can't break Ramsey.Uuid.Converter.
- Position
- Below the diagonal: Ramsey.Uuid.Builder uses a module listed above it, which is the healthy direction.
19→18 Ramsey.Uuid.Builder uses Ramsey.Uuid.Rfc4122✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Builder uses a type in Ramsey.Uuid.Rfc4122.
- The types involved
Ramsey.Uuid.Builder.DefaultUuidBuilder→Ramsey.Uuid.Rfc4122.UuidBuilder
- Direction
- Ramsey.Uuid.Builder uses Ramsey.Uuid.Rfc4122, so a change to Ramsey.Uuid.Rfc4122 can break Ramsey.Uuid.Builder, while a change to Ramsey.Uuid.Builder can't break Ramsey.Uuid.Rfc4122.
- Position
- Below the diagonal: Ramsey.Uuid.Builder uses a module listed above it, which is the healthy direction.
19→20 Ramsey.Uuid.Builder uses Ramsey.Uuid part of a loop✕
- Connections
- 3 pairs of types, where a type in Ramsey.Uuid.Builder uses a type in Ramsey.Uuid.
- The types involved
Ramsey.Uuid.Builder.DegradedUuidBuilder→Ramsey.Uuid.UuidInterfaceRamsey.Uuid.Builder.FallbackBuilder→Ramsey.Uuid.UuidInterfaceRamsey.Uuid.Builder.UuidBuilderInterface→Ramsey.Uuid.UuidInterface
- Direction
- Ramsey.Uuid.Builder uses Ramsey.Uuid, so a change to Ramsey.Uuid can break Ramsey.Uuid.Builder, while a change to Ramsey.Uuid.Builder can't break Ramsey.Uuid.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→2 Ramsey.Uuid uses Ramsey.Uuid.Fields✕
- Connections
- 2 pairs of types, where a type in Ramsey.Uuid uses a type in Ramsey.Uuid.Fields.
- The types involved
Ramsey.Uuid.Uuid→Ramsey.Uuid.Fields.FieldsInterfaceRamsey.Uuid.UuidInterface→Ramsey.Uuid.Fields.FieldsInterface
- Direction
- Ramsey.Uuid uses Ramsey.Uuid.Fields, so a change to Ramsey.Uuid.Fields can break Ramsey.Uuid, while a change to Ramsey.Uuid can't break Ramsey.Uuid.Fields.
- Position
- Below the diagonal: Ramsey.Uuid uses a module listed above it, which is the healthy direction.
20→3 Ramsey.Uuid uses Ramsey.Uuid.Type✕
- Connections
- 8 pairs of types, where a type in Ramsey.Uuid uses a type in Ramsey.Uuid.Type.
- The types involved
Ramsey.Uuid.Uuid→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Uuid→Ramsey.Uuid.Type.IntegerRamsey.Uuid.UuidFactory→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.UuidFactory→Ramsey.Uuid.Type.IntegerRamsey.Uuid.UuidFactoryInterface→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.UuidFactoryInterface→Ramsey.Uuid.Type.IntegerRamsey.Uuid.UuidInterface→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.UuidInterface→Ramsey.Uuid.Type.Integer
- Direction
- Ramsey.Uuid uses Ramsey.Uuid.Type, so a change to Ramsey.Uuid.Type can break Ramsey.Uuid, while a change to Ramsey.Uuid can't break Ramsey.Uuid.Type.
- Position
- Below the diagonal: Ramsey.Uuid uses a module listed above it, which is the healthy direction.
20→4 Ramsey.Uuid uses Ramsey.Uuid.Validator✕
- Connections
- 3 pairs of types, where a type in Ramsey.Uuid uses a type in Ramsey.Uuid.Validator.
- The types involved
Ramsey.Uuid.FeatureSet→Ramsey.Uuid.Validator.ValidatorInterfaceRamsey.Uuid.UuidFactory→Ramsey.Uuid.Validator.ValidatorInterfaceRamsey.Uuid.UuidFactoryInterface→Ramsey.Uuid.Validator.ValidatorInterface
- Direction
- Ramsey.Uuid uses Ramsey.Uuid.Validator, so a change to Ramsey.Uuid.Validator can break Ramsey.Uuid, while a change to Ramsey.Uuid can't break Ramsey.Uuid.Validator.
- Position
- Below the diagonal: Ramsey.Uuid uses a module listed above it, which is the healthy direction.
20→6 Ramsey.Uuid uses Ramsey.Uuid.Codec✕
- Connections
- 3 pairs of types, where a type in Ramsey.Uuid uses a type in Ramsey.Uuid.Codec.
- The types involved
Ramsey.Uuid.FeatureSet→Ramsey.Uuid.Codec.CodecInterfaceRamsey.Uuid.Uuid→Ramsey.Uuid.Codec.CodecInterfaceRamsey.Uuid.UuidFactory→Ramsey.Uuid.Codec.CodecInterface
- Direction
- Ramsey.Uuid uses Ramsey.Uuid.Codec, so a change to Ramsey.Uuid.Codec can break Ramsey.Uuid, while a change to Ramsey.Uuid can't break Ramsey.Uuid.Codec.
- Position
- Below the diagonal: Ramsey.Uuid uses a module listed above it, which is the healthy direction.
20→7 Ramsey.Uuid uses Ramsey.Uuid.Converter✕
- Connections
- 8 pairs of types, where a type in Ramsey.Uuid uses a type in Ramsey.Uuid.Converter.
- The types involved
Ramsey.Uuid.DeprecatedUuidInterface→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.DeprecatedUuidMethodsTrait→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.FeatureSet→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.FeatureSet→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Uuid→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Uuid→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.UuidFactory→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.UuidFactory→Ramsey.Uuid.Converter.TimeConverterInterface
- Direction
- Ramsey.Uuid uses Ramsey.Uuid.Converter, so a change to Ramsey.Uuid.Converter can break Ramsey.Uuid, while a change to Ramsey.Uuid can't break Ramsey.Uuid.Converter.
- Position
- Below the diagonal: Ramsey.Uuid uses a module listed above it, which is the healthy direction.
20→8 Ramsey.Uuid uses Ramsey.Uuid.Math✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid uses a type in Ramsey.Uuid.Math.
- The types involved
Ramsey.Uuid.FeatureSet→Ramsey.Uuid.Math.CalculatorInterface
- Direction
- Ramsey.Uuid uses Ramsey.Uuid.Math, so a change to Ramsey.Uuid.Math can break Ramsey.Uuid, while a change to Ramsey.Uuid can't break Ramsey.Uuid.Math.
- Position
- Below the diagonal: Ramsey.Uuid uses a module listed above it, which is the healthy direction.
20→9 Ramsey.Uuid uses Ramsey.Uuid.Provider✕
- Connections
- 4 pairs of types, where a type in Ramsey.Uuid uses a type in Ramsey.Uuid.Provider.
- The types involved
Ramsey.Uuid.FeatureSet→Ramsey.Uuid.Provider.DceSecurityProviderInterfaceRamsey.Uuid.FeatureSet→Ramsey.Uuid.Provider.NodeProviderInterfaceRamsey.Uuid.FeatureSet→Ramsey.Uuid.Provider.TimeProviderInterfaceRamsey.Uuid.UuidFactory→Ramsey.Uuid.Provider.NodeProviderInterface
- Direction
- Ramsey.Uuid uses Ramsey.Uuid.Provider, so a change to Ramsey.Uuid.Provider can break Ramsey.Uuid, while a change to Ramsey.Uuid can't break Ramsey.Uuid.Provider.
- Position
- Below the diagonal: Ramsey.Uuid uses a module listed above it, which is the healthy direction.
20→13 Ramsey.Uuid uses Ramsey.Uuid.Generator✕
- Connections
- 8 pairs of types, where a type in Ramsey.Uuid uses a type in Ramsey.Uuid.Generator.
- The types involved
Ramsey.Uuid.FeatureSet→Ramsey.Uuid.Generator.DceSecurityGeneratorInterfaceRamsey.Uuid.FeatureSet→Ramsey.Uuid.Generator.NameGeneratorInterfaceRamsey.Uuid.FeatureSet→Ramsey.Uuid.Generator.RandomGeneratorInterfaceRamsey.Uuid.FeatureSet→Ramsey.Uuid.Generator.TimeGeneratorInterfaceRamsey.Uuid.UuidFactory→Ramsey.Uuid.Generator.DceSecurityGeneratorInterfaceRamsey.Uuid.UuidFactory→Ramsey.Uuid.Generator.NameGeneratorInterfaceRamsey.Uuid.UuidFactory→Ramsey.Uuid.Generator.RandomGeneratorInterfaceRamsey.Uuid.UuidFactory→Ramsey.Uuid.Generator.TimeGeneratorInterface
- Direction
- Ramsey.Uuid uses Ramsey.Uuid.Generator, so a change to Ramsey.Uuid.Generator can break Ramsey.Uuid, while a change to Ramsey.Uuid can't break Ramsey.Uuid.Generator.
- Position
- Below the diagonal: Ramsey.Uuid uses a module listed above it, which is the healthy direction.
20→18 Ramsey.Uuid uses Ramsey.Uuid.Rfc4122✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid uses a type in Ramsey.Uuid.Rfc4122.
- The types involved
Ramsey.Uuid.Uuid→Ramsey.Uuid.Rfc4122.FieldsInterface
- Direction
- Ramsey.Uuid uses Ramsey.Uuid.Rfc4122, so a change to Ramsey.Uuid.Rfc4122 can break Ramsey.Uuid, while a change to Ramsey.Uuid can't break Ramsey.Uuid.Rfc4122.
- Position
- Below the diagonal: Ramsey.Uuid uses a module listed above it, which is the healthy direction.
20→19 Ramsey.Uuid uses Ramsey.Uuid.Builder✕
- Connections
- 2 pairs of types, where a type in Ramsey.Uuid uses a type in Ramsey.Uuid.Builder.
- The types involved
Ramsey.Uuid.FeatureSet→Ramsey.Uuid.Builder.UuidBuilderInterfaceRamsey.Uuid.UuidFactory→Ramsey.Uuid.Builder.UuidBuilderInterface
- Direction
- Ramsey.Uuid uses Ramsey.Uuid.Builder, so a change to Ramsey.Uuid.Builder can break Ramsey.Uuid, while a change to Ramsey.Uuid can't break Ramsey.Uuid.Builder.
- Position
- Below the diagonal: Ramsey.Uuid uses a module listed above it, which is the healthy direction.
21→3 Ramsey.Uuid.Guid uses Ramsey.Uuid.Type✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Guid uses a type in Ramsey.Uuid.Type.
- The types involved
Ramsey.Uuid.Guid.Fields→Ramsey.Uuid.Type.Hexadecimal
- Direction
- Ramsey.Uuid.Guid uses Ramsey.Uuid.Type, so a change to Ramsey.Uuid.Type can break Ramsey.Uuid.Guid, while a change to Ramsey.Uuid.Guid can't break Ramsey.Uuid.Type.
- Position
- Below the diagonal: Ramsey.Uuid.Guid uses a module listed above it, which is the healthy direction.
21→6 Ramsey.Uuid.Guid uses Ramsey.Uuid.Codec✕
- Connections
- 2 pairs of types, where a type in Ramsey.Uuid.Guid uses a type in Ramsey.Uuid.Codec.
- The types involved
Ramsey.Uuid.Guid.Guid→Ramsey.Uuid.Codec.CodecInterfaceRamsey.Uuid.Guid.GuidBuilder→Ramsey.Uuid.Codec.CodecInterface
- Direction
- Ramsey.Uuid.Guid uses Ramsey.Uuid.Codec, so a change to Ramsey.Uuid.Codec can break Ramsey.Uuid.Guid, while a change to Ramsey.Uuid.Guid can't break Ramsey.Uuid.Codec.
- Position
- Below the diagonal: Ramsey.Uuid.Guid uses a module listed above it, which is the healthy direction.
21→7 Ramsey.Uuid.Guid uses Ramsey.Uuid.Converter✕
- Connections
- 4 pairs of types, where a type in Ramsey.Uuid.Guid uses a type in Ramsey.Uuid.Converter.
- The types involved
Ramsey.Uuid.Guid.Guid→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Guid.Guid→Ramsey.Uuid.Converter.TimeConverterInterfaceRamsey.Uuid.Guid.GuidBuilder→Ramsey.Uuid.Converter.NumberConverterInterfaceRamsey.Uuid.Guid.GuidBuilder→Ramsey.Uuid.Converter.TimeConverterInterface
- Direction
- Ramsey.Uuid.Guid uses Ramsey.Uuid.Converter, so a change to Ramsey.Uuid.Converter can break Ramsey.Uuid.Guid, while a change to Ramsey.Uuid.Guid can't break Ramsey.Uuid.Converter.
- Position
- Below the diagonal: Ramsey.Uuid.Guid uses a module listed above it, which is the healthy direction.
21→18 Ramsey.Uuid.Guid uses Ramsey.Uuid.Rfc4122✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Guid uses a type in Ramsey.Uuid.Rfc4122.
- The types involved
Ramsey.Uuid.Guid.Fields→Ramsey.Uuid.Rfc4122.FieldsInterface
- Direction
- Ramsey.Uuid.Guid uses Ramsey.Uuid.Rfc4122, so a change to Ramsey.Uuid.Rfc4122 can break Ramsey.Uuid.Guid, while a change to Ramsey.Uuid.Guid can't break Ramsey.Uuid.Rfc4122.
- Position
- Below the diagonal: Ramsey.Uuid.Guid uses a module listed above it, which is the healthy direction.
21→19 Ramsey.Uuid.Guid uses Ramsey.Uuid.Builder✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Guid uses a type in Ramsey.Uuid.Builder.
- The types involved
Ramsey.Uuid.Guid.GuidBuilder→Ramsey.Uuid.Builder.UuidBuilderInterface
- Direction
- Ramsey.Uuid.Guid uses Ramsey.Uuid.Builder, so a change to Ramsey.Uuid.Builder can break Ramsey.Uuid.Guid, while a change to Ramsey.Uuid.Guid can't break Ramsey.Uuid.Builder.
- Position
- Below the diagonal: Ramsey.Uuid.Guid uses a module listed above it, which is the healthy direction.
21→20 Ramsey.Uuid.Guid uses Ramsey.Uuid✕
- Connections
- 2 pairs of types, where a type in Ramsey.Uuid.Guid uses a type in Ramsey.Uuid.
- The types involved
Ramsey.Uuid.Guid.Guid→Ramsey.Uuid.UuidRamsey.Uuid.Guid.GuidBuilder→Ramsey.Uuid.UuidInterface
- Direction
- Ramsey.Uuid.Guid uses Ramsey.Uuid, so a change to Ramsey.Uuid can break Ramsey.Uuid.Guid, while a change to Ramsey.Uuid.Guid can't break Ramsey.Uuid.
- Position
- Below the diagonal: Ramsey.Uuid.Guid uses a module listed above it, which is the healthy direction.
22→2 Ramsey.Uuid.Lazy uses Ramsey.Uuid.Fields✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Lazy uses a type in Ramsey.Uuid.Fields.
- The types involved
Ramsey.Uuid.Lazy.LazyUuidFromString→Ramsey.Uuid.Fields.FieldsInterface
- Direction
- Ramsey.Uuid.Lazy uses Ramsey.Uuid.Fields, so a change to Ramsey.Uuid.Fields can break Ramsey.Uuid.Lazy, while a change to Ramsey.Uuid.Lazy can't break Ramsey.Uuid.Fields.
- Position
- Below the diagonal: Ramsey.Uuid.Lazy uses a module listed above it, which is the healthy direction.
22→3 Ramsey.Uuid.Lazy uses Ramsey.Uuid.Type✕
- Connections
- 2 pairs of types, where a type in Ramsey.Uuid.Lazy uses a type in Ramsey.Uuid.Type.
- The types involved
Ramsey.Uuid.Lazy.LazyUuidFromString→Ramsey.Uuid.Type.HexadecimalRamsey.Uuid.Lazy.LazyUuidFromString→Ramsey.Uuid.Type.Integer
- Direction
- Ramsey.Uuid.Lazy uses Ramsey.Uuid.Type, so a change to Ramsey.Uuid.Type can break Ramsey.Uuid.Lazy, while a change to Ramsey.Uuid.Lazy can't break Ramsey.Uuid.Type.
- Position
- Below the diagonal: Ramsey.Uuid.Lazy uses a module listed above it, which is the healthy direction.
22→7 Ramsey.Uuid.Lazy uses Ramsey.Uuid.Converter✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Lazy uses a type in Ramsey.Uuid.Converter.
- The types involved
Ramsey.Uuid.Lazy.LazyUuidFromString→Ramsey.Uuid.Converter.NumberConverterInterface
- Direction
- Ramsey.Uuid.Lazy uses Ramsey.Uuid.Converter, so a change to Ramsey.Uuid.Converter can break Ramsey.Uuid.Lazy, while a change to Ramsey.Uuid.Lazy can't break Ramsey.Uuid.Converter.
- Position
- Below the diagonal: Ramsey.Uuid.Lazy uses a module listed above it, which is the healthy direction.
22→18 Ramsey.Uuid.Lazy uses Ramsey.Uuid.Rfc4122✕
- Connections
- 2 pairs of types, where a type in Ramsey.Uuid.Lazy uses a type in Ramsey.Uuid.Rfc4122.
- The types involved
Ramsey.Uuid.Lazy.LazyUuidFromString→Ramsey.Uuid.Rfc4122.UuidV1Ramsey.Uuid.Lazy.LazyUuidFromString→Ramsey.Uuid.Rfc4122.UuidV6
- Direction
- Ramsey.Uuid.Lazy uses Ramsey.Uuid.Rfc4122, so a change to Ramsey.Uuid.Rfc4122 can break Ramsey.Uuid.Lazy, while a change to Ramsey.Uuid.Lazy can't break Ramsey.Uuid.Rfc4122.
- Position
- Below the diagonal: Ramsey.Uuid.Lazy uses a module listed above it, which is the healthy direction.
22→20 Ramsey.Uuid.Lazy uses Ramsey.Uuid✕
- Connections
- 1 pair of types, where a type in Ramsey.Uuid.Lazy uses a type in Ramsey.Uuid.
- The types involved
Ramsey.Uuid.Lazy.LazyUuidFromString→Ramsey.Uuid.UuidInterface
- Direction
- Ramsey.Uuid.Lazy uses Ramsey.Uuid, so a change to Ramsey.Uuid can break Ramsey.Uuid.Lazy, while a change to Ramsey.Uuid.Lazy can't break Ramsey.Uuid.
- Position
- Below the diagonal: Ramsey.Uuid.Lazy 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
| A05:2025 — Injection | 1 | High / Critical |
Roadmap
Top priorities: Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED; Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +7.8 pts | Medium | Architecture documentation |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +1.1 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +1.1 pts | Low | Project Cohesion |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.5 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.5 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.4 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.4 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Nonstandard/UuidV6.php | 7.4 | Mixed | Code Duplication: Edited copy of a member (11 corresponding lines) |
| src/Guid/Fields.php | 7.4 | Mixed | Code Duplication: Edited copy of a member (8 corresponding lines) |
| src/Converter/Time/GenericTimeConverter.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (28 corresponding lines) |
| src/DeprecatedUuidMethodsTrait.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (12 corresponding lines) |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| src/Lazy/LazyUuidFromString.php | 8.5 | Near-clean | God Classes: TooManyMethods: LazyUuidFromString |
| src/UuidFactory.php | 8.5 | Near-clean | God Classes: TooManyMethods: UuidFactory |
| src/Uuid.php | 8.5 | Near-clean | God Classes: TooManyMethods: Uuid |
| src/Provider/Dce/SystemDceSecurityProvider.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (20 corresponding lines) |
| src/Rfc4122/Validator.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (4 corresponding lines) |
| src/Codec/GuidStringCodec.php | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
| src/Fields/SerializableFieldsTrait.php | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 6) |
| src/Guid/GuidBuilder.php | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 40 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 24 of 33 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a Codecov configuration (codecov.yml) and a coverage step in CI (`codecov/codecov-action`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.php), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its Composer package dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated 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. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's PHP, Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's PHP, Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 3 TooManyMethods finding(s) in God Classes — start with LazyUuidFromString.php, UuidFactory.php, Uuid.php. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
8 duplicated block group(s) detected. 3.4 % of the production lines (290 of 8,549) are in a reported copy. A further 7 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with GuidStringCodec.php, Fields.php, UuidV6.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Edited copy of a member (28 corresponding lines) finding(s) in Code Duplication — start with GenericTimeConverter.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with DeprecatedUuidMethodsTrait.php. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 16 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 391 tests.
D12 · Dependency Hygiene
1 outdated, 0 abandoned direct Composer dependencies. PLATFORM requirements (php, ext-*, lib-*) are deliberately not graded here: they name the runtime rather than a Packagist package, so there is no release for them to be behind — whether that runtime is still supported is a separate question with a separate remedy. Development requirements are excluded, because a consumer never installs them. A newer release is reported only where this repository's OWN constraint already admits it, so the remedy is `composer update` and never a manifest edit. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 3 locked Composer package(s) use a banned license. Licences were read from this repository's REDACTED, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 77 package(s) under `packages-dev` are not installed for a consumer and are excluded. ★ COVERAGE OF THIS VERDICT: it grades this repository's Composer package dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/FeatureSet.php. Counted over 37 of the 114 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
0 deducted task-comment markers across 8549 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 61 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 2 build units (Composer, Python) 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
28 % of calls cross a namespace and 23 % go through an interface, but 99 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 37 of the 114 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
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 2 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P10 · Library API & versioning
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `pip`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `pip` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF1 · Benchmark discipline
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X3 · Exception handling
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 97% | Exemplary | Solid. |
| Architecture | 86% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 69% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 87% | Strong | Solid. |
| Security | 82% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's PHP imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. PHP builds its object graph per request and shares none of it between requests.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed PHP surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .php, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Composer build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P2 Observability — This repository's PHP, Python source (2 module(s), 115 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 — no HTTP server, API framework or worker entry point was found in the PHP, Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 1% of this repository's production lines — php (8,469 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — X13 reached only 1% of this repository's production lines — php (8,469 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's PHP and Python were read, and no request in it can be cancelled by a caller (amphp's HttpClient or connect) — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 1 finding(s)
- REDACTED
Serious — 22 finding(s)
- TooManyMethods: LazyUuidFromString src/Lazy/LazyUuidFromString.php:51
- TooManyMethods: UuidFactory src/UuidFactory.php:48
- TooManyMethods: Uuid src/Uuid.php:47
- Duplicated block (9 lines × 2) src/Codec/GuidStringCodec.php:36
- Duplicated block (9 lines × 2) src/Guid/Fields.php:132
- Duplicated block (9 lines × 2) src/Nonstandard/UuidV6.php:73
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (28 corresponding lines) src/Converter/Time/GenericTimeConverter.php:58
- Edited copy of a member (12 corresponding lines) src/DeprecatedUuidMethodsTrait.php:119
- Edited copy of a member (11 corresponding lines) src/Nonstandard/UuidV6.php:73
- Edited copy of a member (13 corresponding lines) src/Converter/Time/GenericTimeConverter.php:94
- Edited copy of a member (20 corresponding lines) src/Provider/Dce/SystemDceSecurityProvider.php:45
- Edited copy of a member (4 corresponding lines) src/Rfc4122/Validator.php:44
- Edited copy of a member (8 corresponding lines) src/Guid/Fields.php:160
- Duplicated block (12 lines × 2) src/DeprecatedUuidMethodsTrait.php:123
- Duplicated block (6 lines × 6) src/Fields/SerializableFieldsTrait.php:76
- Duplicated block (6 lines × 2) src/Guid/Fields.php:122
- Duplicated block (7 lines × 2) src/Guid/GuidBuilder.php:57
- Duplicated block (7 lines × 7) src/Nonstandard/UuidV6.php:59
Minor — 9 finding(s)
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- CI build step not evidenced
- Dependabot does not watch pip REDACTED:2
Minor — 1 finding(s)
- Outdated: ramsey/collection
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-763c0713045440169eba82bd577ce0df/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-763c0713045440169eba82bd577ce0df/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 1 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 2 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |