Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
Homebrew/brew carries serious gaps (49%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
It is strongest in Code Health (100%) — the code is clean and low-risk to change.
The area that most needs attention is Readiness (34%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Security (52%) is the next concern — exposure to security and compliance incidents is elevated.
Leadership focus, highest impact first: 1 No tests found finding(s) in Test Distribution (Test Distribution); ILogger (or Serilog) and log at meaningful points across… (Observability); Keep the changelog current (Release Hygiene).
For scale: Hobby (~0 production lines); rebuilding it from scratch would take roughly ~0.7 person-years (~1–2 engineers). Approximate, ±~30%.
It builds on a genuinely strong Code Health foundation (100%); the priorities above are the highest-leverage way to bring the rest up to that level.
Code Health
100% ★
Exemplary
Maturity
61%
Adequate · gated by M2
Readiness
34%
Weak · gated by D9, P2, P6
Security
52%
Adequate · gated by D28, D29
How the score is built — each lens's share of the headline
Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
Readiness 34% · 50% weightSecurity 52% · 27% weightMaturity 61% · 15% weightCode Health 100% · 8% weight
Raise Readiness 34 → 70 (the Healthy floor) ⇒ headline 49 → ~61.
Code composition — where the lines go
Tests 100%
Top priorities
1
Resolve the 1 No tests found finding(s) in Test Distribution.
2
Adopt ILogger (or Serilog) and log at meaningful points across the projects.
3
Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
Diagnosis — what's actually going on
Highest-leverage move
Of everything flagged, the best return on effort is: Resolve the 1 No tests found finding(s) in Test Distribution. The rest can wait behind it.
At a glance — Code Health
The Good
At a glance — Architecture
The Good
The Bad
At a glance — Maturity
The Good
At a glance — Readiness
The Good
At a glance — Security
The Good
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2021 — Injection | 20 | High / Critical |
| A02:2021 — Cryptographic Failures | 7 | High / Critical |
| A05:2021 — Security Misconfiguration | 1 | Medium |
Roadmap
Begin by addressing the lack of tests to ensure code reliability. Next, implement structured logging and health checks to improve system observability. Then, maintain a current changelog for each release to preserve project history. After that, add readiness and liveness probes with an automated rollback strategy to handle bad releases. Finally, update the root README with a quick-start section to help new contributors get up to speed.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No tests found finding(s) in Test Distribution. | +17.2 pts | Low | Test Distribution |
| Adopt ILogger (or Serilog) and log at meaningful points across the projects. | +17.2 pts | Medium | Observability |
| Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub. | +17.2 pts | Medium | Release Hygiene |
| Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically. | +11.8 pts | Medium | Deployment & Rollback |
| Resolve the 6 Secret finding(s) in Secrets (history) — start with analytics.rb (5), base.html. | +3.4 pts | Low | Secrets (history) |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +5.8 pts | Medium | Documentation (README) |
| Grow the ADR log (currently 13) — reach 20 to raise the maturity tier; document significant decisions as they're made. | +5.8 pts | Medium | Architecture documentation |
| Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root. | +5.8 pts | Medium | Folder & project structure |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| docs/_layouts/base.html | 4.1 | Mixed | Secrets (history): Secret: generic-api-key |
| Library/Homebrew/utils/analytics.rb | 4.5 | Mixed | Secrets (history): Secret: generic-api-key |
| Library/Homebrew/dev-cmd/bump-cask-pr.rb | 5.8 | Mixed | Static Analysis (SAST): High: dangerous-exec |
| Library/Homebrew/dev-cmd/bump-formula-pr.rb | 5.8 | Mixed | Static Analysis (SAST): High: dangerous-exec |
| Library/Homebrew/system_command.rb | 5.8 | Mixed | Static Analysis (SAST): High: dangerous-exec |
| .github/workflows/release.yml | 7.2 | Mixed | Static Analysis (SAST): High: gha-workflow-env-secret |
| Library/Homebrew/bundle.rb | 7.2 | Mixed | Static Analysis (SAST): High: dangerous-exec |
| Library/Homebrew/bundle/extensions/winget.rb | 7.2 | Mixed | Static Analysis (SAST): High: dangerous-exec |
| Library/Homebrew/cmd/log.rb | 7.2 | Mixed | Static Analysis (SAST): High: dangerous-exec |
| Library/Homebrew/dev-cmd/bump.rb | 7.2 | Mixed | Static Analysis (SAST): High: dangerous-exec |
| Library/Homebrew/formula-analytics/pyproject.toml | 7.2 | Mixed | Static Analysis (SAST): High: uv-missing-dependency-cooldown |
| Library/Homebrew/formula_assertions.rb | 7.2 | Mixed | Static Analysis (SAST): High: dangerous-exec |
| Library/Homebrew/formulary.rb | 7.2 | Mixed | Static Analysis (SAST): High: weak-hashes-md5 |
| Library/Homebrew/mcp_server.rb | 7.2 | Mixed | Static Analysis (SAST): High: dangerous-exec |
| Library/Homebrew/test_bot/test_cleanup.rb | 7.2 | Mixed | Static Analysis (SAST): High: dangerous-exec |
| Library/Homebrew/test_bot/test_formulae.rb | 7.2 | Mixed | Static Analysis (SAST): High: dangerous-exec |
| docs/governance/2019-membership.md | 8.5 | Near-clean | ADR Quality: Empty ADR with only a title and a list of contributors (no context, decision, or consequences) |
| docs/governance/2019-plc-minutes.md | 8.5 | Near-clean | ADR Quality: No context/problem and no consequences; this is a pure minute-taking record with no real decision or trade-off discussion |
| docs/governance/2020-membership.md | 8.5 | Near-clean | ADR Quality: This is a list of member accounts with no context/problem and no decision; it contains only the author names |
| docs/governance/2020-plc-minutes.md | 8.5 | Near-clean | ADR Quality: This is a committee minutes record with no decision or consequences; the visible content is administrative rather than an architecture decision |
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. 30 of 33 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — 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 — 33 dimensions across the health lenses
D3D4D5D7D9D12D13D15D16D19D20D21D26D27D28D29D31D34D35D36AX5M1M2M3M4P1P2P3P4P6X1X3X4
How to trust any code-health report — three questions
- 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, 41 of 48 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 |
| jscpd | Code duplication | — | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.301 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.301 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | 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 | Local LLM | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D18 Solution Shape — evaluation did not complete — Dimension evaluation failed — excluded from the score.
- D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
- D32 Data Compliance (PII/GDPR) — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
- D33 JS/npm Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
- D37 Vulnerability-disclosure Policy — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
- D38 OSV Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
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
- 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 (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (EF migration scaffolds, *.Designer.cs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only; the generated footprint is reported separately under Solution Shape.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
- 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.
- D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- 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.
The LLM boundary
Dimensions
D3 · God Classes
0 god class(es) detected.
Do you agree with this assessment?
D4 · Code Duplication
0 duplicated block group(s) detected.
Do you agree with this assessment?
D5 · Coupling
0 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Do you agree with this assessment?
D7 · Architectural Integrity
Of 1 mechanizable ADRs, 1 are prevented by analyzers, 0 by tests, 0 exist only in prose. Coverage: 100 %. Cycles found: 0.
Do you agree with this assessment?
D9 · Test Distribution
No test projects found.
No tests found
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D12 · Dependency Hygiene
0 outdated, 0 vulnerable, 0 deprecated packages.
Do you agree with this assessment?
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
Do you agree with this assessment?
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
Do you agree with this assessment?
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author.
Do you agree with this assessment?
D19 · Documentation Quality
Homebrew's documentation is clear and complete for a large open-source project: it includes an official README with installation, donations, a donation link, and links to every major Homebrew topic (installation, troubleshooting, contribution, FAQ), plus the generated man pages, completions directories, and a governance section. The docs are well organized by audience into Users, Contributors, Maintainers, Governance, and Project history, with each listed in the outline present in the visible text.
The README links to `brew bundle` but does not mention what happens when a formulae dependency is removed or updated (e.g. how to handle broken dependencies).README.md
The Users section lists `Bottles`, `Taps`, and `Trusting Taps` but does not explain what happens when a bottle is removed from the repository.docs/index.md
Do you agree with this assessment?
D20 · ADR Quality
Evaluated 13 ADR(s) individually; mean quality 2.3/10 (frequently incomplete). 12 flagged with a specific gap.
Empty ADR with only a title and a list of contributors (no context, decision, or consequences)docs/governance/2019-membership.md
No context/problem and no consequences; this is a pure minute-taking record with no real decision or trade-off discussiondocs/governance/2019-plc-minutes.md
This is a list of member accounts with no context/problem and no decision; it contains only the author namesdocs/governance/2020-membership.md
This is a committee minutes record with no decision or consequences; the visible content is administrative rather than an architecture decisiondocs/governance/2020-plc-minutes.md
Decision (electing STV PLC and Schulze project leader) is explicit but the body is a minute listing motions, reports, and presentations with no context/problem or consequences/trade-offsdocs/governance/2021-agm-minutes.md
What to do
- Resolve the 1 Empty ADR with only a title and a list of contributors (no context,… finding(s) in ADR Quality — start with 2019-membership.md. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No context/problem and no consequences; this is a pure minute-taking… finding(s) in ADR Quality — start with 2019-plc-minutes.md. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 This is a list of member accounts with no context/problem and no… finding(s) in ADR Quality — start with 2020-membership.md. — One of this dimension's main actionable groups (1 warning-level).
Do you agree with this assessment?
D21 · Naming Consistency
0 naming inconsistencies across 0 sampled symbols.
Do you agree with this assessment?
D26 · Project Cohesion
No projects to assess.
Do you agree with this assessment?
D27 · Navigability
Too little code to assess navigability.
Do you agree with this assessment?
D28 · Secrets (history)
7 finding(s): 0 critical, 7 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
Secret: generic-api-key docs/_layouts/base.html:3
Rotate the exposed credentials — git history can't be un-committed
What to do
- Resolve the 6 Secret finding(s) in Secrets (history) — start with analytics.rb (5), base.html. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D29 · Static Analysis (SAST)
20 finding(s): 0 critical, 18 high, 2 medium, 0 low.
High: gha-workflow-env-secret .github/workflows/release.yml:19
Medium: unquoted-attribute-var docs/_layouts/base.html:10
What to do
- Resolve the 18 High finding(s) in Static Analysis (SAST) — start with bump-cask-pr.rb (2), bump-formula-pr.rb (2), system_command.rb (2). — One of this dimension's main actionable groups (18 issue-level).
- Resolve the 2 Medium finding(s) in Static Analysis (SAST) — start with base.html (2). — One of this dimension's main actionable groups (2 warning-level).
Do you agree with this assessment?
D31 · IaC & Container Security
1 finding(s): 0 critical, 0 high, 0 medium, 1 low.
Low IaC: DS-0026Dockerfile
Do you agree with this assessment?
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked.
Do you agree with this assessment?
D35 · Change Coupling
No strong hidden change-coupling between production files.
Do you agree with this assessment?
D36 · Supply-chain Provenance & Signing
3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
No artifact signing
What to do
- Resolve the 1 No artifact signing finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
Frontend & cross-cutting dimensions
AX5 · Architecture & structure
Do you agree with this assessment?
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Add a 'Testing' section to the root README — how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Do you agree with this assessment?
M2 · Architecture documentation
- No C4/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.
What to do
- Grow the ADR log (currently 13) — reach 20 to raise the maturity tier; document significant decisions as they're made.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Do you agree with this assessment?
M3 · Folder & project structure
- Projects aren't grouped under a src/ folder — production and tooling code are mixed at the root.
- Test projects aren't grouped under a tests/ folder — the test surface isn't separable from production code at a glance.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
- Group test projects under tests/ (or test/, spec/) so the test surface is discoverable and CI can scope it.
Do you agree with this assessment?
M4 · Documentation accuracy
Do you agree with this assessment?
P1 · CI/CD gates
Do you agree with this assessment?
P2 · Observability
- No ILogger/Serilog usage found — production issues will be hard to diagnose.
What to do
- Adopt ILogger (or Serilog) and log at meaningful points across the projects.
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
Do you agree with this assessment?
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Do you agree with this assessment?
P4 · Deployment & Rollback
- Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
- Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
Do you agree with this assessment?
P6 · Release Hygiene
- A changelog exists but has few versioned entries — keep it current with each release.
What to do
- Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
- Stamp a version (csproj <Version>, a VERSION file, or GitVersion) or tag releases with semver so builds and releases are traceable.
Do you agree with this assessment?
X1 · Async correctness
Do you agree with this assessment?
X3 · Exception handling
Do you agree with this assessment?
X4 · Structured logging
Do you agree with this assessment?
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 100% | Exemplary | Strongest area. |
| Maturity | 61% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 34% | Weak — gated by D9, P2, P6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 52% | Adequate — gated by D28, D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not included — 58 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX10 Code composition — no source files detected — code composition not applicable
- AX2 Stateful singletons — no singleton implementations detected
- AX3 Project dependency cycles — no csproj graph available
- AX4 Dependency direction — no csproj graph available
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — no data
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D1 Cyclomatic Complexity — No production methods were analyzable, so cyclomatic complexity was not measured (the solution likely failed to load or has no production code).
- D10 Test Quality — ~103967 lines of test code exist on disk but weren't loaded from the analyzed solution (excluded from the .sln, or co-located/using a test attribute not loaded here), so test quality couldn't be assessed. Include the tests in the analyzed solution to enable this check.
- D11 Test Reliability — Test reliability not included
- D14 License Compliance — license scan produced no result — the tool ran but its JSON output could not be parsed; the offline NuGet fallback resolved nothing
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — Dimension evaluation failed
- D2 Cognitive Complexity — No production methods were analyzable, so cognitive complexity was not measured (the solution likely failed to load or has no production code).
- D22 Internal API Consistency — No exposed public API
- D23 Boundary Type-Coupling — Zero projects and zero LoC mean the codebase is trivial and has no structure to justify boundaries.
- D24 Comment Value — No inline comments to assess — comment value is not applicable here.
- D25 ADR Conformance — none of 13 ADRs are conformance-checkable — unverifiable.
- D30 Dependency Vulnerabilities — No .NET solution found; no NuGet dependencies to scan for vulnerabilities.
- D32 Data Compliance (PII/GDPR) — No PII/GDPR ruleset is bundled (the public p/gdpr semgrep pack was retired) — data compliance is not assessed in this scan.
- D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D38 OSV Dependency Vulnerabilities — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan.
- D39 IL Efficiency — The target did not build, so no IL was available to measure.
- D6 Cohesion (LCOM4) — No production classes were analyzable, so cohesion (LCOM4) was not measured (the solution likely failed to load or has no production code).
- D8 Code Coverage — Coverage not measured — test suite did not build
- DM1 Domain Modelling — not run — 0/3 markers found
- ED1 Event-Driven — not run — 0/3 markers found
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not run — 0/3 markers found
- GD1 Unfinished & placeholder code — no source files
- IC1 Incompleteness & stubs — no C# methods found
- P12 CI test-gate honesty — no data
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — run tests with `--collect:"XPlat Code Coverage"` (or in CI) to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X2 Cancellation propagation — no async methods found
- X5 Nullable reference types — no NRT-eligible projects
Appendix A — Findings (grouped)
Issue — 25 finding(s)
D29 · Static Analysis (SAST)
- High: gha-workflow-env-secret .github/workflows/release.yml:19
- High: dangerous-exec Library/Homebrew/bundle.rb:34
- High: dangerous-exec Library/Homebrew/bundle/extensions/winget.rb:435
- High: dangerous-exec Library/Homebrew/cmd/log.rb:84
- High: dangerous-exec Library/Homebrew/dev-cmd/bump-cask-pr.rb:525
- High: dangerous-exec Library/Homebrew/dev-cmd/bump-cask-pr.rb:555
- High: dangerous-exec Library/Homebrew/dev-cmd/bump-formula-pr.rb:821
- High: dangerous-exec Library/Homebrew/dev-cmd/bump-formula-pr.rb:824
- High: dangerous-exec Library/Homebrew/dev-cmd/bump.rb:574
- High: uv-missing-dependency-cooldown Library/Homebrew/formula-analytics/pyproject.toml:7
- High: dangerous-exec Library/Homebrew/formula_assertions.rb:58
- High: weak-hashes-md5 Library/Homebrew/formulary.rb:900
- High: dangerous-exec Library/Homebrew/mcp_server.rb:324
- High: dangerous-exec Library/Homebrew/system_command.rb:416
- High: dangerous-exec Library/Homebrew/system_command.rb:429
- High: dangerous-exec Library/Homebrew/test_bot/test_cleanup.rb:21
- High: dangerous-exec Library/Homebrew/test_bot/test_formulae.rb:237
- High: dangerous-exec Library/Homebrew/utils/analytics.rb:69
D28 · Secrets (history)
- Secret: generic-api-key docs/_layouts/base.html:3
- Secret: generic-api-key Library/Homebrew/utils/analytics.rb:14
- Secret: generic-api-key Library/Homebrew/utils/analytics.rb:15
- Secret: generic-api-key Library/Homebrew/utils/analytics.rb:15
- Secret: generic-api-key Library/Homebrew/utils/analytics.rb:15
- Secret: generic-api-key Library/Homebrew/utils/analytics.rb:20
D18 · Solution Shape
- Dimension evaluation failed
Warning — 15 finding(s)
D29 · Static Analysis (SAST)
- Medium: unquoted-attribute-var docs/_layouts/base.html:10
- Medium: var-in-href docs/_layouts/base.html:155
D20 · ADR Quality
- Empty ADR with only a title and a list of contributors (no context, decision, or consequences) docs/governance/2019-membership.md
D20 · ADR Quality
- No context/problem and no consequences; this is a pure minute-taking record with no real decision or trade-off discussion docs/governance/2019-plc-minutes.md
D20 · ADR Quality
- This is a list of member accounts with no context/problem and no decision; it contains only the author names docs/governance/2020-membership.md
D20 · ADR Quality
- This is a committee minutes record with no decision or consequences; the visible content is administrative rather than an architecture decision docs/governance/2020-plc-minutes.md
D20 · ADR Quality
- Decision (electing STV PLC and Schulze project leader) is explicit but the body is a minute listing motions, reports, and presentations with no context/problem or consequences/trade-offs docs/governance/2021-agm-minutes.md
D20 · ADR Quality
- This is a meeting record with no context/problem and no decision; the governance amendment is recorded but not explained docs/governance/2021-egm-minutes.md
D20 · ADR Quality
- This is a list of member accounts with no context/problem and no decision; it contains only names docs/governance/2021-membership.md
D20 · ADR Quality
- No context/problem and no explicit decision (TSC member appointments are administrative rather than an architecture decision) docs/governance/2021-plc-minutes.md
D20 · ADR Quality
- No context/problem and no explicit decision are stated (only procedural items such as voting passed, member presentations) docs/governance/2022-agm-minutes.md
D20 · ADR Quality
- This is a GitHub member list, not an architecture decision record docs/governance/2022-membership.md
D20 · ADR Quality
- No context/problem statement and no explicit decision; this is a full meeting minutes record rather than an ADR docs/governance/2023-agm-minutes.md
D20 · ADR Quality
- This is a Homebrew Annual General Meeting schedule with seating, reports, election results, and a long list of presentations/discussions; no context/problem or explicit decision is present docs/governance/2024-agm-minutes.md
D8 · Code Coverage
- Coverage not measured — test suite did not build
Recommendation — 7 finding(s)
D11 · Test Reliability
- Test reliability not included
D19 · Documentation Quality
- The README links to `brew bundle` but does not mention what happens when a formulae dependency is removed or updated (e.g. how to handle broken dependencies). README.md
D19 · Documentation Quality
- The Users section lists `Bottles`, `Taps`, and `Trusting Taps` but does not explain what happens when a bottle is removed from the repository. docs/index.md
D28 · Secrets (history)
- Rotate the exposed credentials — git history can't be un-committed
D31 · IaC & Container Security
- Low IaC: DS-0026 Dockerfile
D36 · Supply-chain Provenance & Signing
- No artifact signing
D9 · Test Distribution
- No tests found
Info — 1 finding(s)
D22 · Internal API Consistency
- No exposed public API
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --report-format json --report-path /dev/stdout --exit-code 0 --source . | 7 | artifacts/raw/gitleaks-history.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --json --quiet --timeout 0 --metrics off . | 20 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet (no .NET solution) | — | dotnet (no .NET solution): not present in this environment | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 1 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No PII/GDPR ruleset is bundled (the public p/gdpr semgrep pack was retired) — data compliance is not assessed in this scan. | 0 | — |
| D33 · JS/npm Dependency Vulnerabilities | trivy | — | trivy: not applicable — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D38 · OSV Dependency Vulnerabilities | osv-scanner | — | osv-scanner: not applicable — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan. | 0 | — |