Executive summary
spatie/laravel-backup falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 58.2 out of 100 and is rated Adequate, and 15 of its 17 critical findings are security problems.
Code Health, at 47.9, is the weakest lens and counts most in the score. The best first step is raising the type checker to a stricter level, worth about 8.4 points. Writing log messages as searchable templates comes next, worth about 6.1 points. Raising Code Health to 70 would lift the score to about 67.1.
Twelve pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one password or key is open to anyone who can read the repository. Pinning each tool to an exact version, setting a waiting period for automatic updates and replacing the exposed password or key would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed. The loop of parts of the code that depend on each other needs breaking by moving the shared parts into a project of their own.
The product code is 5,146 lines, about €7,900 to rebuild.
If Code Health rose from 47.9 to 70, the lowest score rated Strong, the score would rise from 58.2 to about 67.1.
New since the last survey: 12 findings
- Cognitive Complexity · Manifest.addFiles (cognitive 18) src/Tasks/Backup/Manifest.php
- Code Duplication · Edited copies of one member (6 members, 10+ corresponding lines) src/Notifications/Notifications/BackupHasFailedNotification.php
- Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) src/Notifications/Notifications/BackupWasSuccessfulNotification.php
- Code Duplication · Edited copy of a member (8 corresponding lines) src/Notifications/Notifications/HealthyBackupWasFoundNotification.php
- Coupling · Circular dependency config/backup.php
- Coupling · Unstable project src/Commands
- Coupling · Off the main sequence: src/Support
- Coupling · Off the main sequence: src/Traits
- Coupling · Off the main sequence: src/Exceptions
- Coupling · Off the main sequence: src/Events
- Coupling · Off the main sequence: src/Helpers
- Exception handling · Swallowed exception (empty catch) src/BackupDestination/BackupDestination.php
Fixed since the last survey: 1 finding
- Code Duplication · Duplicated block (15 lines × 2) src/Commands/BackupCommand.php
Rebuild cost: about €7,900 · Estimate
| Cost to rebuild | €2,600 to €13,000, for 44 to 138 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 58. 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: 5,146 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Spatie.Backup | 2 Spatie.Backup.Enums | 3 Spatie.Backup.Helpers | 4 Spatie.Backup.Support | 5 Spatie.Backup.Traits | 6 Spatie.Backup.Config | 7 src.Helpers | 8 Spatie.Backup.BackupDestination | 9 Spatie.Backup.Notifications | 10 Spatie.Backup.Tasks.Backup | 11 Spatie.Backup.Events | 12 Spatie.Backup.Exceptions | 13 Spatie.Backup.Notifications.Channels.Discord | 14 Spatie.Backup.Notifications.Channels.Webhook | 15 Spatie.Backup.Tasks.Cleanup | 16 Spatie.Backup.Tasks.Monitor | 17 Spatie.Backup.Commands | 18 Spatie.Backup.Listeners | 19 Spatie.Backup.Notifications.Notifications | 20 Spatie.Backup.Tasks.Cleanup.Strategies | 21 Spatie.Backup.Tasks.Monitor.HealthChecks |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Spatie.Backup | |||||||||||||||||||||
| 2 Spatie.Backup.Enums | |||||||||||||||||||||
| 3 Spatie.Backup.Helpers | |||||||||||||||||||||
| 4 Spatie.Backup.Support | |||||||||||||||||||||
| 5 Spatie.Backup.Traits | |||||||||||||||||||||
| 6 Spatie.Backup.Config | 2 | 15 | |||||||||||||||||||
| 7 src.Helpers | 1 | ||||||||||||||||||||
| 8 Spatie.Backup.BackupDestination | 1 | ||||||||||||||||||||
| 9 Spatie.Backup.Notifications | 2 | ||||||||||||||||||||
| 10 Spatie.Backup.Tasks.Backup | 4 | ||||||||||||||||||||
| 11 Spatie.Backup.Events | 1 | ||||||||||||||||||||
| 12 Spatie.Backup.Exceptions | 2 | ||||||||||||||||||||
| 13 Spatie.Backup.Notifications.Channels.Discord | 1 | ||||||||||||||||||||
| 14 Spatie.Backup.Notifications.Channels.Webhook | 1 | ||||||||||||||||||||
| 15 Spatie.Backup.Tasks.Cleanup | 1 | 2 | |||||||||||||||||||
| 16 Spatie.Backup.Tasks.Monitor | 1 | 2 | |||||||||||||||||||
| 17 Spatie.Backup.Commands | 5 | 1 | 1 | 1 | |||||||||||||||||
| 18 Spatie.Backup.Listeners | 1 | 1 | |||||||||||||||||||
| 19 Spatie.Backup.Notifications.Notifications | 6 | 6 | 6 | ||||||||||||||||||
| 20 Spatie.Backup.Tasks.Cleanup.Strategies | 2 | 1 | |||||||||||||||||||
| 21 Spatie.Backup.Tasks.Monitor.HealthChecks | 4 | 3 |
6→2 Spatie.Backup.Config uses Spatie.Backup.Enums✕
- Connections
- 2 pairs of types, where a type in Spatie.Backup.Config uses a type in Spatie.Backup.Enums.
- The types involved
Spatie.Backup.Config.BackupConfig→Spatie.Backup.Enums.DumpFilenameBaseSpatie.Backup.Config.BackupConfig→Spatie.Backup.Enums.Encryption
- Direction
- Spatie.Backup.Config uses Spatie.Backup.Enums, so a change to Spatie.Backup.Enums can break Spatie.Backup.Config, while a change to Spatie.Backup.Config can't break Spatie.Backup.Enums.
- Position
- Below the diagonal: Spatie.Backup.Config uses a module listed above it, which is the healthy direction.
6→4 Spatie.Backup.Config uses Spatie.Backup.Support✕
- Connections
- 15 pairs of types, where a type in Spatie.Backup.Config uses a type in Spatie.Backup.Support.
- The types involved
Spatie.Backup.Config.BackupConfig→Spatie.Backup.Support.DataSpatie.Backup.Config.CleanupConfig→Spatie.Backup.Support.DataSpatie.Backup.Config.Config→Spatie.Backup.Support.DataSpatie.Backup.Config.DestinationConfig→Spatie.Backup.Support.DataSpatie.Backup.Config.MonitoredBackupConfig→Spatie.Backup.Support.DataSpatie.Backup.Config.MonitoredBackupsConfig→Spatie.Backup.Support.DataSpatie.Backup.Config.NotificationDiscordConfig→Spatie.Backup.Support.DataSpatie.Backup.Config.NotificationMailConfig→Spatie.Backup.Support.DataSpatie.Backup.Config.NotificationMailSenderConfig→Spatie.Backup.Support.DataSpatie.Backup.Config.NotificationSlackConfig→Spatie.Backup.Support.DataSpatie.Backup.Config.NotificationWebhookConfig→Spatie.Backup.Support.DataSpatie.Backup.Config.NotificationsConfig→Spatie.Backup.Support.DataSpatie.Backup.Config.SourceConfig→Spatie.Backup.Support.DataSpatie.Backup.Config.SourceFilesConfig→Spatie.Backup.Support.DataSpatie.Backup.Config.StrategyConfig→Spatie.Backup.Support.Data
- Direction
- Spatie.Backup.Config uses Spatie.Backup.Support, so a change to Spatie.Backup.Support can break Spatie.Backup.Config, while a change to Spatie.Backup.Config can't break Spatie.Backup.Support.
- Position
- Below the diagonal: Spatie.Backup.Config uses a module listed above it, which is the healthy direction.
7→4 src.Helpers uses Spatie.Backup.Support✕
- Connections
- 1 pair of types, where a type in src.Helpers uses a type in Spatie.Backup.Support.
- The types involved
src.Helpers.functions→Spatie.Backup.Support.BackupLogger
- Direction
- src.Helpers uses Spatie.Backup.Support, so a change to Spatie.Backup.Support can break src.Helpers, while a change to src.Helpers can't break Spatie.Backup.Support.
- Position
- Below the diagonal: src.Helpers uses a module listed above it, which is the healthy direction.
8→6 Spatie.Backup.BackupDestination uses Spatie.Backup.Config✕
- Connections
- 1 pair of types, where a type in Spatie.Backup.BackupDestination uses a type in Spatie.Backup.Config.
- The types involved
Spatie.Backup.BackupDestination.BackupDestinationFactory→Spatie.Backup.Config.Config
- Direction
- Spatie.Backup.BackupDestination uses Spatie.Backup.Config, so a change to Spatie.Backup.Config can break Spatie.Backup.BackupDestination, while a change to Spatie.Backup.BackupDestination can't break Spatie.Backup.Config.
- Position
- Below the diagonal: Spatie.Backup.BackupDestination uses a module listed above it, which is the healthy direction.
9→6 Spatie.Backup.Notifications uses Spatie.Backup.Config✕
- Connections
- 2 pairs of types, where a type in Spatie.Backup.Notifications uses a type in Spatie.Backup.Config.
- The types involved
Spatie.Backup.Notifications.BaseNotification→Spatie.Backup.Config.ConfigSpatie.Backup.Notifications.Notifiable→Spatie.Backup.Config.Config
- Direction
- Spatie.Backup.Notifications uses Spatie.Backup.Config, so a change to Spatie.Backup.Config can break Spatie.Backup.Notifications, while a change to Spatie.Backup.Notifications can't break Spatie.Backup.Config.
- Position
- Below the diagonal: Spatie.Backup.Notifications uses a module listed above it, which is the healthy direction.
10→6 Spatie.Backup.Tasks.Backup uses Spatie.Backup.Config✕
- Connections
- 4 pairs of types, where a type in Spatie.Backup.Tasks.Backup uses a type in Spatie.Backup.Config.
- The types involved
Spatie.Backup.Tasks.Backup.BackupJob→Spatie.Backup.Config.ConfigSpatie.Backup.Tasks.Backup.BackupJobFactory→Spatie.Backup.Config.ConfigSpatie.Backup.Tasks.Backup.BackupJobFactory→Spatie.Backup.Config.SourceFilesConfigSpatie.Backup.Tasks.Backup.Zip→Spatie.Backup.Config.Config
- Direction
- Spatie.Backup.Tasks.Backup uses Spatie.Backup.Config, so a change to Spatie.Backup.Config can break Spatie.Backup.Tasks.Backup, while a change to Spatie.Backup.Tasks.Backup can't break Spatie.Backup.Config.
- Position
- Below the diagonal: Spatie.Backup.Tasks.Backup uses a module listed above it, which is the healthy direction.
11→10 Spatie.Backup.Events uses Spatie.Backup.Tasks.Backup✕
- Connections
- 1 pair of types, where a type in Spatie.Backup.Events uses a type in Spatie.Backup.Tasks.Backup.
- The types involved
Spatie.Backup.Events.BackupManifestWasCreated→Spatie.Backup.Tasks.Backup.Manifest
- Direction
- Spatie.Backup.Events uses Spatie.Backup.Tasks.Backup, so a change to Spatie.Backup.Tasks.Backup can break Spatie.Backup.Events, while a change to Spatie.Backup.Events can't break Spatie.Backup.Tasks.Backup.
- Position
- Below the diagonal: Spatie.Backup.Events uses a module listed above it, which is the healthy direction.
12→8 Spatie.Backup.Exceptions uses Spatie.Backup.BackupDestination✕
- Connections
- 2 pairs of types, where a type in Spatie.Backup.Exceptions uses a type in Spatie.Backup.BackupDestination.
- The types involved
Spatie.Backup.Exceptions.BackupFailed→Spatie.Backup.BackupDestination.BackupDestinationSpatie.Backup.Exceptions.InvalidBackupFile→Spatie.Backup.BackupDestination.Backup
- Direction
- Spatie.Backup.Exceptions uses Spatie.Backup.BackupDestination, so a change to Spatie.Backup.BackupDestination can break Spatie.Backup.Exceptions, while a change to Spatie.Backup.Exceptions can't break Spatie.Backup.BackupDestination.
- Position
- Below the diagonal: Spatie.Backup.Exceptions uses a module listed above it, which is the healthy direction.
13→9 Spatie.Backup.Notifications.Channels.Discord uses Spatie.Backup.Notifications✕
- Connections
- 1 pair of types, where a type in Spatie.Backup.Notifications.Channels.Discord uses a type in Spatie.Backup.Notifications.
- The types involved
Spatie.Backup.Notifications.Channels.Discord.DiscordChannel→Spatie.Backup.Notifications.Notifiable
- Direction
- Spatie.Backup.Notifications.Channels.Discord uses Spatie.Backup.Notifications, so a change to Spatie.Backup.Notifications can break Spatie.Backup.Notifications.Channels.Discord, while a change to Spatie.Backup.Notifications.Channels.Discord can't break Spatie.Backup.Notifications.
- Position
- Below the diagonal: Spatie.Backup.Notifications.Channels.Discord uses a module listed above it, which is the healthy direction.
14→9 Spatie.Backup.Notifications.Channels.Webhook uses Spatie.Backup.Notifications✕
- Connections
- 1 pair of types, where a type in Spatie.Backup.Notifications.Channels.Webhook uses a type in Spatie.Backup.Notifications.
- The types involved
Spatie.Backup.Notifications.Channels.Webhook.WebhookChannel→Spatie.Backup.Notifications.Notifiable
- Direction
- Spatie.Backup.Notifications.Channels.Webhook uses Spatie.Backup.Notifications, so a change to Spatie.Backup.Notifications can break Spatie.Backup.Notifications.Channels.Webhook, while a change to Spatie.Backup.Notifications.Channels.Webhook can't break Spatie.Backup.Notifications.
- Position
- Below the diagonal: Spatie.Backup.Notifications.Channels.Webhook uses a module listed above it, which is the healthy direction.
15→6 Spatie.Backup.Tasks.Cleanup uses Spatie.Backup.Config✕
- Connections
- 1 pair of types, where a type in Spatie.Backup.Tasks.Cleanup uses a type in Spatie.Backup.Config.
- The types involved
Spatie.Backup.Tasks.Cleanup.CleanupStrategy→Spatie.Backup.Config.Config
- Direction
- Spatie.Backup.Tasks.Cleanup uses Spatie.Backup.Config, so a change to Spatie.Backup.Config can break Spatie.Backup.Tasks.Cleanup, while a change to Spatie.Backup.Tasks.Cleanup can't break Spatie.Backup.Config.
- Position
- Below the diagonal: Spatie.Backup.Tasks.Cleanup uses a module listed above it, which is the healthy direction.
15→8 Spatie.Backup.Tasks.Cleanup uses Spatie.Backup.BackupDestination✕
- Connections
- 2 pairs of types, where a type in Spatie.Backup.Tasks.Cleanup uses a type in Spatie.Backup.BackupDestination.
- The types involved
Spatie.Backup.Tasks.Cleanup.CleanupStrategy→Spatie.Backup.BackupDestination.BackupCollectionSpatie.Backup.Tasks.Cleanup.CleanupStrategy→Spatie.Backup.BackupDestination.BackupDestination
- Direction
- Spatie.Backup.Tasks.Cleanup uses Spatie.Backup.BackupDestination, so a change to Spatie.Backup.BackupDestination can break Spatie.Backup.Tasks.Cleanup, while a change to Spatie.Backup.Tasks.Cleanup can't break Spatie.Backup.BackupDestination.
- Position
- Below the diagonal: Spatie.Backup.Tasks.Cleanup uses a module listed above it, which is the healthy direction.
16→6 Spatie.Backup.Tasks.Monitor uses Spatie.Backup.Config✕
- Connections
- 1 pair of types, where a type in Spatie.Backup.Tasks.Monitor uses a type in Spatie.Backup.Config.
- The types involved
Spatie.Backup.Tasks.Monitor.BackupDestinationStatusFactory→Spatie.Backup.Config.MonitoredBackupsConfig
- Direction
- Spatie.Backup.Tasks.Monitor uses Spatie.Backup.Config, so a change to Spatie.Backup.Config can break Spatie.Backup.Tasks.Monitor, while a change to Spatie.Backup.Tasks.Monitor can't break Spatie.Backup.Config.
- Position
- Below the diagonal: Spatie.Backup.Tasks.Monitor uses a module listed above it, which is the healthy direction.
16→8 Spatie.Backup.Tasks.Monitor uses Spatie.Backup.BackupDestination✕
- Connections
- 2 pairs of types, where a type in Spatie.Backup.Tasks.Monitor uses a type in Spatie.Backup.BackupDestination.
- The types involved
Spatie.Backup.Tasks.Monitor.BackupDestinationStatus→Spatie.Backup.BackupDestination.BackupDestinationSpatie.Backup.Tasks.Monitor.HealthCheck→Spatie.Backup.BackupDestination.BackupDestination
- Direction
- Spatie.Backup.Tasks.Monitor uses Spatie.Backup.BackupDestination, so a change to Spatie.Backup.BackupDestination can break Spatie.Backup.Tasks.Monitor, while a change to Spatie.Backup.Tasks.Monitor can't break Spatie.Backup.BackupDestination.
- Position
- Below the diagonal: Spatie.Backup.Tasks.Monitor uses a module listed above it, which is the healthy direction.
17→6 Spatie.Backup.Commands uses Spatie.Backup.Config✕
- Connections
- 5 pairs of types, where a type in Spatie.Backup.Commands uses a type in Spatie.Backup.Config.
- The types involved
Spatie.Backup.Commands.BackupCommand→Spatie.Backup.Config.ConfigSpatie.Backup.Commands.BaseCommand→Spatie.Backup.Config.ConfigSpatie.Backup.Commands.CleanupCommand→Spatie.Backup.Config.ConfigSpatie.Backup.Commands.ListCommand→Spatie.Backup.Config.ConfigSpatie.Backup.Commands.MonitorCommand→Spatie.Backup.Config.Config
- Direction
- Spatie.Backup.Commands uses Spatie.Backup.Config, so a change to Spatie.Backup.Config can break Spatie.Backup.Commands, while a change to Spatie.Backup.Commands can't break Spatie.Backup.Config.
- Position
- Below the diagonal: Spatie.Backup.Commands uses a module listed above it, which is the healthy direction.
17→8 Spatie.Backup.Commands uses Spatie.Backup.BackupDestination✕
- Connections
- 1 pair of types, where a type in Spatie.Backup.Commands uses a type in Spatie.Backup.BackupDestination.
- The types involved
Spatie.Backup.Commands.ListCommand→Spatie.Backup.BackupDestination.Backup
- Direction
- Spatie.Backup.Commands uses Spatie.Backup.BackupDestination, so a change to Spatie.Backup.BackupDestination can break Spatie.Backup.Commands, while a change to Spatie.Backup.Commands can't break Spatie.Backup.BackupDestination.
- Position
- Below the diagonal: Spatie.Backup.Commands uses a module listed above it, which is the healthy direction.
17→15 Spatie.Backup.Commands uses Spatie.Backup.Tasks.Cleanup✕
- Connections
- 1 pair of types, where a type in Spatie.Backup.Commands uses a type in Spatie.Backup.Tasks.Cleanup.
- The types involved
Spatie.Backup.Commands.CleanupCommand→Spatie.Backup.Tasks.Cleanup.CleanupStrategy
- Direction
- Spatie.Backup.Commands uses Spatie.Backup.Tasks.Cleanup, so a change to Spatie.Backup.Tasks.Cleanup can break Spatie.Backup.Commands, while a change to Spatie.Backup.Commands can't break Spatie.Backup.Tasks.Cleanup.
- Position
- Below the diagonal: Spatie.Backup.Commands uses a module listed above it, which is the healthy direction.
17→16 Spatie.Backup.Commands uses Spatie.Backup.Tasks.Monitor✕
- Connections
- 1 pair of types, where a type in Spatie.Backup.Commands uses a type in Spatie.Backup.Tasks.Monitor.
- The types involved
Spatie.Backup.Commands.ListCommand→Spatie.Backup.Tasks.Monitor.BackupDestinationStatus
- Direction
- Spatie.Backup.Commands uses Spatie.Backup.Tasks.Monitor, so a change to Spatie.Backup.Tasks.Monitor can break Spatie.Backup.Commands, while a change to Spatie.Backup.Commands can't break Spatie.Backup.Tasks.Monitor.
- Position
- Below the diagonal: Spatie.Backup.Commands uses a module listed above it, which is the healthy direction.
18→6 Spatie.Backup.Listeners uses Spatie.Backup.Config✕
- Connections
- 1 pair of types, where a type in Spatie.Backup.Listeners uses a type in Spatie.Backup.Config.
- The types involved
Spatie.Backup.Listeners.EncryptBackupArchive→Spatie.Backup.Config.Config
- Direction
- Spatie.Backup.Listeners uses Spatie.Backup.Config, so a change to Spatie.Backup.Config can break Spatie.Backup.Listeners, while a change to Spatie.Backup.Listeners can't break Spatie.Backup.Config.
- Position
- Below the diagonal: Spatie.Backup.Listeners uses a module listed above it, which is the healthy direction.
18→11 Spatie.Backup.Listeners uses Spatie.Backup.Events✕
- Connections
- 1 pair of types, where a type in Spatie.Backup.Listeners uses a type in Spatie.Backup.Events.
- The types involved
Spatie.Backup.Listeners.EncryptBackupArchive→Spatie.Backup.Events.BackupZipWasCreated
- Direction
- Spatie.Backup.Listeners uses Spatie.Backup.Events, so a change to Spatie.Backup.Events can break Spatie.Backup.Listeners, while a change to Spatie.Backup.Listeners can't break Spatie.Backup.Events.
- Position
- Below the diagonal: Spatie.Backup.Listeners uses a module listed above it, which is the healthy direction.
19→9 Spatie.Backup.Notifications.Notifications uses Spatie.Backup.Notifications✕
- Connections
- 6 pairs of types, where a type in Spatie.Backup.Notifications.Notifications uses a type in Spatie.Backup.Notifications.
- The types involved
Spatie.Backup.Notifications.Notifications.BackupHasFailedNotification→Spatie.Backup.Notifications.BaseNotificationSpatie.Backup.Notifications.Notifications.BackupWasSuccessfulNotification→Spatie.Backup.Notifications.BaseNotificationSpatie.Backup.Notifications.Notifications.CleanupHasFailedNotification→Spatie.Backup.Notifications.BaseNotificationSpatie.Backup.Notifications.Notifications.CleanupWasSuccessfulNotification→Spatie.Backup.Notifications.BaseNotificationSpatie.Backup.Notifications.Notifications.HealthyBackupWasFoundNotification→Spatie.Backup.Notifications.BaseNotificationSpatie.Backup.Notifications.Notifications.UnhealthyBackupWasFoundNotification→Spatie.Backup.Notifications.BaseNotification
- Direction
- Spatie.Backup.Notifications.Notifications uses Spatie.Backup.Notifications, so a change to Spatie.Backup.Notifications can break Spatie.Backup.Notifications.Notifications, while a change to Spatie.Backup.Notifications.Notifications can't break Spatie.Backup.Notifications.
- Position
- Below the diagonal: Spatie.Backup.Notifications.Notifications uses a module listed above it, which is the healthy direction.
19→11 Spatie.Backup.Notifications.Notifications uses Spatie.Backup.Events✕
- Connections
- 6 pairs of types, where a type in Spatie.Backup.Notifications.Notifications uses a type in Spatie.Backup.Events.
- The types involved
Spatie.Backup.Notifications.Notifications.BackupHasFailedNotification→Spatie.Backup.Events.BackupHasFailedSpatie.Backup.Notifications.Notifications.BackupWasSuccessfulNotification→Spatie.Backup.Events.BackupWasSuccessfulSpatie.Backup.Notifications.Notifications.CleanupHasFailedNotification→Spatie.Backup.Events.CleanupHasFailedSpatie.Backup.Notifications.Notifications.CleanupWasSuccessfulNotification→Spatie.Backup.Events.CleanupWasSuccessfulSpatie.Backup.Notifications.Notifications.HealthyBackupWasFoundNotification→Spatie.Backup.Events.HealthyBackupWasFoundSpatie.Backup.Notifications.Notifications.UnhealthyBackupWasFoundNotification→Spatie.Backup.Events.UnhealthyBackupWasFound
- Direction
- Spatie.Backup.Notifications.Notifications uses Spatie.Backup.Events, so a change to Spatie.Backup.Events can break Spatie.Backup.Notifications.Notifications, while a change to Spatie.Backup.Notifications.Notifications can't break Spatie.Backup.Events.
- Position
- Below the diagonal: Spatie.Backup.Notifications.Notifications uses a module listed above it, which is the healthy direction.
19→13 Spatie.Backup.Notifications.Notifications uses Spatie.Backup.Notifications.Channels.Discord✕
- Connections
- 6 pairs of types, where a type in Spatie.Backup.Notifications.Notifications uses a type in Spatie.Backup.Notifications.Channels.Discord.
- The types involved
Spatie.Backup.Notifications.Notifications.BackupHasFailedNotification→Spatie.Backup.Notifications.Channels.Discord.DiscordMessageSpatie.Backup.Notifications.Notifications.BackupWasSuccessfulNotification→Spatie.Backup.Notifications.Channels.Discord.DiscordMessageSpatie.Backup.Notifications.Notifications.CleanupHasFailedNotification→Spatie.Backup.Notifications.Channels.Discord.DiscordMessageSpatie.Backup.Notifications.Notifications.CleanupWasSuccessfulNotification→Spatie.Backup.Notifications.Channels.Discord.DiscordMessageSpatie.Backup.Notifications.Notifications.HealthyBackupWasFoundNotification→Spatie.Backup.Notifications.Channels.Discord.DiscordMessageSpatie.Backup.Notifications.Notifications.UnhealthyBackupWasFoundNotification→Spatie.Backup.Notifications.Channels.Discord.DiscordMessage
- Direction
- Spatie.Backup.Notifications.Notifications uses Spatie.Backup.Notifications.Channels.Discord, so a change to Spatie.Backup.Notifications.Channels.Discord can break Spatie.Backup.Notifications.Notifications, while a change to Spatie.Backup.Notifications.Notifications can't break Spatie.Backup.Notifications.Channels.Discord.
- Position
- Below the diagonal: Spatie.Backup.Notifications.Notifications uses a module listed above it, which is the healthy direction.
20→8 Spatie.Backup.Tasks.Cleanup.Strategies uses Spatie.Backup.BackupDestination✕
- Connections
- 2 pairs of types, where a type in Spatie.Backup.Tasks.Cleanup.Strategies uses a type in Spatie.Backup.BackupDestination.
- The types involved
Spatie.Backup.Tasks.Cleanup.Strategies.DefaultStrategy→Spatie.Backup.BackupDestination.BackupSpatie.Backup.Tasks.Cleanup.Strategies.DefaultStrategy→Spatie.Backup.BackupDestination.BackupCollection
- Direction
- Spatie.Backup.Tasks.Cleanup.Strategies uses Spatie.Backup.BackupDestination, so a change to Spatie.Backup.BackupDestination can break Spatie.Backup.Tasks.Cleanup.Strategies, while a change to Spatie.Backup.Tasks.Cleanup.Strategies can't break Spatie.Backup.BackupDestination.
- Position
- Below the diagonal: Spatie.Backup.Tasks.Cleanup.Strategies uses a module listed above it, which is the healthy direction.
20→15 Spatie.Backup.Tasks.Cleanup.Strategies uses Spatie.Backup.Tasks.Cleanup✕
- Connections
- 1 pair of types, where a type in Spatie.Backup.Tasks.Cleanup.Strategies uses a type in Spatie.Backup.Tasks.Cleanup.
- The types involved
Spatie.Backup.Tasks.Cleanup.Strategies.DefaultStrategy→Spatie.Backup.Tasks.Cleanup.CleanupStrategy
- Direction
- Spatie.Backup.Tasks.Cleanup.Strategies uses Spatie.Backup.Tasks.Cleanup, so a change to Spatie.Backup.Tasks.Cleanup can break Spatie.Backup.Tasks.Cleanup.Strategies, while a change to Spatie.Backup.Tasks.Cleanup.Strategies can't break Spatie.Backup.Tasks.Cleanup.
- Position
- Below the diagonal: Spatie.Backup.Tasks.Cleanup.Strategies uses a module listed above it, which is the healthy direction.
21→8 Spatie.Backup.Tasks.Monitor.HealthChecks uses Spatie.Backup.BackupDestination✕
- Connections
- 4 pairs of types, where a type in Spatie.Backup.Tasks.Monitor.HealthChecks uses a type in Spatie.Backup.BackupDestination.
- The types involved
Spatie.Backup.Tasks.Monitor.HealthChecks.IsReachable→Spatie.Backup.BackupDestination.BackupDestinationSpatie.Backup.Tasks.Monitor.HealthChecks.MaximumAgeInDays→Spatie.Backup.BackupDestination.BackupSpatie.Backup.Tasks.Monitor.HealthChecks.MaximumAgeInDays→Spatie.Backup.BackupDestination.BackupDestinationSpatie.Backup.Tasks.Monitor.HealthChecks.MaximumStorageInMegabytes→Spatie.Backup.BackupDestination.BackupDestination
- Direction
- Spatie.Backup.Tasks.Monitor.HealthChecks uses Spatie.Backup.BackupDestination, so a change to Spatie.Backup.BackupDestination can break Spatie.Backup.Tasks.Monitor.HealthChecks, while a change to Spatie.Backup.Tasks.Monitor.HealthChecks can't break Spatie.Backup.BackupDestination.
- Position
- Below the diagonal: Spatie.Backup.Tasks.Monitor.HealthChecks uses a module listed above it, which is the healthy direction.
21→16 Spatie.Backup.Tasks.Monitor.HealthChecks uses Spatie.Backup.Tasks.Monitor✕
- Connections
- 3 pairs of types, where a type in Spatie.Backup.Tasks.Monitor.HealthChecks uses a type in Spatie.Backup.Tasks.Monitor.
- The types involved
Spatie.Backup.Tasks.Monitor.HealthChecks.IsReachable→Spatie.Backup.Tasks.Monitor.HealthCheckSpatie.Backup.Tasks.Monitor.HealthChecks.MaximumAgeInDays→Spatie.Backup.Tasks.Monitor.HealthCheckSpatie.Backup.Tasks.Monitor.HealthChecks.MaximumStorageInMegabytes→Spatie.Backup.Tasks.Monitor.HealthCheck
- Direction
- Spatie.Backup.Tasks.Monitor.HealthChecks uses Spatie.Backup.Tasks.Monitor, so a change to Spatie.Backup.Tasks.Monitor can break Spatie.Backup.Tasks.Monitor.HealthChecks, while a change to Spatie.Backup.Tasks.Monitor.HealthChecks can't break Spatie.Backup.Tasks.Monitor.
- Position
- Below the diagonal: Spatie.Backup.Tasks.Monitor.HealthChecks uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 14 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: 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; Interpolated log message defeats structured logging; Swallowed exception (empty catch).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +8.4 pts | Medium | Nullable reference types |
| Interpolated log message defeats structured logging | +6.1 pts | Medium | Structured logging |
| Swallowed exception (empty catch) | +4.1 pts | Medium | Exception handling |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.9 pts | Low | Supply-chain Provenance & Signing |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +1.7 pts | Medium | Architecture documentation |
| Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. | +0.7 pts | Low | Secrets (history) |
| 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 Static Analysis (SAST) — start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Notifications/Notifications/BackupWasSuccessfulNotification.php | 7.2 | Mixed | Code Duplication: Edited copies of one member (4 members, 12+ corresponding lines) |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Notifications/Notifications/BackupHasFailedNotification.php | 7.4 | Mixed | Code Duplication: Edited copies of one member (6 members, 10+ corresponding lines) |
| src/Commands/BackupCommand.php | 7.8 | Mixed | Cyclomatic Complexity: BackupCommand.handle (cyclomatic 19) |
| config/backup.php | 8.0 | Near-clean | Coupling: Circular dependency |
| src/Tasks/Backup/Zip.php | 8.5 | Near-clean | Cognitive Complexity: Zip.add (cognitive 20) |
| src/Tasks/Backup/Manifest.php | 8.5 | Near-clean | Cognitive Complexity: Manifest.addFiles (cognitive 18) |
| src/Notifications/Notifications/HealthyBackupWasFoundNotification.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (8 corresponding lines) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 37 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 37 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, 36 of 52 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. Not scored — 13 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- 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.
- 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.
- D32 Data Compliance (PII/GDPR) — 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. `src/Config/SourceFilesConfig.php` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- 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, 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.
- 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.
- 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.
- 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 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.
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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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 BackupCommand.handle at 19.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with BackupCommand.handle (cyclomatic 19). — Refactoring it lifts Cyclomatic Complexity from 9.7 to about 10.0/10.
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was BackupCommand.handle at 22.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with BackupCommand.handle (cognitive 22), Zip.add (cognitive 20), Manifest.addFiles (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 3 together lifts Cognitive Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
5 duplicated block group(s) detected. 2.7 % of the production lines (137 of 5,146) are in a reported copy. A further 3 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copies of one member (6 members, 10+ corresponding lines) finding(s) in Code Duplication — start with BackupHasFailedNotification.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copies of one member (4 members, 12+ corresponding lines) finding(s) in Code Duplication — start with BackupWasSuccessfulNotification.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with HealthyBackupWasFoundNotification.php. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
16 production modules (source-import), 1 dependency cycle(s), 1 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 5 module(s) off the main sequence, with abstractness counted on 12 of the 16 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 5 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 Circular dependency finding(s) in Coupling — start with backup.php. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Unstable project src/Commands finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 21 classes have LCOM4 above 3.
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
No source file's living knowledge is concentrated in a single author. Counted over 21 of the 84 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 5146 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. 30 document(s) read across 1 unit(s).
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
14 finding(s): 0 critical, 14 high, 0 medium, 0 low. 12 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `src/Config/SourceFilesConfig.php` (line 25) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 12 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (12 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
1 of 21 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Notifications/Channels/Discord/DiscordMessage.php. Counted over 21 of the 84 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 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 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
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 13 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
- The projects config → src/Notifications → src/Config → config (one cycle inside a mutually-dependent group of 7 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — config/backup.php:3
What to do
- Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
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.
P3 · Security & performance tooling
- `REDACTED` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
What to do
- Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — src/BackupDestination/BackupDestination.php:109, src/BackupDestination/BackupDestination.php:122
What to do
- Swallowed exception (empty catch)
X4 · Structured logging
- `log` at line 58 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->log(LogLevel::ERROR, 'Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::error('order moved', ['order_id' => $orderId])` with Laravel's facade. — src/Support/BackupLogger.php:58
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 0/1 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
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 | 47.9 | Weak — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 85.3 | Adequate — gated by D5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 66.8 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 66.8 | Adequate | Strongest area. |
| Security | 65.2 | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not evidenced — 1 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
Not included — 78 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: 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
- 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.
- D10 Test Quality — ~2385 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 — Not scored — 13 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- 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 — This repository is one build unit, `(repository root)` (3665 LoC, 83 module-visible types across 20 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's PHP source (1 module(s), 116 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 source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.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
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- 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 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. 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)
Critical — 17 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Project dependency cycle config/backup.php:3
- REDACTED
- REDACTED
- REDACTED
- Circular dependency config/backup.php:3
Serious — 25 finding(s)
- Off the main sequence: src/Support
- Off the main sequence: src/Traits
- Off the main sequence: src/Exceptions
- Off the main sequence: src/Events
- Off the main sequence: src/Helpers
- REDACTED
- REDACTED
- Swallowed exception (empty catch) src/BackupDestination/BackupDestination.php:109
- Swallowed exception (empty catch) src/BackupDestination/BackupDestination.php:122
- BackupCommand.handle (cyclomatic 19) src/Commands/BackupCommand.php:40
- BackupCommand.handle (cognitive 22) src/Commands/BackupCommand.php:40
- Zip.add (cognitive 20) src/Tasks/Backup/Zip.php:107
- Manifest.addFiles (cognitive 18) src/Tasks/Backup/Manifest.php:30
- REDACTED
- REDACTED
- Edited copies of one member (6 members, 10+ corresponding lines) src/Notifications/Notifications/BackupHasFailedNotification.php:20
- Edited copies of one member (4 members, 12+ corresponding lines) src/Notifications/Notifications/BackupWasSuccessfulNotification.php:34
- Edited copy of a member (8 corresponding lines) src/Notifications/Notifications/HealthyBackupWasFoundNotification.php:50
- Duplicated block (4–22 lines × 3) src/Notifications/Notifications/BackupHasFailedNotification.php:35
- Duplicated block (8 lines × 3) src/Notifications/Notifications/BackupWasSuccessfulNotification.php:34
- Duplicated block (7–8 lines × 2) src/Notifications/Notifications/BackupHasFailedNotification.php:61
- Duplicated block (2–7 lines × 3) src/Notifications/Notifications/BackupWasSuccessfulNotification.php:23
- Duplicated block (5 lines × 2) src/Notifications/Notifications/BackupWasSuccessfulNotification.php:50
- Unstable project src/Commands
- SAST runs, but gates no merge
Minor — 10 finding(s)
- REDACTED
- Orphaned files with no living knowledge
- Orphaned file src/Notifications/Channels/Discord/DiscordMessage.php:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- CI build step not evidenced
- Interpolated log message defeats structured logging src/Support/BackupLogger.php:58
- 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-a511786bcb0c478b8d5719b6626e8653/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-a511786bcb0c478b8d5719b6626e8653/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=712" --report-format json --report-path /tmp/watchdog-gitleaks-a511786bcb0c478b8d5719b6626e8653/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-a511786bcb0c478b8d5719b6626e8653/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 . | 14 | 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. semgrep could not parse 1 file(s) — `src/Config/SourceFilesConfig.php` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 | — |