Executive summary
robinebers/openusage meets our standard for a preview release. It scores 65 out of 100 and is rated Strong, and all 38 of its critical findings are security problems.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 4 points. Recording design decisions comes next, worth about 2 points.
Sixteen secrets can leak from the build pipeline. Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and four passwords or keys in the code's history and three in the code are open to anyone who can read the repository. Limiting each secret to its own step, pinning each tool to an exact version and replacing each exposed password or key would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and passing outside input through environment variables would deal with the pipeline step that puts outside input straight into a shell command.
The product code is 12,313 lines, about €27,000 to rebuild.
If Production Readiness rose from 62 to 62, the lowest score rated Strong, the score would rise from 65 to about 66.
New since the last survey: 30 findings
- Cyclomatic Complexity · AccountProviderRuntime.claimClaudeResetGrant (cyclomatic 17) Sources/OpenUsage/Providers/Claude/AccountProviderRuntime+ClaudeResets.swift
- Cyclomatic Complexity · MonitorView.viewDidMoveToWindow (cyclomatic 17) Sources/OpenUsage/Support/PopoverKeyReader.swift
- Cognitive Complexity · AccountProviderRuntime.claimClaudeResetGrant (cognitive 18) Sources/OpenUsage/Providers/Claude/AccountProviderRuntime+ClaudeResets.swift
- Cognitive Complexity · WireResource.init (cognitive 17) Sources/OpenUsage/Services/LimitsEnvelope.swift
- Cognitive Complexity · OAuthLoginSupport.swift.authorizationCode (cognitive 16) Sources/OpenUsage/Services/OAuthLoginSupport.swift
- God Classes · TooManyMethods: AccountProviderRuntime Sources/OpenUsage/Providers/AccountProviderRuntime.swift
- God Classes · MethodTooLong: AccountProviderRuntime.widgetDescriptors Sources/OpenUsage/Providers/AccountProviderRuntime+Descriptors.swift
- Code Duplication · Duplicated block (13 lines × 2) Sources/OpenUsage/Providers/Codex/CodexUsageClient.swift
- Code Duplication · Duplicated block (5 lines × 3) Sources/OpenUsage/Providers/AccountProviderRuntime+Descriptors.swift
- Code Duplication · Duplicated block (4–5 lines × 3) Sources/OpenUsage/Providers/AccountProviderRuntime+Descriptors.swift
- Code Duplication · Duplicated block (5 lines × 2) Sources/OpenUsage/Providers/Claude/AccountProviderRuntime+ClaudeResets.swift
- Cohesion (LCOM4) · Low cohesion: UpdaterController (LCOM4 4) Sources/OpenUsage/App/UpdaterController.swift
- Test Quality · No assertions: testAbsentArgonPreservesExistingFourBuckets Tests/OpenUsageTests/AntigravityArgonQuotaTests.swift
- Test Quality · No assertions: testUnavailableArgonPreservesSharedQuotas Tests/OpenUsageTests/AntigravityArgonQuotaTests.swift
- Test Quality · No assertions: testOnlyExplicitArgonWeeklyGroupCanPopulateTheRow Tests/OpenUsageTests/AntigravityArgonQuotaTests.swift
- Test Quality · No assertions: testAmbiguousWeeklyBucketsDoNotChooseOrMergeAQuota Tests/OpenUsageTests/AntigravityArgonQuotaTests.swift
- Test Quality · No assertions: testUnpinningAfterHoverOutHidesThePopover Tests/OpenUsageTests/HoverPopoverStateTests.swift
- Test Quality · No assertions: testClaudeRefusedRefreshTokenReadsAsExpiredSignIn Tests/OpenUsageTests/OAuthRefreshPersistenceTests.swift
- Test Quality · No assertions: testGrokRefusedRefreshTokenReadsAsExpiredSignIn Tests/OpenUsageTests/OAuthRefreshPersistenceTests.swift
- Test Quality · No assertions: testSuccessStatusesDoNotThrow Tests/OpenUsageTests/ProviderErrorTriageTests.swift
- Test Quality · No assertions: testRateLimitWithoutRetryAfterDoublesFromFiveMinutesToAnHour Tests/OpenUsageTests/RefreshBackoffTests.swift
- Test Quality · No assertions: testNoAnswerRetriesEveryPassWithoutGrowingTheWait Tests/OpenUsageTests/RefreshBackoffTests.swift
- REDACTED Scanning · REDACTED
- REDACTED Scanning · REDACTED
- REDACTED Scanning · REDACTED
- Secrets (history) · REDACTED
- Change Coupling · Change coupling: LiquidGlassFallbacks.swift ↔ DashboardView.swift Sources/OpenUsage/Support/LiquidGlassFallbacks.swift
- Exception handling · Swallowed exception (caught, then discarded) Sources/OpenUsage/Providers/Antigravity/AntigravityUsageMapper.swift
- Async & latency hygiene · Sync-over-async blocking Sources/OpenUsage/Providers/Claude/AccountProviderRuntime+ClaudeUsage.swift
- Async & latency hygiene · Sync-over-async blocking Sources/OpenUsage/Providers/Claude/AccountProviderRuntime+ClaudeUsage.swift
Fixed since the last survey: 164 findings
- Cyclomatic Complexity · SVGPath.parse (cyclomatic 54) Sources/OpenUsage/Support/ProviderIconShape.swift
- Cyclomatic Complexity · CodexLogFileParser.parse (cyclomatic 45) Sources/OpenUsage/Providers/Codex/CodexLogFileParser.swift
- Cyclomatic Complexity · ProviderAccountAssembly.assemble (cyclomatic 39) Sources/OpenUsage/Services/ProviderAccountAssembly.swift
- Cyclomatic Complexity · ClaudeProvider.refresh (cyclomatic 33) Sources/OpenUsage/Providers/Claude/ClaudeProvider.swift
- Cyclomatic Complexity · UsageHistoryDocument.validate (cyclomatic 30) Sources/OpenUsage/Models/UsageHistoryDocument.swift
- Cyclomatic Complexity · IncrementalJSONLScanner.items (cyclomatic 30) Sources/OpenUsage/Providers/IncrementalJSONLScanner.swift
- Cyclomatic Complexity · JSONLStreamingReader.read (cyclomatic 29) Sources/OpenUsage/Providers/JSONLStreamingReader.swift
- Cyclomatic Complexity · ClaudeLogUsageScanner.ownedUsageFiles (cyclomatic 27) Sources/OpenUsage/Providers/Claude/ClaudeLogUsageScanner.swift
- Cyclomatic Complexity · OpenSSHEd25519Key.parse (cyclomatic 25) Sources/OpenUsage/Providers/Ollama/OpenSSHEd25519Key.swift
- Cyclomatic Complexity · MonitorView.viewDidMoveToWindow (cyclomatic 24) Sources/OpenUsage/Support/PopoverDismissReader.swift
- Cyclomatic Complexity · PaceNotificationLogic.transitions (cyclomatic 22) Sources/OpenUsage/Support/PaceNotificationLogic.swift
- Cyclomatic Complexity · AntigravityProvider.probeCloudCode (cyclomatic 22) Sources/OpenUsage/Providers/Antigravity/AntigravityProvider.swift
- Cyclomatic Complexity · CursorSpendHistoryFetcher.refresh (cyclomatic 22) Sources/OpenUsage/Providers/Cursor/CursorSpendHistoryFetcher.swift
- Cyclomatic Complexity · WidgetDataStore.localHistoryDocument (cyclomatic 21) Sources/OpenUsage/Stores/WidgetDataStore.swift
- Cyclomatic Complexity · ProviderAccountAssembly.discoverDesktopOrganizations (cyclomatic 20) Sources/OpenUsage/Services/ProviderAccountDiscoveryReadout.swift
- Cyclomatic Complexity · ClaudeAuthStore.loadCredentialSet (cyclomatic 20) Sources/OpenUsage/Providers/Claude/ClaudeAuthStore.swift
- Cyclomatic Complexity · ProviderAccountAssembly.makeCodexCards (cyclomatic 19) Sources/OpenUsage/Services/ProviderAccountAssembly+Codex.swift
- Cyclomatic Complexity · AntigravityProvider.probeLS (cyclomatic 19) Sources/OpenUsage/Providers/Antigravity/AntigravityProvider.swift
- Cyclomatic Complexity · AntigravityProvider.fetchCloudCode (cyclomatic 18) Sources/OpenUsage/Providers/Antigravity/AntigravityProvider.swift
- Cyclomatic Complexity · ClaudeProvider.fetchLiveUsage (cyclomatic 18) Sources/OpenUsage/Providers/Claude/ClaudeProvider.swift
- Cyclomatic Complexity · CursorSpendHistoryFetcher.fetchDay (cyclomatic 18) Sources/OpenUsage/Providers/Cursor/CursorSpendHistoryFetcher.swift
- Cyclomatic Complexity · ClaudeSessionIdentity.parse (cyclomatic 17) Sources/OpenUsage/Providers/Claude/ClaudeSessionIdentity.swift
- Cyclomatic Complexity · CodexLogUsageScanner.aggregate (cyclomatic 17) Sources/OpenUsage/Providers/Codex/CodexLogUsageScanner+Pricing.swift
- Cyclomatic Complexity · OpenCodeCodexUsageScanner.scan (cyclomatic 17) Sources/OpenUsage/Providers/OpenCode/OpenCodeCodexUsageScanner.swift
- Cyclomatic Complexity · OpenUsageISO8601.normalizeFractionalISO (cyclomatic 16) Sources/OpenUsage/Support/OpenUsageISO8601.swift
- Cyclomatic Complexity · AntigravityProtoDecoder.field (cyclomatic 16) Sources/OpenUsage/Providers/Antigravity/AntigravityProtoDecoder.swift
- Cyclomatic Complexity · AntigravityProtoDecoder.generationEvent (cyclomatic 16) Sources/OpenUsage/Providers/Antigravity/AntigravityProtoDecoder.swift
- Cyclomatic Complexity · ClaudeLogUsageScanner.parseEntries (cyclomatic 16) Sources/OpenUsage/Providers/Claude/ClaudeLogUsageScanner.swift
- Cyclomatic Complexity · ClaudeSwapAccount.discover (cyclomatic 16) Sources/OpenUsage/Providers/Claude/ClaudeSwapAccount.swift
- Cyclomatic Complexity · OpenCodeProvider.refresh (cyclomatic 16) Sources/OpenUsage/Providers/OpenCode/OpenCodeProvider.swift
- Cognitive Complexity · CodexLogFileParser.parse (cognitive 73) Sources/OpenUsage/Providers/Codex/CodexLogFileParser.swift
- Cognitive Complexity · SVGPath.parse (cognitive 66) Sources/OpenUsage/Support/ProviderIconShape.swift
- Cognitive Complexity · ClaudeLogUsageScanner.ownedUsageFiles (cognitive 53) Sources/OpenUsage/Providers/Claude/ClaudeLogUsageScanner.swift
- Cognitive Complexity · UsageHistoryDocument.validate (cognitive 52) Sources/OpenUsage/Models/UsageHistoryDocument.swift
- Cognitive Complexity · JSONLStreamingReader.read (cognitive 48) Sources/OpenUsage/Providers/JSONLStreamingReader.swift
- Cognitive Complexity · CursorSpendHistoryFetcher.fetchDay (cognitive 47) Sources/OpenUsage/Providers/Cursor/CursorSpendHistoryFetcher.swift
- Cognitive Complexity · ProviderAccountAssembly.assemble (cognitive 46) Sources/OpenUsage/Services/ProviderAccountAssembly.swift
- Cognitive Complexity · AntigravityProvider.probeLS (cognitive 35) Sources/OpenUsage/Providers/Antigravity/AntigravityProvider.swift
- Cognitive Complexity · ClaudeProvider.refresh (cognitive 35) Sources/OpenUsage/Providers/Claude/ClaudeProvider.swift
- Cognitive Complexity · IncrementalJSONLScanner.items (cognitive 34) Sources/OpenUsage/Providers/IncrementalJSONLScanner.swift
- Cognitive Complexity · CodexProvider.refreshAccount (cognitive 34) Sources/OpenUsage/Providers/Codex/CodexProvider+Accounts.swift
- Cognitive Complexity · WidgetDataStore.localHistoryDocument (cognitive 31) Sources/OpenUsage/Stores/WidgetDataStore.swift
- Cognitive Complexity · ClaudeSessionIdentity.parse (cognitive 29) Sources/OpenUsage/Providers/Claude/ClaudeSessionIdentity.swift
- Cognitive Complexity · OpenCodeCodexUsageScanner.scan (cognitive 29) Sources/OpenUsage/Providers/OpenCode/OpenCodeCodexUsageScanner.swift
- Cognitive Complexity · AntigravityProtoDecoder.field (cognitive 28) Sources/OpenUsage/Providers/Antigravity/AntigravityProtoDecoder.swift
- Cognitive Complexity · ClaudeAuthStore.loadCredentialSet (cognitive 28) Sources/OpenUsage/Providers/Claude/ClaudeAuthStore.swift
- Cognitive Complexity · CursorSpendHistoryFetcher.refresh (cognitive 28) Sources/OpenUsage/Providers/Cursor/CursorSpendHistoryFetcher.swift
- Cognitive Complexity · ClaudeDesktopAuthStore.loadActiveOrganization (cognitive 25) REDACTED
- Cognitive Complexity · AntigravityDbUsageScanner.readDatabase (cognitive 24) Sources/OpenUsage/Providers/Antigravity/AntigravityDbUsageScanner.swift
- Cognitive Complexity · OpenSSHEd25519Key.parse (cognitive 24) Sources/OpenUsage/Providers/Ollama/OpenSSHEd25519Key.swift
- Cognitive Complexity · MonitorView.viewDidMoveToWindow (cognitive 23) Sources/OpenUsage/Support/PopoverDismissReader.swift
- Cognitive Complexity · AntigravityDbUsageScanner.scan (cognitive 23) Sources/OpenUsage/Providers/Antigravity/AntigravityDbUsageScanner.swift
- Cognitive Complexity · CodexLogUsageScanner.aggregate (cognitive 23) Sources/OpenUsage/Providers/Codex/CodexLogUsageScanner+Pricing.swift
- Cognitive Complexity · ProviderAccountAssembly.makeCodexCards (cognitive 22) Sources/OpenUsage/Services/ProviderAccountAssembly+Codex.swift
- Cognitive Complexity · OpenCodeUsageScanner.scan (cognitive 22) Sources/OpenUsage/Providers/OpenCode/OpenCodeUsageScanner.swift
- Cognitive Complexity · WidgetDataStore.refresh (cognitive 21) Sources/OpenUsage/Stores/WidgetDataStore.swift
- Cognitive Complexity · WidgetData.meterState (cognitive 20) Sources/OpenUsage/Models/WidgetData.swift
- Cognitive Complexity · ClaudeProvider.fetchLiveUsage (cognitive 20) Sources/OpenUsage/Providers/Claude/ClaudeProvider.swift
- Cognitive Complexity · ProviderAccountAssembly.discoverDesktopOrganizations (cognitive 19) Sources/OpenUsage/Services/ProviderAccountDiscoveryReadout.swift
- Cognitive Complexity · UsageHistoryAggregator.merge (cognitive 19) Sources/OpenUsage/Services/UsageHistoryAggregator.swift
- Cognitive Complexity · AntigravityProvider.probeCloudCode (cognitive 19) Sources/OpenUsage/Providers/Antigravity/AntigravityProvider.swift
- Cognitive Complexity · OpenCodeProvider.refresh (cognitive 19) Sources/OpenUsage/Providers/OpenCode/OpenCodeProvider.swift
- Cognitive Complexity · DailyUsageAccumulator.merged (cognitive 18) Sources/OpenUsage/Providers/DailyUsageAccumulator.swift
- Cognitive Complexity · UsageReader.read (cognitive 18) Sources/OpenUsage/Services/UsageReader.swift
- Cognitive Complexity · OpenUsageISO8601.normalizeFractionalISO (cognitive 18) Sources/OpenUsage/Support/OpenUsageISO8601.swift
- Cognitive Complexity · ClaudeSwapAccount.discover (cognitive 18) Sources/OpenUsage/Providers/Claude/ClaudeSwapAccount.swift
- Cognitive Complexity · CodexLogUsageScanner.sessionFiles (cognitive 18) Sources/OpenUsage/Providers/Codex/CodexLogUsageScanner.swift
- Cognitive Complexity · JSONLScanCacheWriter.pruneStaleIdentities (cognitive 17) Sources/OpenUsage/Providers/JSONLScanCacheStore.swift
- Cognitive Complexity · ProviderAccountsStore.reconcile (cognitive 17) Sources/OpenUsage/Stores/ProviderAccountsStore.swift
- Cognitive Complexity · SVGPath.parse::readNumber (cognitive 17) Sources/OpenUsage/Support/ProviderIconShape.swift
- Cognitive Complexity · ClaudeLogUsageScanner.coworkClaudeDirs (cognitive 17) Sources/OpenUsage/Providers/Claude/ClaudeLogUsageScanner.swift
- Cognitive Complexity · GrokLogUsageScanner.parseCompletedTurn (cognitive 17) Sources/OpenUsage/Providers/Grok/GrokLogUsageScanner.swift
- Cognitive Complexity · OpenCodeAuthStore.goAPIKey (cognitive 17) Sources/OpenUsage/Providers/OpenCode/OpenCodeAuthStore.swift
- Cognitive Complexity · JSONLTailIO.tailParse (cognitive 16) Sources/OpenUsage/Providers/JSONLTailParsing.swift
- Cognitive Complexity · LayoutStore.applyMetricDividerOrderImpl (cognitive 16) Sources/OpenUsage/Stores/LayoutStore+Customization.swift
- Cognitive Complexity · ClaudeAuthStore.loadSwapVaultCredential (cognitive 16) Sources/OpenUsage/Providers/Claude/ClaudeSwapAccount.swift
- Cognitive Complexity · ClaudeDesktopAuthStore.normalizedCache (cognitive 16) Sources/OpenUsage/Providers/Claude/ClaudeDesktopAuthStore+TokenCache.swift
- Cognitive Complexity · ClaudeLogUsageScanner.parseEntries (cognitive 16) Sources/OpenUsage/Providers/Claude/ClaudeLogUsageScanner.swift
- Cognitive Complexity · CursorProvider.probe (cognitive 16) Sources/OpenUsage/Providers/Cursor/CursorProvider.swift
- God Classes · MethodTooLong: ProviderAccountAssembly.assemble Sources/OpenUsage/Services/ProviderAccountAssembly.swift
- God Classes · MethodTooLong: JSONLStreamingReader.read Sources/OpenUsage/Providers/JSONLStreamingReader.swift
- God Classes · ClassTooLong: ClaudeProvider Sources/OpenUsage/Providers/Claude/ClaudeProvider.swift
- God Classes · MethodTooLong: SVGPath.parse Sources/OpenUsage/Support/ProviderIconShape.swift
- God Classes · MethodTooLong: ClaudeProvider.refresh Sources/OpenUsage/Providers/Claude/ClaudeProvider.swift
- Code Duplication · Duplicated block (15 lines × 2) Sources/OpenUsage/Providers/Cursor/CursorSpendHistoryFetcher.swift
- Code Duplication · Duplicated block (11 lines × 2) Sources/OpenUsage/Providers/Ollama/OllamaProvider.swift
- Code Duplication · Duplicated block (9 lines × 2) Sources/OpenUsage/Providers/Claude/ClaudeProvider.swift
- Code Duplication · Duplicated block (9 lines × 2) Sources/OpenUsage/Providers/Codex/CodexResetClaimService.swift
- Code Duplication · Duplicated block (9 lines × 2) Sources/OpenUsage/Providers/Grok/GrokLogUsageScanner.swift
- Code Duplication · Duplicated block (8–9 lines × 2) Sources/OpenUsage/Services/LocalUsageAPI.swift
- Code Duplication · Duplicated block (9 lines × 2) Sources/OpenUsage/Views/PopoverTopBar.swift
- Code Duplication · Duplicated block (8 lines × 3) Sources/OpenUsage/Providers/Antigravity/AntigravityProvider.swift
- Code Duplication · Duplicated block (6–8 lines × 2) Sources/OpenUsage/Services/ProviderAccountAssembly.swift
- Code Duplication · Duplicated block (7 lines × 2) Sources/OpenUsage/Providers/Antigravity/AntigravityDbUsageScanner.swift
- Code Duplication · Duplicated block (6–7 lines × 2) Sources/OpenUsage/Providers/Copilot/CopilotOrgBillingClient.swift
- Code Duplication · Duplicated block (7 lines × 2) Sources/OpenUsage/Support/ProviderIconShape.swift
- Code Duplication · Duplicated block (6 lines × 2) Sources/OpenUsage/Providers/SpendTileMapper.swift
- Code Duplication · Duplicated block (5–6 lines × 3) Sources/OpenUsage/Support/ProviderIconShape.swift
- Code Duplication · Duplicated block (5 lines × 2) Sources/OpenUsage/Providers/Claude/ClaudeProvider.swift
- Code Duplication · Duplicated block (5 lines × 2) Sources/OpenUsage/Support/LogRedaction.swift
Rebuild cost: about €27,000 · Estimate
| Cost to rebuild | €9,100 to €46,000, for 152 to 481 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 65. 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: 12,313 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 OpenUsage | 2 OpenUsageApp | 3 OpenUsageCLI |
|---|---|---|---|
| 1 OpenUsage | |||
| 2 OpenUsageApp | |||
| 3 OpenUsageCLI | 3 |
3→1 OpenUsageCLI uses OpenUsage✕
- Connections
- 3 pairs of types, where a type in OpenUsageCLI uses a type in OpenUsage.
- The types involved
OpenUsageCLI.AppBundleLocator→OpenUsage.StringOpenUsageCLI.CLIArguments→OpenUsage.StringOpenUsageCLI.OpenUsageCLI→OpenUsage.String
- Direction
- OpenUsageCLI uses OpenUsage, so a change to OpenUsage can break OpenUsageCLI, while a change to OpenUsageCLI can't break OpenUsage.
- Position
- Below the diagonal: OpenUsageCLI uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 31 | High / Critical |
| A07:2025 — Authentication Failures | 8 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 3 | Medium |
Roadmap
Immediately resolve the three leaked secrets in REDACTED and the sixteen hardcoded secrets in the CI workflows to eliminate critical security vulnerabilities. Integrate automated security scanning into the continuous integration pipeline to prevent future regressions from reaching production. Finally, establish a structured repository for architecture decision records to document significant design choices and their consequences.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3). | +3.9 pts | Low | REDACTED Scanning |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.9 pts | Low | ADR Quality |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +2.8 pts | Medium | Security & performance tooling |
| Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. | +1.0 pts | Low | Secrets (history) |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +1.7 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.8 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.8 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.8 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| Tests/OpenUsageTests/AntigravityArgonQuotaTests.swift | 7.2 | Near-clean | Test Quality: No assertions: testAbsentArgonPreservesExistingFourBuckets |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| Sources/OpenUsage/Providers/Claude/AccountProviderRuntime+ClaudeResets.swift | 7.4 | Near-clean | Cyclomatic Complexity: AccountProviderRuntime.claimClaudeResetGrant (cyclomatic 17) |
| Sources/OpenUsage/Providers/AccountProviderRuntime+Descriptors.swift | 7.4 | Near-clean | God Classes: MethodTooLong: AccountProviderRuntime.widgetDescriptors |
| Sources/OpenUsage/Views/DashboardView.swift | 7.8 | Near-clean | Cyclomatic Complexity: DashboardView.body (cyclomatic 24) |
| Sources/OpenUsage/Providers/Cursor/CursorUsageMapper.swift | 7.8 | Near-clean | Cyclomatic Complexity: CursorUsageMapper.mapUsage (cyclomatic 19) |
| Sources/OpenUsage/Providers/Grok/GrokCreditsConfigDecoder.swift | 7.8 | Near-clean | Cyclomatic Complexity: GrokCreditsConfigDecoder.decode (cyclomatic 16) |
| Tests/OpenUsageTests/OAuthRefreshPersistenceTests.swift | 7.8 | Near-clean | Test Quality: No assertions: testClaudeRefusedRefreshTokenReadsAsExpiredSignIn |
| Tests/OpenUsageTests/RefreshBackoffTests.swift | 7.8 | Near-clean | Test Quality: No assertions: testRateLimitWithoutRetryAfterDoublesFromFiveMinutesToAnHour |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 42 of 42 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 42 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, 84 of 95 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in . produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.swift) and this repository declares a SwiftPM test suite (OpenUsage), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (18 contributor(s) across 660 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 17 hold 0.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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: 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Sources/OpenUsage/Models/ProviderSnapshot.swift`, `Sources/OpenUsage/Providers/AccountProviderRuntime+Descriptors.swift`, `REDACTED`, `Sources/OpenUsage/Providers/Claude/ClaudeUsageMapper.swift`, `REDACTED`, … (+5 more) 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.
- D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in Sources/OpenUsage/App/AppContainer.swift, 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.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Swift 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Swift 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, 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.
- S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust and Dart source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust or Dart was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Swift 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.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Swift (Foundation mutable collections) 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.
- X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Scala, JavaScript/TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart and Ruby source only, and no C# was loaded and no Scala, JavaScript, TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Swift 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.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was DashboardView.body at 24.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with DashboardView.body (cyclomatic 24), CursorUsageMapper.mapUsage (cyclomatic 19), AccountProviderRuntime.claimClaudeResetGrant (cyclomatic 17). — 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 6 together lifts Cyclomatic Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
11 method(s) exceeded the cognitive complexity threshold of 15; the worst was DashboardView.body at 25.
What to do
- Bring the 11 bodies over 15 down to 15 or less in Cognitive Complexity — start with DashboardView.body (cognitive 25), CursorUsageMapper.mapUsage (cognitive 23), QuotaNotificationEvaluator.evaluate (cognitive 22). — 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 11 together lifts Cognitive Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with AccountProviderRuntime.swift, LayoutStore.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with AccountProviderRuntime+Descriptors.swift. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
4 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with CodexUsageClient.swift. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (5 lines × 3) finding(s) in Code Duplication — start with AccountProviderRuntime+Descriptors.swift. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (4–5 lines × 3) finding(s) in Code Duplication — start with AccountProviderRuntime+Descriptors.swift. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
3 production modules (SwiftPM), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 29 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with UpdaterController.swift. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
521 test methods: 521 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 13 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 521 tests.
What to do
- Resolve the 13 No assertions finding(s) in Test Quality — start with AntigravityArgonQuotaTests.swift (4), OAuthRefreshPersistenceTests.swift (2), RefreshBackoffTests.swift (2). — One of this dimension's main actionable groups (13 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D12 · Dependency Hygiene
2 outdated direct SwiftPM dependencies, 0 pinning defect(s). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.
D13 · REDACTED Scanning
3 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 3 SwiftPM package(s) use a banned license. SwiftPM has no package registry, so each package's licence is the one its repository declares: 2 of them read from the licence file the repository carries at the revision Package.resolved pins, and 1 — unpinned, or whose licence file could not be read or named — from api.deps.dev, which reports the licence the repository declares today. Graded: every package a committed Package.resolved pins, direct and transitive, and every declared dependency none pins. 1 of them declare no licence that matches a known SPDX licence; that is missing data, not a violation, and none of them is charged.
D15 · Churn × Complexity Hotspots
Top hotspots: Sources/OpenUsage/Providers/Cursor/CursorUsageMapper.swift (6×19=114); Sources/OpenUsage/Views/DashboardView.swift (4×24=96) Repeated repair below the complexity floor: Sources/OpenUsage/Providers/ProviderRuntime.swift (3 of 5 changes were fixes); Sources/OpenUsage/Providers/Ollama/OllamaUsageMapper.swift (3 of 4 changes were fixes)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with CursorUsageMapper.swift, DashboardView.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with ProviderRuntime.swift, OllamaUsageMapper.swift. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 12313 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.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (SwiftPM) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
4 finding(s): 0 critical, 4 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 4 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 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)
31 finding(s): 0 critical, 31 high, 0 medium, 0 low. 13 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) — `Sources/OpenUsage/Stores/WidgetDataStore.swift` (line 42) — 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 16 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (13), REDACTED (3). — One of this dimension's main actionable groups (16 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 13 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 (13 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 80 of the 159 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: LiquidGlassFallbacks.swift↔DashboardView.swift 85%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with LiquidGlassFallbacks.swift. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 24770 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
- `refreshClaude` is async and calls .wait() — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — Sources/OpenUsage/Providers/Claude/AccountProviderRuntime+ClaudeUsage.swift:15
- `refreshHourlyReads` is async and calls .wait() — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — Sources/OpenUsage/Providers/Claude/AccountProviderRuntime+ClaudeUsage.swift:41
What to do
- Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
X14 · Bypassable address classification
X26 · Unsynchronised callback handoff
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — Sources/OpenUsage/Providers/Antigravity/AntigravityUsageMapper.swift:163
What to do
- Swallowed exception (caught, then discarded)
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82% | Strong | Strongest area. |
| Architecture | 89% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 67% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 62% | Adequate — gated by D13, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 65% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 70% | Strong | Solid. |
Not evidenced — 2 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported 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 property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency is measured on C# only; Swift 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+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .swift, 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
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.swift), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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) — 10 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Swift suite
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — 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
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `swift test --enable-code-coverage` (SwiftPM) or `xcodebuild test -scheme <YourScheme> -enableCodeCoverage YES` (an .xcodeproj/.xcworkspace suite), then `xcrun llvm-cov export -format=lcov`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, 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 applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Swift code has 13,745 production line(s), 2 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- 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
- X15 Unvalidated length from an untrusted reader — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — Not applicable: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. Swift has no `++` or `--`, and an assignment yields `()`, which cannot be an operand of `&&`, `||` or `?:` nor the Bool a `case … where` clause needs. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — 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 — 38 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 48 finding(s)
- No assertions: testAbsentArgonPreservesExistingFourBuckets Tests/OpenUsageTests/AntigravityArgonQuotaTests.swift:30
- No assertions: testUnavailableArgonPreservesSharedQuotas Tests/OpenUsageTests/AntigravityArgonQuotaTests.swift:34
- No assertions: testOnlyExplicitArgonWeeklyGroupCanPopulateTheRow Tests/OpenUsageTests/AntigravityArgonQuotaTests.swift:47
- No assertions: testAmbiguousWeeklyBucketsDoNotChooseOrMergeAQuota Tests/OpenUsageTests/AntigravityArgonQuotaTests.swift:83
- No assertions: testReportedStandardSeatUsesStructuredTotalInsteadOfLegacyTwentyDollars Tests/OpenUsageTests/CursorTeamPoolTests.swift:5
- No assertions: testUnpinningAfterHoverOutHidesThePopover Tests/OpenUsageTests/HoverPopoverStateTests.swift:20
- No assertions: testClaudeRefusedRefreshTokenReadsAsExpiredSignIn Tests/OpenUsageTests/OAuthRefreshPersistenceTests.swift:93
- No assertions: testGrokRefusedRefreshTokenReadsAsExpiredSignIn Tests/OpenUsageTests/OAuthRefreshPersistenceTests.swift:97
- No assertions: testInvalidateDropsQueuedHeight Tests/OpenUsageTests/PanelHeightBridgeTests.swift:33
- No assertions: testTraySurfaceIsFullyOpaqueInBothAppearances Tests/OpenUsageTests/PopoverSurfaceOpacityTests.swift:8
- No assertions: testSuccessStatusesDoNotThrow Tests/OpenUsageTests/ProviderErrorTriageTests.swift:10
- No assertions: testRateLimitWithoutRetryAfterDoublesFromFiveMinutesToAnHour Tests/OpenUsageTests/RefreshBackoffTests.swift:52
- No assertions: testNoAnswerRetriesEveryPassWithoutGrowingTheWait Tests/OpenUsageTests/RefreshBackoffTests.swift:98
- Hotspot: Sources/OpenUsage/Providers/Cursor/CursorUsageMapper.swift Sources/OpenUsage/Providers/Cursor/CursorUsageMapper.swift:69
- Hotspot: Sources/OpenUsage/Views/DashboardView.swift Sources/OpenUsage/Views/DashboardView.swift:26
- Repeated repair: Sources/OpenUsage/Providers/ProviderRuntime.swift Sources/OpenUsage/Providers/ProviderRuntime.swift:26
- Repeated repair: Sources/OpenUsage/Providers/Ollama/OllamaUsageMapper.swift Sources/OpenUsage/Providers/Ollama/OllamaUsageMapper.swift:8
- TooManyMethods: AccountProviderRuntime Sources/OpenUsage/Providers/AccountProviderRuntime.swift:3
- TooManyMethods: LayoutStore Sources/OpenUsage/Stores/LayoutStore.swift:4
- Sync-over-async blocking Sources/OpenUsage/Providers/Claude/AccountProviderRuntime+ClaudeUsage.swift:15
- Sync-over-async blocking Sources/OpenUsage/Providers/Claude/AccountProviderRuntime+ClaudeUsage.swift:41
- DashboardView.body (cyclomatic 24) Sources/OpenUsage/Views/DashboardView.swift:26
- CursorUsageMapper.mapUsage (cyclomatic 19) Sources/OpenUsage/Providers/Cursor/CursorUsageMapper.swift:69
- AccountProviderRuntime.claimClaudeResetGrant (cyclomatic 17) Sources/OpenUsage/Providers/Claude/AccountProviderRuntime+ClaudeResets.swift:55
- WidgetDataStore.refresh (cyclomatic 17) Sources/OpenUsage/Stores/WidgetDataStore.swift:104
- MonitorView.viewDidMoveToWindow (cyclomatic 17) Sources/OpenUsage/Support/PopoverKeyReader.swift:40
- GrokCreditsConfigDecoder.decode (cyclomatic 16) Sources/OpenUsage/Providers/Grok/GrokCreditsConfigDecoder.swift:18
- DashboardView.body (cognitive 25) Sources/OpenUsage/Views/DashboardView.swift:26
- CursorUsageMapper.mapUsage (cognitive 23) Sources/OpenUsage/Providers/Cursor/CursorUsageMapper.swift:69
- QuotaNotificationEvaluator.evaluate (cognitive 22) Sources/OpenUsage/Stores/QuotaNotificationEvaluator.swift:16
- PaceNotificationLogic.transitions (cognitive 21) Sources/OpenUsage/Support/PaceNotificationLogic.swift:61
- GrokCreditsConfigDecoder.decode (cognitive 20) Sources/OpenUsage/Providers/Grok/GrokCreditsConfigDecoder.swift:18
- MenuBarStripRenderer.visibleBounds (cognitive 19) Sources/OpenUsage/Support/MenuBarStripRenderer.swift:37
- AccountProviderRuntime.claimClaudeResetGrant (cognitive 18) Sources/OpenUsage/Providers/Claude/AccountProviderRuntime+ClaudeResets.swift:55
- WireResource.init (cognitive 17) Sources/OpenUsage/Services/LimitsEnvelope.swift:82
- ZAIUsageMapper.mapQuota (cognitive 17) Sources/OpenUsage/Providers/ZAI/ZAIUsageMapper.swift:9
- OAuthLoginSupport.swift.authorizationCode (cognitive 16) Sources/OpenUsage/Services/OAuthLoginSupport.swift:173
- ReorderGeometry.swift.reorderTarget (cognitive 16) Sources/OpenUsage/Views/ReorderGeometry.swift:111
- MethodTooLong: AccountProviderRuntime.widgetDescriptors Sources/OpenUsage/Providers/AccountProviderRuntime+Descriptors.swift:8
- Change coupling: LiquidGlassFallbacks.swift ↔ DashboardView.swift Sources/OpenUsage/Support/LiquidGlassFallbacks.swift:1
- REDACTED
- Duplicated block (13 lines × 2) Sources/OpenUsage/Providers/Codex/CodexUsageClient.swift:4
- Duplicated block (5 lines × 3) Sources/OpenUsage/Providers/AccountProviderRuntime+Descriptors.swift:30
- Duplicated block (4–5 lines × 3) Sources/OpenUsage/Providers/AccountProviderRuntime+Descriptors.swift:14
- Duplicated block (5 lines × 2) Sources/OpenUsage/Providers/Claude/AccountProviderRuntime+ClaudeResets.swift:102
- Off the main sequence: OpenUsage
- Low cohesion: UpdaterController (LCOM4 4) Sources/OpenUsage/App/UpdaterController.swift:17
- Swallowed exception (caught, then discarded) Sources/OpenUsage/Providers/Antigravity/AntigravityUsageMapper.swift:163
Minor — 7 finding(s)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST
Minor — 2 finding(s)
- Outdated: posthog-ios
- Outdated: sparkle
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9e5392165790497198bc62a86b946992/history.json --exit-code 0 --source . | 5 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9e5392165790497198bc62a86b946992/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 31 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 10 file(s) — `Sources/OpenUsage/Models/ProviderSnapshot.swift`, `Sources/OpenUsage/Providers/AccountProviderRuntime+Descriptors.swift`, `REDACTED`, `Sources/OpenUsage/Providers/Claude/ClaudeUsageMapper.swift`, `REDACTED`, … (+5 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |