Executive summary
itsgoingd/clockwork falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 52.5 out of 100 and is rated Adequate, and it has no critical findings.
Production Readiness, at 36.0, is the weakest lens and counts most in the score. The best first step is adding an automated build and test pipeline, worth about 10.4 points. Recording design decisions comes next, worth about 7.0 points. Raising Production Readiness to 70 would lift the score to about 64.6.
Most of the 42 serious findings are in Code Health.
The product code is 9,164 lines, about €9,000 to rebuild.
If Production Readiness rose from 36.0 to 70, the lowest score rated Strong, the score would rise from 52.5 to about 64.6.
New since the last survey: 22 findings
- Code Duplication · Edited copy of a member (20 corresponding lines) Clockwork/Support/Slim/ClockworkMiddleware.php
- Code Duplication · Edited copy of a member (27 corresponding lines) Clockwork/Support/Laravel/ClockworkSupport.php
- Code Duplication · Edited copy of a member (20 corresponding lines) Clockwork/DataSource/LaravelDataSource.php
- Code Duplication · Edited copy of a member (17 corresponding lines) Clockwork/Support/Slim/ClockworkMiddleware.php
- Code Duplication · Edited copy of a member (14 corresponding lines) Clockwork/Support/Slim/ClockworkMiddleware.php
- Code Duplication · Edited copy of a member (14 corresponding lines) Clockwork/Storage/RedisStorage.php
- Code Duplication · Edited copy of a member (13 corresponding lines) Clockwork/DataSource/LaravelDataSource.php
- Code Duplication · Edited copy of a member (11 corresponding lines) Clockwork/Storage/RedisStorage.php
- Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) Clockwork/DataSource/PhpDataSource.php
- Code Duplication · Edited copy of a member (12 corresponding lines) Clockwork/Storage/SqlStorage.php
- Code Duplication · Edited copy of a member (7 corresponding lines) Clockwork/Support/Vanilla/Clockwork.php
- Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) Clockwork/Storage/SqlStorage.php
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) Clockwork/Storage/Search.php
- Code Duplication · Edited copy of a member (6 corresponding lines) Clockwork/Support/Vanilla/ClockworkMiddleware.php
- Code Duplication · Edited copy of a member (10 corresponding lines) Clockwork/Support/Doctrine/Legacy/Logger.php
- Code Duplication · Edited copy of a member (9 corresponding lines) Clockwork/Support/Laravel/ClockworkSupport.php
- Code Duplication · Edited copy of a member (7 corresponding lines) Clockwork/Support/Laravel/ClockworkController.php
- Code Duplication · Edited copy of a member (3 corresponding lines) Clockwork/DataSource/LaravelDataSource.php
- Code Duplication · Edited copy of a member (9 corresponding lines) Clockwork/DataSource/LaravelQueueDataSource.php
- Code Duplication · Edited copy of a member (3 corresponding lines) Clockwork/Support/Slim/ClockworkMiddleware.php
- Code Duplication · Edited copy of a member (5 corresponding lines) Clockwork/Storage/RedisStorage.php
- Code Duplication · Edited copy of a member (5 corresponding lines) Clockwork/Support/Laravel/ClockworkController.php
Fixed since the last survey: 1 finding
- Code Duplication · Duplicated block (6–7 lines × 2) Clockwork/Storage/SqlSearch.php
Rebuild cost: about €9,000 · Estimate
| Cost to rebuild | €3,000 to €15,000, for 50 to 158 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 52. 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: 9,164 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 Authentication | 2 Helpers.Concerns | 3 Request | 4 Request.Timeline | 5 Support.Doctrine | 6 Support.Doctrine.Legacy | 7 Support.Guzzle | 8 Support.Laravel.Console | 9 Support.Slim | 10 Support.Slim.Legacy | 11 Support.Vanilla | 12 Web | 13 DataSource | 14 Helpers | 15 Storage | 16 Support.Monolog.Handler | 17 Support.Monolog.Monolog | 18 Support.Monolog.Monolog2 | 19 Support.Monolog.Monolog3 | 20 Support.Swift | 21 Support.Twig | 22 Clockwork | 23 DataSource.Concerns | 24 Support.Laravel.Eloquent | 25 Support.Laravel | 26 Support.Slim.Old | 27 Support.Symfony | 28 Support.Lumen |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Authentication | ||||||||||||||||||||||||||||
| 2 Helpers.Concerns | ||||||||||||||||||||||||||||
| 3 Request | ||||||||||||||||||||||||||||
| 4 Request.Timeline | ||||||||||||||||||||||||||||
| 5 Support.Doctrine | ||||||||||||||||||||||||||||
| 6 Support.Doctrine.Legacy | ||||||||||||||||||||||||||||
| 7 Support.Guzzle | ||||||||||||||||||||||||||||
| 8 Support.Laravel.Console | ||||||||||||||||||||||||||||
| 9 Support.Slim | ||||||||||||||||||||||||||||
| 10 Support.Slim.Legacy | ||||||||||||||||||||||||||||
| 11 Support.Vanilla | ||||||||||||||||||||||||||||
| 12 Web | ||||||||||||||||||||||||||||
| 13 DataSource | 21 | |||||||||||||||||||||||||||
| 14 Helpers | 1 | |||||||||||||||||||||||||||
| 15 Storage | 7 | |||||||||||||||||||||||||||
| 16 Support.Monolog.Handler | 1 | |||||||||||||||||||||||||||
| 17 Support.Monolog.Monolog | 1 | |||||||||||||||||||||||||||
| 18 Support.Monolog.Monolog2 | 1 | |||||||||||||||||||||||||||
| 19 Support.Monolog.Monolog3 | 1 | |||||||||||||||||||||||||||
| 20 Support.Swift | 1 | |||||||||||||||||||||||||||
| 21 Support.Twig | 1 | |||||||||||||||||||||||||||
| 22 Clockwork | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||
| 23 DataSource.Concerns | 1 | 1 | ||||||||||||||||||||||||||
| 24 Support.Laravel.Eloquent | 2 | |||||||||||||||||||||||||||
| 25 Support.Laravel | 1 | |||||||||||||||||||||||||||
| 26 Support.Slim.Old | 1 | |||||||||||||||||||||||||||
| 27 Support.Symfony | 1 | 1 | ||||||||||||||||||||||||||
| 28 Support.Lumen | 1 | 2 |
13→3 DataSource uses Request✕
- Connections
- 21 pairs of types, where a type in DataSource uses a type in Request.
- The types involved
Clockwork.DataSource.DBALDataSource→Clockwork.Request.RequestClockwork.DataSource.DataSource→Clockwork.Request.RequestClockwork.DataSource.DataSourceInterface→Clockwork.Request.RequestClockwork.DataSource.EloquentDataSource→Clockwork.Request.RequestClockwork.DataSource.GuzzleDataSource→Clockwork.Request.RequestClockwork.DataSource.LaravelCacheDataSource→Clockwork.Request.RequestClockwork.DataSource.LaravelDataSource→Clockwork.Request.RequestClockwork.DataSource.LaravelEventsDataSource→Clockwork.Request.RequestClockwork.DataSource.LaravelHttpClientDataSource→Clockwork.Request.RequestClockwork.DataSource.LaravelNotificationsDataSource→Clockwork.Request.RequestClockwork.DataSource.LaravelQueueDataSource→Clockwork.Request.RequestClockwork.DataSource.LaravelRedisDataSource→Clockwork.Request.RequestClockwork.DataSource.LaravelViewsDataSource→Clockwork.Request.RequestClockwork.DataSource.LumenDataSource→Clockwork.Request.RequestClockwork.DataSource.MonologDataSource→Clockwork.Request.RequestClockwork.DataSource.PhpDataSource→Clockwork.Request.RequestClockwork.DataSource.PsrMessageDataSource→Clockwork.Request.RequestClockwork.DataSource.SlimDataSource→Clockwork.Request.RequestClockwork.DataSource.SwiftDataSource→Clockwork.Request.RequestClockwork.DataSource.TwigDataSource→Clockwork.Request.RequestClockwork.DataSource.XdebugDataSource→Clockwork.Request.Request
- Direction
- DataSource uses Request, so a change to Request can break DataSource, while a change to DataSource can't break Request.
- Position
- Below the diagonal: DataSource uses a module listed above it, which is the healthy direction.
14→3 Helpers uses Request✕
- Connections
- 1 pair of types, where a type in Helpers uses a type in Request.
- The types involved
Clockwork.Helpers.ServerTiming→Clockwork.Request.Request
- Direction
- Helpers uses Request, so a change to Request can break Helpers, while a change to Helpers can't break Request.
- Position
- Below the diagonal: Helpers uses a module listed above it, which is the healthy direction.
15→3 Storage uses Request✕
- Connections
- 7 pairs of types, where a type in Storage uses a type in Request.
- The types involved
Clockwork.Storage.FileStorage→Clockwork.Request.RequestClockwork.Storage.RedisStorage→Clockwork.Request.RequestClockwork.Storage.Search→Clockwork.Request.RequestClockwork.Storage.SqlStorage→Clockwork.Request.RequestClockwork.Storage.Storage→Clockwork.Request.RequestClockwork.Storage.StorageInterface→Clockwork.Request.RequestClockwork.Storage.SymfonyStorage→Clockwork.Request.Request
- Direction
- Storage uses Request, so a change to Request can break Storage, while a change to Storage can't break Request.
- Position
- Below the diagonal: Storage uses a module listed above it, which is the healthy direction.
16→3 Support.Monolog.Handler uses Request✕
- Connections
- 1 pair of types, where a type in Support.Monolog.Handler uses a type in Request.
- The types involved
Clockwork.Support.Monolog.Handler.ClockworkHandler→Clockwork.Request.Log
- Direction
- Support.Monolog.Handler uses Request, so a change to Request can break Support.Monolog.Handler, while a change to Support.Monolog.Handler can't break Request.
- Position
- Below the diagonal: Support.Monolog.Handler uses a module listed above it, which is the healthy direction.
17→3 Support.Monolog.Monolog uses Request✕
- Connections
- 1 pair of types, where a type in Support.Monolog.Monolog uses a type in Request.
- The types involved
Clockwork.Support.Monolog.Monolog.ClockworkHandler→Clockwork.Request.Log
- Direction
- Support.Monolog.Monolog uses Request, so a change to Request can break Support.Monolog.Monolog, while a change to Support.Monolog.Monolog can't break Request.
- Position
- Below the diagonal: Support.Monolog.Monolog uses a module listed above it, which is the healthy direction.
18→3 Support.Monolog.Monolog2 uses Request✕
- Connections
- 1 pair of types, where a type in Support.Monolog.Monolog2 uses a type in Request.
- The types involved
Clockwork.Support.Monolog.Monolog2.ClockworkHandler→Clockwork.Request.Log
- Direction
- Support.Monolog.Monolog2 uses Request, so a change to Request can break Support.Monolog.Monolog2, while a change to Support.Monolog.Monolog2 can't break Request.
- Position
- Below the diagonal: Support.Monolog.Monolog2 uses a module listed above it, which is the healthy direction.
19→3 Support.Monolog.Monolog3 uses Request✕
- Connections
- 1 pair of types, where a type in Support.Monolog.Monolog3 uses a type in Request.
- The types involved
Clockwork.Support.Monolog.Monolog3.ClockworkHandler→Clockwork.Request.Log
- Direction
- Support.Monolog.Monolog3 uses Request, so a change to Request can break Support.Monolog.Monolog3, while a change to Support.Monolog.Monolog3 can't break Request.
- Position
- Below the diagonal: Support.Monolog.Monolog3 uses a module listed above it, which is the healthy direction.
20→4 Support.Swift uses Request.Timeline✕
- Connections
- 1 pair of types, where a type in Support.Swift uses a type in Request.Timeline.
- The types involved
Clockwork.Support.Swift.SwiftPluginClockworkTimeline→Clockwork.Request.Timeline.Timeline
- Direction
- Support.Swift uses Request.Timeline, so a change to Request.Timeline can break Support.Swift, while a change to Support.Swift can't break Request.Timeline.
- Position
- Below the diagonal: Support.Swift uses a module listed above it, which is the healthy direction.
21→4 Support.Twig uses Request.Timeline✕
- Connections
- 1 pair of types, where a type in Support.Twig uses a type in Request.Timeline.
- The types involved
Clockwork.Support.Twig.ProfilerClockworkDumper→Clockwork.Request.Timeline.Timeline
- Direction
- Support.Twig uses Request.Timeline, so a change to Request.Timeline can break Support.Twig, while a change to Support.Twig can't break Request.Timeline.
- Position
- Below the diagonal: Support.Twig uses a module listed above it, which is the healthy direction.
22→1 Clockwork uses Authentication✕
- Connections
- 1 pair of types, where a type in Clockwork uses a type in Authentication.
- The types involved
Clockwork.Clockwork→Clockwork.Authentication.AuthenticatorInterface
- Direction
- Clockwork uses Authentication, so a change to Authentication can break Clockwork, while a change to Clockwork can't break Authentication.
- Position
- Below the diagonal: Clockwork uses a module listed above it, which is the healthy direction.
22→3 Clockwork uses Request✕
- Connections
- 1 pair of types, where a type in Clockwork uses a type in Request.
- The types involved
Clockwork.Clockwork→Clockwork.Request.Request
- Direction
- Clockwork uses Request, so a change to Request can break Clockwork, while a change to Clockwork can't break Request.
- Position
- Below the diagonal: Clockwork uses a module listed above it, which is the healthy direction.
22→13 Clockwork uses DataSource✕
- Connections
- 1 pair of types, where a type in Clockwork uses a type in DataSource.
- The types involved
Clockwork.Clockwork→Clockwork.DataSource.DataSourceInterface
- Direction
- Clockwork uses DataSource, so a change to DataSource can break Clockwork, while a change to Clockwork can't break DataSource.
- Position
- Below the diagonal: Clockwork uses a module listed above it, which is the healthy direction.
22→15 Clockwork uses Storage✕
- Connections
- 1 pair of types, where a type in Clockwork uses a type in Storage.
- The types involved
Clockwork.Clockwork→Clockwork.Storage.StorageInterface
- Direction
- Clockwork uses Storage, so a change to Storage can break Clockwork, while a change to Clockwork can't break Storage.
- Position
- Below the diagonal: Clockwork uses a module listed above it, which is the healthy direction.
23→3 DataSource.Concerns uses Request✕
- Connections
- 1 pair of types, where a type in DataSource.Concerns uses a type in Request.
- The types involved
Clockwork.DataSource.Concerns.EloquentDetectDuplicateQueries→Clockwork.Request.Request
- Direction
- DataSource.Concerns uses Request, so a change to Request can break DataSource.Concerns, while a change to DataSource.Concerns can't break Request.
- Position
- Below the diagonal: DataSource.Concerns uses a module listed above it, which is the healthy direction.
23→14 DataSource.Concerns uses Helpers✕
- Connections
- 1 pair of types, where a type in DataSource.Concerns uses a type in Helpers.
- The types involved
Clockwork.DataSource.Concerns.EloquentDetectDuplicateQueries→Clockwork.Helpers.StackTrace
- Direction
- DataSource.Concerns uses Helpers, so a change to Helpers can break DataSource.Concerns, while a change to DataSource.Concerns can't break Helpers.
- Position
- Below the diagonal: DataSource.Concerns uses a module listed above it, which is the healthy direction.
24→13 Support.Laravel.Eloquent uses DataSource✕
- Connections
- 2 pairs of types, where a type in Support.Laravel.Eloquent uses a type in DataSource.
- The types involved
Clockwork.Support.Laravel.Eloquent.ResolveModelLegacyScope→Clockwork.DataSource.EloquentDataSourceClockwork.Support.Laravel.Eloquent.ResolveModelScope→Clockwork.DataSource.EloquentDataSource
- Direction
- Support.Laravel.Eloquent uses DataSource, so a change to DataSource can break Support.Laravel.Eloquent, while a change to Support.Laravel.Eloquent can't break DataSource.
- Position
- Below the diagonal: Support.Laravel.Eloquent uses a module listed above it, which is the healthy direction.
25→22 Support.Laravel uses Clockwork✕
- Connections
- 1 pair of types, where a type in Support.Laravel uses a type in Clockwork.
- The types involved
Clockwork.Support.Laravel.ClockworkController→Clockwork.Clockwork
- Direction
- Support.Laravel uses Clockwork, so a change to Clockwork can break Support.Laravel, while a change to Support.Laravel can't break Clockwork.
- Position
- Below the diagonal: Support.Laravel uses a module listed above it, which is the healthy direction.
26→22 Support.Slim.Old uses Clockwork✕
- Connections
- 1 pair of types, where a type in Support.Slim.Old uses a type in Clockwork.
- The types involved
Clockwork.Support.Slim.Old.ClockworkLogWriter→Clockwork.Clockwork
- Direction
- Support.Slim.Old uses Clockwork, so a change to Clockwork can break Support.Slim.Old, while a change to Support.Slim.Old can't break Clockwork.
- Position
- Below the diagonal: Support.Slim.Old uses a module listed above it, which is the healthy direction.
27→3 Support.Symfony uses Request✕
- Connections
- 1 pair of types, where a type in Support.Symfony uses a type in Request.
- The types involved
Clockwork.Support.Symfony.ProfileTransformer→Clockwork.Request.Request
- Direction
- Support.Symfony uses Request, so a change to Request can break Support.Symfony, while a change to Support.Symfony can't break Request.
- Position
- Below the diagonal: Support.Symfony uses a module listed above it, which is the healthy direction.
27→22 Support.Symfony uses Clockwork✕
- Connections
- 1 pair of types, where a type in Support.Symfony uses a type in Clockwork.
- The types involved
Clockwork.Support.Symfony.ClockworkController→Clockwork.Clockwork
- Direction
- Support.Symfony uses Clockwork, so a change to Clockwork can break Support.Symfony, while a change to Support.Symfony can't break Clockwork.
- Position
- Below the diagonal: Support.Symfony uses a module listed above it, which is the healthy direction.
28→22 Support.Lumen uses Clockwork✕
- Connections
- 1 pair of types, where a type in Support.Lumen uses a type in Clockwork.
- The types involved
Clockwork.Support.Lumen.Controller→Clockwork.Clockwork
- Direction
- Support.Lumen uses Clockwork, so a change to Clockwork can break Support.Lumen, while a change to Support.Lumen can't break Clockwork.
- Position
- Below the diagonal: Support.Lumen uses a module listed above it, which is the healthy direction.
28→25 Support.Lumen uses Support.Laravel✕
- Connections
- 2 pairs of types, where a type in Support.Lumen uses a type in Support.Laravel.
- The types involved
Clockwork.Support.Lumen.ClockworkServiceProvider→Clockwork.Support.Laravel.ClockworkServiceProviderClockwork.Support.Lumen.ClockworkSupport→Clockwork.Support.Laravel.ClockworkSupport
- Direction
- Support.Lumen uses Support.Laravel, so a change to Support.Laravel can break Support.Lumen, while a change to Support.Lumen can't break Support.Laravel.
- Position
- Below the diagonal: Support.Lumen 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
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; 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; Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a CI workflow that builds and runs the test suite on every push/PR. | +10.4 pts | Medium | CI/CD gates |
| 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.0 pts | Medium | Architecture documentation |
| Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive. | +3.6 pts | Medium | Nullable reference types |
| Resolve the 13 Orphaned file finding(s) in Knowledge Freshness — start with SqlStorage.php, ProfileTransformer.php, SqlSearch.php. | +2.8 pts | Medium | Knowledge Freshness |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.2 pts | Low | Bus Factor |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +2.1 pts | Medium | Documentation (README) |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +0.2 pts | Low | Knowledge Freshness |
| Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with Serializer.normalize (cognitive 25), Search.matchesNumber (cognitive 18). | +0.3 pts | Medium | Cognitive Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| Clockwork/Support/Slim/ClockworkMiddleware.php | 7.0 | Mixed | Code Duplication: Edited copy of a member (20 corresponding lines) |
| Clockwork/DataSource/LaravelDataSource.php | 7.1 | Mixed | Code Duplication: Edited copy of a member (20 corresponding lines) |
| Clockwork/Storage/RedisStorage.php | 7.2 | Mixed | Code Duplication: Edited copy of a member (14 corresponding lines) |
| Clockwork/Support/Laravel/ClockworkSupport.php | 7.4 | Mixed | God Classes: TooManyMethods: ClockworkSupport |
| Clockwork/Storage/SqlStorage.php | 7.4 | Mixed | Code Duplication: Edited copy of a member (12 corresponding lines) |
| Clockwork/Helpers/Serializer.php | 7.8 | Mixed | Cyclomatic Complexity: Serializer.normalize (cyclomatic 22) |
| Clockwork/Storage/Search.php | 7.8 | Mixed | Cognitive Complexity: Search.matchesNumber (cognitive 18) |
| Clockwork/Support/Vanilla/Clockwork.php | 7.8 | Mixed | God Classes: TooManyMethods: Clockwork |
| Clockwork/DataSource/PhpDataSource.php | 7.8 | Mixed | Code Duplication: Edited copies of one member (3 members, 16+ corresponding lines) |
| Clockwork/Support/Laravel/ClockworkController.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (7 corresponding lines) |
| Clockwork/Request/Request.php | 8.5 | Near-clean | God Classes: TooManyMethods: Request |
| Clockwork/Support/Vanilla/ClockworkMiddleware.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (6 corresponding lines) |
| Clockwork/Support/Doctrine/Legacy/Logger.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (10 corresponding lines) |
| Clockwork/DataSource/LaravelQueueDataSource.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (9 corresponding lines) |
| Clockwork/Support/Laravel/ClockworkMiddleware.php | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| Clockwork/Storage/SqlSearch.php | 8.5 | Near-clean | Code Duplication: Duplicated block (11–12 lines × 2) |
| Clockwork/Support/Laravel/Console/CapturingLegacyFormatter.php | 8.5 | Near-clean | Code Duplication: Duplicated block (54 lines × 2) |
| Clockwork/Request/ShouldCollect.php | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| Clockwork/Clockwork.php | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: Clockwork (LCOM4 4) |
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 33 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 33 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, 55 of 62 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.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.
- D12 Dependency Hygiene — 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 repository's dependency manifest (composer.json) was found, but this pass cannot parse it for hygiene, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D30 wherever the manifest is OSV-readable.
- D14 License Compliance — 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. Not scored — this repository declares a composer.json but commits no composer.lock this pass can read, so the set of packages it installs is not on disk: its composer.json states version CONSTRAINTS, and Composer's guidance is that a library leaves the lock uncommitted. Producing the graph needs Composer's solver, which this pass does not run, and grading whichever release happens to be newest today would be a verdict about a dependency graph nobody resolved. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (composer.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- 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.
- D26 Project Cohesion — 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. `(repository root)` (8570 LoC, 95 module-visible types across 28 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Laravel's service container and Symfony DependencyInjection, whose lifetimes are not modelled 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.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'PDO' is imported (Clockwork/Storage/SqlStorage.php:112), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'PDO' is imported (Clockwork/Storage/SqlStorage.php:112), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'PDO' is imported (Clockwork/Storage/SqlStorage.php:112), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'PDO' is imported (Clockwork/Storage/SqlStorage.php:112), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's PHP 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 the 1 JavaScript/TypeScript file(s) found looked minified or bundled, which this check does not read, 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.
- 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").
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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.
- 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
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Serializer.normalize at 22.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with Serializer.normalize (cyclomatic 22). — Refactoring it lifts Cyclomatic Complexity from 9.5 to about 10.0/10.
D2 · Cognitive Complexity
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was Serializer.normalize at 25.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with Serializer.normalize (cognitive 25), Search.matchesNumber (cognitive 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 3 TooManyMethods finding(s) in God Classes — start with ClockworkSupport.php, Request.php, Clockwork.php. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
12 duplicated block group(s) detected. 6.0 % of the production lines (549 of 9,164) are in a reported copy. A further 22 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 2 Edited copy of a member (20 corresponding lines) finding(s) in Code Duplication — start with ClockworkMiddleware.php, LaravelDataSource.php. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with ClockworkMiddleware.php, RedisStorage.php. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with Clockwork.php, ClockworkController.php. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
1 of 56 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with Clockwork.php. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Clockwork/Support/Laravel/ClockworkSupport.php. Counted over 37 of the 100 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
0 deducted task-comment markers across 9164 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. 1 document(s) read across 1 unit(s).
D27 · Navigability
8 % of calls cross a namespace and 0 % go through an interface, but 43 % 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)
semgrep found no security issues. semgrep hit a parse error in 1 file(s) — `Clockwork/Web/public/assets/index-159S-Gz-.js` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
D34 · Knowledge Freshness
13 of 37 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Clockwork/Storage/SqlStorage.php. Counted over 37 of the 100 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 13 Orphaned file finding(s) in Knowledge Freshness — start with SqlStorage.php, ProfileTransformer.php, SqlSearch.php. — One of this dimension's main actionable groups (13 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add phpstan or psalm (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Run what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X4 · Structured logging
X5 · Nullable reference types
- This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70.8 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 97.0 | Exemplary | Solid. |
| Maturity | 51.0 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 36.0 | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100.0 | Checked 2 of 8 | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'PDO' (Clockwork/Storage/SqlStorage.php:112) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'PDO' (Clockwork/Storage/SqlStorage.php:112) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'PDO' (Clockwork/Storage/SqlStorage.php:112) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- 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 — 76 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: 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
- 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 — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: this repository stores data through 'PDO' (Clockwork/Storage/SqlStorage.php:112) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- 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.
- D10 Test Quality — ~157 lines of test source are present (.php) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
- D14 License Compliance — Composer package licences not graded — this repository commits no composer.lock and this pass does not run Composer's solver
- 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 — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .php, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- 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, Scala, Rust and Java, 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
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repository's JavaScript/TypeScript, PHP source (2 module(s), 103 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 — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript, PHP source (service entry point: Clockwork/Support/Symfony/ClockworkController.php:8 (extends AbstractController))
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X14 Bypassable address classification — not 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
- 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
- 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 was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- 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
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- 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
- 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.
- 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)
Serious — 42 finding(s)
- TooManyMethods: ClockworkSupport Clockwork/Support/Laravel/ClockworkSupport.php:19
- TooManyMethods: Request Clockwork/Request/Request.php:6
- TooManyMethods: Clockwork Clockwork/Support/Vanilla/Clockwork.php:14
- Edited copy of a member (20 corresponding lines) Clockwork/Support/Slim/ClockworkMiddleware.php:59
- Edited copy of a member (20 corresponding lines) Clockwork/DataSource/LaravelDataSource.php:104
- Edited copy of a member (14 corresponding lines) Clockwork/Support/Slim/ClockworkMiddleware.php:34
- Edited copy of a member (14 corresponding lines) Clockwork/Storage/RedisStorage.php:147
- Edited copy of a member (7 corresponding lines) Clockwork/Support/Vanilla/Clockwork.php:91
- Edited copy of a member (7 corresponding lines) Clockwork/Support/Laravel/ClockworkController.php:16
- Edited copy of a member (9 corresponding lines) Clockwork/Support/Laravel/ClockworkSupport.php:263
- Edited copy of a member (9 corresponding lines) Clockwork/DataSource/LaravelQueueDataSource.php:69
- Edited copy of a member (3 corresponding lines) Clockwork/DataSource/LaravelDataSource.php:192
- Edited copy of a member (3 corresponding lines) Clockwork/Support/Slim/ClockworkMiddleware.php:52
- Edited copy of a member (5 corresponding lines) Clockwork/Storage/RedisStorage.php:249
- Edited copy of a member (5 corresponding lines) Clockwork/Support/Laravel/ClockworkController.php:28
- Duplicated block (5 lines × 2) Clockwork/Storage/RedisStorage.php:157
- Duplicated block (5 lines × 2) Clockwork/Request/ShouldCollect.php:114
- Serializer.normalize (cyclomatic 22) Clockwork/Helpers/Serializer.php:44
- Serializer.normalize (cognitive 25) Clockwork/Helpers/Serializer.php:44
- Search.matchesNumber (cognitive 18) Clockwork/Storage/Search.php:135
- Edited copy of a member (27 corresponding lines) Clockwork/Support/Laravel/ClockworkSupport.php:96
- Edited copy of a member (17 corresponding lines) Clockwork/Support/Slim/ClockworkMiddleware.php:83
- Edited copy of a member (13 corresponding lines) Clockwork/DataSource/LaravelDataSource.php:46
- Edited copy of a member (11 corresponding lines) Clockwork/Storage/RedisStorage.php:114
- Edited copies of one member (3 members, 16+ corresponding lines) Clockwork/DataSource/PhpDataSource.php:65
- Edited copy of a member (12 corresponding lines) Clockwork/Storage/SqlStorage.php:183
- Edited copies of one member (4 members, 5+ corresponding lines) Clockwork/Storage/SqlStorage.php:120
- Edited copies of one member (3 members, 5+ corresponding lines) Clockwork/Storage/Search.php:70
- Edited copy of a member (6 corresponding lines) Clockwork/Support/Vanilla/ClockworkMiddleware.php:64
- Edited copy of a member (10 corresponding lines) Clockwork/Support/Doctrine/Legacy/Logger.php:73
- Duplicated block (15 lines × 2) Clockwork/DataSource/LaravelDataSource.php:109
- Duplicated block (13 lines × 2) Clockwork/DataSource/LaravelDataSource.php:86
- Duplicated block (9–11 lines × 2) Clockwork/Support/Slim/ClockworkMiddleware.php:68
- Duplicated block (11 lines × 2) Clockwork/Support/Slim/ClockworkMiddleware.php:83
- Duplicated block (10 lines × 2) Clockwork/Support/Laravel/ClockworkMiddleware.php:21
- Duplicated block (9 lines × 3) Clockwork/Support/Slim/ClockworkMiddleware.php:68
- Duplicated block (9 lines × 2) Clockwork/DataSource/PhpDataSource.php:65
- Duplicated block (11–12 lines × 2) Clockwork/Storage/SqlSearch.php:74
- Duplicated block (8 lines × 2) Clockwork/Storage/SqlStorage.php:153
- Duplicated block (54 lines × 2) Clockwork/Support/Laravel/Console/CapturingLegacyFormatter.php:14
- Low cohesion: Clockwork (LCOM4 4) Clockwork/Clockwork.php:11
- No CI pipeline
Minor — 20 finding(s)
- Orphaned file Clockwork/Storage/SqlStorage.php:1
- Orphaned file Clockwork/Support/Symfony/ProfileTransformer.php:1
- Orphaned file Clockwork/Storage/SqlSearch.php:1
- Orphaned file Clockwork/Storage/Search.php:1
- Orphaned file Clockwork/DataSource/PhpDataSource.php:1
- Orphaned file Clockwork/DataSource/LaravelEventsDataSource.php:1
- Orphaned file Clockwork/Helpers/StackFilter.php:1
- Orphaned file Clockwork/Support/Slim/ClockworkMiddleware.php:1
- Orphaned file Clockwork/Helpers/StackTrace.php:1
- Orphaned file Clockwork/DataSource/PsrMessageDataSource.php:1
- Orphaned file Clockwork/Support/Symfony/ClockworkSupport.php:1
- Orphaned file Clockwork/DataSource/SlimDataSource.php:1
- Orphaned file Clockwork/Support/Lumen/Controller.php:1
- Off-boarding risk: anonymized user #1
- Orphaned files with no living knowledge
- No ADRs
- No architecture diagram/doc
- No SAST
- Duplicated predicate Clockwork/DataSource/LaravelDataSource.php:113
- PHP static analysis does not check null everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-8f6edfd3f7e9496f8cab1ce1acbe8376/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-8f6edfd3f7e9496f8cab1ce1acbe8376/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=281" --report-format json --report-path /tmp/watchdog-gitleaks-8f6edfd3f7e9496f8cab1ce1acbe8376/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8f6edfd3f7e9496f8cab1ce1acbe8376/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet). | 0 | — |