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.
ray-project/ray carries serious gaps (43%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.
The area that most needs attention is Readiness (20%) — 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 (60%) is the next concern — exposure to security and compliance incidents is elevated.
Leadership focus, highest impact first: 2 Leaked secret finding(s) (Secret Scanning); 1 No tests found finding(s) in Test Distribution (Test Distribution); ILogger (or Serilog) and log at meaningful points across… (Observability).
For scale: Hobby (~0 production lines); rebuilding it from scratch would take roughly ~3.0 person-years (~1–6 engineers). Approximate, ±~30%.
Code Health
75%
Adequate · gated by D4
Architecture
63%
Adequate · gated by R9
Maturity
73%
Strong
Readiness
20% ⚠
Critical · gated by D9, D13, P2, P3, P5
Security
60%
Adequate · gated by D31, D38
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 20% · 47% weightSecurity 60% · 26% weightArchitecture 63% · 14% weightMaturity 73% · 8% weightCode Health 75% · 4% weight
Raise Readiness 20 → 70 (the Healthy floor) ⇒ headline 43 → ~64.
Code composition — where the lines go
Tests 100%
Top priorities
1
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with k8s_config.yaml, ray.default.conf.
2
Resolve the 1 No tests found finding(s) in Test Distribution.
3
Adopt ILogger (or Serilog) and log at meaningful points across the projects.
Diagnosis — what's actually going on
Highest-leverage move
Of everything flagged, the best return on effort is: Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with k8s_config.yaml, ray.default.conf. The rest can wait behind it.
At a glance — Code Health
The Good
D1 · .NET / C#
Cyclomatic Complexity
8.9
D2 · .NET / C#
Cognitive Complexity
7.5
D3 · .NET / C#
God Classes
10.0
R1 · React / TS
Type Safety
9.3
R2 · React / TS
Cyclomatic Complexity
8.7
R3 · React / TS
Large Files
8.4
R7 · React / TS
Dead Code
8.2
X1 · Repo
Async correctness
10.0
X3 · Repo
Exception handling
10.0
X4 · Repo
Structured logging
10.0
The Ugly
At a glance — Architecture
The Good
The Ugly
At a glance — Maturity
The Good
The Ugly
At a glance — Readiness
The Good
The Bad
The Ugly
At a glance — Security
The Good
The Ugly
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2021 — Security Misconfiguration | 50 | High / Critical |
| A06:2021 — Vulnerable & Outdated Components | 50 | High / Critical |
| A02:2021 — Cryptographic Failures | 6 | High / Critical |
Roadmap
Begin by resolving the two leaked secrets in k8s_config.yaml and ray.default.conf to secure sensitive data. Next, address the missing test coverage and implement structured logging with ILogger or Serilog to improve observability. Finally, codify disaster recovery backups in infrastructure as code, and add readiness probes and rolling update strategies to ensure safe deployments and automatic rollbacks.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with k8s_config.yaml, ray.default.conf. | +22.6 pts | Low | Secret Scanning |
| Resolve the 1 No tests found finding(s) in Test Distribution. | +22.6 pts | Low | Test Distribution |
| Adopt ILogger (or Serilog) and log at meaningful points across the projects. | +22.6 pts | Medium | Observability |
| Codify backups + geo-recovery in IaC (snapshot/replication/geo-redundant) to back the DR plan. | +22.1 pts | Medium | DR & Backup |
| Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically. | +20.8 pts | Medium | Deployment & Rollback |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +20.1 pts | Medium | Dependency Hygiene |
| Add the missing tooling (eslint, tsc) as package.json scripts and run them in CI. | +15.6 pts | Medium | Tooling |
| Bump outdated dependencies to current versions to limit upgrade debt. | +12.3 pts | Medium | Dependency Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| python/ray/dashboard/client/package-lock.json | 4.4 | Mixed | OSV Dependency Vulnerabilities: Critical CVE: [GHSA redacted] |
| ci/raydepsets/tests/test_data/requirements_compiled_large_test.txt | 4.4 | Mixed | OSV Dependency Vulnerabilities: High CVE: [GHSA redacted] |
| python/requirements/ml/core-requirements.txt | 4.4 | Mixed | OSV Dependency Vulnerabilities: Critical CVE: [GHSA redacted] |
| ci/docker/ml.build.Dockerfile | 5.1 | Mixed | IaC & Container Security: Critical IaC: DS-0010 |
| ci/docker/runtime_env_container/Dockerfile | 5.1 | Mixed | IaC & Container Security: Critical IaC: DS-0010 |
| python/requirements/test-requirements.txt | 5.1 | Mixed | OSV Dependency Vulnerabilities: Critical CVE: [GHSA redacted] |
| ci/docker/rllib.build.Dockerfile | 5.8 | Mixed | IaC & Container Security: Critical IaC: DS-0010 |
| doc/source/templates/testing/docker/04_finetuning_llms_with_deepspeed/Dockerfile | 5.8 | Mixed | IaC & Container Security: Critical IaC: DS-0010 |
| release/workspace_templates/testing/docker/04_finetuning_llms_with_deepspeed/Dockerfile | 5.8 | Mixed | IaC & Container Security: Critical IaC: DS-0010 |
| .buildkite/release-automation/forge_arm64.Dockerfile | 5.8 | Mixed | IaC & Container Security: High IaC: DS-0002 |
| ci/docker/base.build.Dockerfile | 5.8 | Mixed | IaC & Container Security: High IaC: DS-0002 |
| ci/docker/base.gpu.Dockerfile | 5.8 | Mixed | IaC & Container Security: High IaC: DS-0002 |
| ci/docker/base.test.Dockerfile | 5.8 | Mixed | IaC & Container Security: High IaC: DS-0002 |
| ci/docker/data.build.Dockerfile | 5.8 | Mixed | IaC & Container Security: High IaC: DS-0002 |
| ci/docker/doctest.build.Dockerfile | 5.8 | Mixed | IaC & Container Security: High IaC: DS-0002 |
| python/requirements/ml/tune-test-requirements.txt | 5.8 | Mixed | OSV Dependency Vulnerabilities: Critical CVE: [GHSA redacted] |
| release/air_examples/dreambooth/dreambooth/requirements.txt | 5.8 | Mixed | OSV Dependency Vulnerabilities: Critical CVE: [GHSA redacted] |
| release/ray_release/byod/requirements_ml_byod_3.10.txt | 5.8 | Mixed | OSV Dependency Vulnerabilities: Critical CVE: [GHSA redacted] |
| java/serve/src/main/java/io/ray/serve/config/DeploymentConfig.java | 7.0 | Mixed | Code Duplication: Duplicated block (23 lines × 2) |
| java/runtime/src/main/java/io/ray/runtime/util/generator/RayCallGenerator.java | 7.2 | Mixed | Code Duplication: Duplicated block (117 lines × 2) |
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. 40 of 43 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 — 43 dimensions across the health lenses
D1D2D3D4D5D7D9D12D13D19D20D21D26D27D28D29D31D33D37D38AX5M1M2M3M4P1P2P3P4P5R1R10R2R3R4R5R6R7R8R9X1X3X4
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, 147 of 155 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.
- D36 Supply-chain Provenance & Signing — 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
- 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 (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").
- 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.
- D33 JS/npm Dependency Vulnerabilities: JS/npm CVE matching reads package manifests and lockfiles — risk from how a dependency is used, and advisories not yet published, fall outside this scan.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
The LLM boundary
Dimensions
D1 · Cyclomatic Complexity
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RayConfig.<init> at 28.
constructor (cyclomatic 19)doc/source/_static/js/termynal.js:30
What to do
- Resolve the 1 constructor (cyclomatic 19) finding(s) in Cyclomatic Complexity — start with termynal.js. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cyclomatic Complexity 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?
D2 · Cognitive Complexity
19 method(s) exceeded the cognitive complexity threshold of 15; the worst was ParallelActorCallGenerator.buildCalls at 40.
constructor (cognitive 18)doc/source/_static/js/termynal.js:30
(anonymous) (cognitive 17)doc/source/_static/api-nav-loader.js:26
What to do
- Resolve the 1 constructor (cognitive 18) finding(s) in Cognitive Complexity — start with termynal.js. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 (anonymous) (cognitive 17) finding(s) in Cognitive Complexity — start with api-nav-loader.js. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cognitive Complexity 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?
D3 · God Classes
0 god class(es) detected.
Do you agree with this assessment?
D4 · Code Duplication
36 duplicated block group(s) detected.
Duplicated block (23 lines × 2) java/api/src/main/java/io/ray/api/parallelactor/Call.java:21
Duplicated block (6 lines × 2) java/api/src/main/java/io/ray/api/PyActorCall.java:19
Duplicated block (5 lines × 2) java/api/src/main/java/io/ray/api/PyActorCall.java:30
Duplicated block (117 lines × 2) java/runtime/src/main/java/io/ray/runtime/util/generator/RayCallGenerator.java:230
Duplicated block (22 lines × 2) java/serve/src/main/java/io/ray/serve/config/DeploymentConfig.java:121
What to do
- Resolve the 9 Duplicated block (23 lines × 2) finding(s) in Code Duplication — start with DeploymentConfig.java (8), Call.java. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with GcsClient.java, PyActorCall.java, ServeControllerClient.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with AbstractRayRuntime.java, NativeTaskSubmitter.java, PyActorCall.java. — One of this dimension's main actionable groups (3 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.
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 0 mechanizable ADRs, 0 are prevented by analyzers, 0 by tests, 0 exist only in prose. Coverage: 100 %. Cycles found: 0.
What to do
- Enforce Architectural Integrity 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?
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
2 secret(s) detected.
Leaked secret: hardcoded-credential doc/source/serve/doc_code/fault_tolerance/k8s_config.yaml:89
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with k8s_config.yaml, ray.default.conf. — One of this dimension's main actionable groups (2 issue-level).
- Enforce Secret Scanning 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?
D19 · Documentation Quality
Ray's documentation is clear and complete for a unified framework: an excellent README with a header badge plus a detailed What-is-Ray section explaining core components and AI libraries; Buildkite pipeline docs covering *.rayci.yml files, test-rules.txt ordering, and the CI reference implementation; a dedicated doc/README.md that explains MyST Markdown usage, dependency installation, building from source, subproject builds, announcement/includes, broken-link checking, and Docker image build notes; and Java-specific instructions. The outline is visible in every clipped document (e.g., '## Announcements and includes' exists).
The Java test instructions are cut mid-sentence, so the full run command and custom-test subcommand are not visible.java/README.md
What to do
- Resolve the 1 The Java test instructions are cut mid-sentence, so the full run command… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D20 · ADR Quality
Evaluated 1 ADR(s) individually; mean quality 1.5/10 (frequently incomplete). 1 flagged with a specific gap.
This is a duplicate 'Page not found' title with no context/problem and no decision; only an orphan metadata marker explains its purposedoc/source/404.md
What to do
- Resolve the 1 This is a duplicate 'Page not found' title with no context/problem and… finding(s) in ADR Quality — start with 404.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)
4 finding(s): 0 critical, 4 high, 0 medium, 0 low.
Secret: square-access-token doc/requirements-doc.lock.txt:978
What to do
- Resolve the 4 Secret finding(s) in Secrets (history) — start with docbuild_depset_py3.11.lock, ml_torchft_py3.13.lock, ray-torch-cu128_base_py3.14.lock. — One of this dimension's main actionable groups (4 issue-level).
Do you agree with this assessment?
D29 · Static Analysis (SAST)
semgrep found no security issues.
Do you agree with this assessment?
D31 · IaC & Container Security
222 finding(s): 11 critical, 74 high, 42 medium, 95 low.
High IaC: DS-0002 .buildkite/release-automation/forge_arm64.Dockerfile
Critical IaC: DS-0010 ci/docker/ml.build.Dockerfile
What to do
- Resolve the 39 High IaC finding(s) in IaC & Container Security — start with Dockerfile (2), base.build.Dockerfile (2), base.gpu.Dockerfile (2). — One of this dimension's main actionable groups (39 issue-level).
- Resolve the 11 Critical IaC finding(s) in IaC & Container Security — start with Dockerfile (9), ml.build.Dockerfile, rllib.build.Dockerfile. — One of this dimension's main actionable groups (11 issue-level).
Do you agree with this assessment?
D33 · JS/npm Dependency Vulnerabilities
No known-vulnerable JS/npm dependencies.
Do you agree with this assessment?
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
Do you agree with this assessment?
D38 · OSV Dependency Vulnerabilities
787 finding(s): 22 critical, 196 high, 509 medium, 60 low.
High CVE: [GHSA redacted] ci/raydepsets/tests/test_data/requirements_compiled_large_test.txt
Critical CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
What to do
- Resolve the 28 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (19), requirements_compiled_large_test.txt (9). — One of this dimension's main actionable groups (28 issue-level).
- Resolve the 22 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with core-requirements.txt (7), package-lock.json (4), test-requirements.txt (3). — One of this dimension's main actionable groups (22 issue-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
What to do
- Grow the ADR log (currently 1) — reach 8 to raise the maturity tier; document significant decisions as they're made.
Do you agree with this assessment?
M3 · Folder & project structure
- 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 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
- A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (dotnet test / npm test / pytest / a test job) was matched — the gate may be running tests, or "test" may be incidental (a path, "latest", a reporter). Make the test step explicit so the gate is unambiguous.
What to do
- Run the test suite in CI via an explicit runner step (e.g. `dotnet test`) and gate merges on it.
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
- No static application security testing (CodeQL / security analyzers / codehealth) detected.
What to do
- Add a SAST step (e.g. CodeQL) or a security analyzer package.
- 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.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup
What to do
- Codify backups + geo-recovery in IaC (snapshot/replication/geo-redundant) to back the DR plan.
- Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
Do you agree with this assessment?
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
Do you agree with this assessment?
R10 · Code Duplication
- python/ray/dashboard/client/src/components/ActorTable.tsx:275 · python/ray/dashboard/client/src/components/ActorTable.tsx:301 — ActorTable.tsx:275
- python/ray/dashboard/client/src/common/links.tsx:8 · python/ray/dashboard/client/src/common/links.tsx:43 — links.tsx:8
- python/ray/dashboard/client/src/components/ActorTable.tsx:208 · python/ray/dashboard/client/src/pages/node/index.tsx:58 — ActorTable.tsx:208
- python/ray/dashboard/client/src/pages/serve/ServeEntityLogViewer.component.test.tsx:76 · python/ray/dashboard/client/src/pages/serve/ServeEntityLogViewer.component.test.tsx:264 — ServeEntityLogViewer.component.test.tsx:76
- python/ray/dashboard/client/src/common/timezone.ts:21 · python/ray/dashboard/client/src/pages/layout/MainNavLayout.tsx:75 — timezone.ts:21
- python/ray/dashboard/client/src/pages/job/hook/useJobProgress.unit.test.ts:54 · python/ray/dashboard/client/src/pages/log/Logs.component.test.tsx:30 — useJobProgress.unit.test.ts:54
- python/ray/dashboard/client/src/pages/job/index.tsx:180 · python/ray/dashboard/client/src/pages/node/index.tsx:428 — index.tsx:180
- python/ray/dashboard/client/src/pages/layout/MainNavLayout.tsx:102 · python/ray/dashboard/client/src/pages/overview/cards/RecentJobsCard.component.test.tsx:27 — MainNavLayout.tsx:102
What to do
- Extract the duplicated blocks into shared functions/components.
Do you agree with this assessment?
R2 · Cyclomatic Complexity
- Branch-heavy code is where defects cluster — extract decisions into smaller functions. (×8) — ServeEntityLogViewer.tsx:32, ActorTable.tsx:613, ActorDetail.tsx:53, …
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files
What to do
- Split the oversized components into smaller, focused ones.
Do you agree with this assessment?
R4 · Test Coverage
- No test imports this module directly or transitively — its behavior is unverified. (×8) — mockedUseActorList.ts, SortableTableHead.tsx, mockServeApplication.ts, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗
What to do
- Add the missing tooling (eslint, tsc) as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code
- Unreachable from the 1 application, 10 tooling and 40 test entry point(s) detected in this repo. Gate removals on your build/type-check — an undetected custom entry would make these reachable.
- no import path from any entry point (1 application, 10 tooling, 40 test roots considered) (×7) — mockedUseActorList.ts, SortableTableHead.tsx, mockServeApplication.ts, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
Do you agree with this assessment?
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — LogVirtualView.tsx:3
- Declared in python/ray/dashboard/client/package.json but never imported anywhere in that package or its workspace members — dead weight and attack surface. Verify against build tooling before removing. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Do you agree with this assessment?
R9 · Circular Imports
- python/ray/dashboard/client/src/App.tsx → python/ray/dashboard/client/src/common/MultiTabLogViewer.tsx → python/ray/dashboard/client/src/components/ActorTable.tsx → python/ray/dashboard/client/src/components/EventTable.tsx → python/ray/dashboard/client/src/components/WorkerTable.tsx → python/ray/dashboard/client/src/pages/actor/ActorDetail.tsx → python/ray/dashboard/client/src/pages/actor/ActorList.tsx → python/ray/dashboard/client/src/pages/actor/ActorLogs.tsx → python/ray/dashboard/client/src/pages/actor/hook/useActorDetail.ts → python/ray/dashboard/client/src/pages/actor/index.tsx → python/ray/dashboard/client/src/pages/cmd/CMDResult.tsx → python/ray/dashboard/client/src/pages/job/JobDetail.tsx → python/ray/dashboard/client/src/pages/job/JobDetailActorPage.tsx → python/ray/dashboard/client/src/pages/job/JobDriverLogs.tsx → python/ray/dashboard/client/src/pages/layout/MainNavLayout.tsx → python/ray/dashboard/client/src/pages/log/LogViewer.tsx → python/ray/dashboard/client/src/pages/log/Logs.tsx → python/ray/dashboard/client/src/pages/metrics/Metrics.tsx → python/ray/dashboard/client/src/pages/metrics/index.ts → python/ray/dashboard/client/src/pages/node/NodeDetail.tsx → python/ray/dashboard/client/src/pages/node/hook/useNodeDetail.ts → python/ray/dashboard/client/src/pages/overview/OverviewPage.tsx → python/ray/dashboard/client/src/pages/overview/cards/ClusterUtilizationCard.tsx → python/ray/dashboard/client/src/pages/overview/cards/NodeCountCard.tsx → python/ray/dashboard/client/src/pages/overview/cards/RecentServeCard.tsx → python/ray/dashboard/client/src/pages/serve/ServeApplicationDetailPage.tsx → python/ray/dashboard/client/src/pages/serve/ServeApplicationRow.tsx → python/ray/dashboard/client/src/pages/serve/ServeDeploymentDetailPage.tsx → python/ray/dashboard/client/src/pages/serve/ServeDeploymentMetricsSection.tsx → python/ray/dashboard/client/src/pages/serve/ServeDeploymentRow.tsx → python/ray/dashboard/client/src/pages/serve/ServeDeploymentsListPage.tsx → python/ray/dashboard/client/src/pages/serve/ServeEntityLogViewer.tsx → python/ray/dashboard/client/src/pages/serve/ServeMetricsSection.tsx → python/ray/dashboard/client/src/pages/serve/ServeReplicaDetailLayout.tsx → python/ray/dashboard/client/src/pages/serve/ServeReplicaDetailPage.tsx → python/ray/dashboard/client/src/pages/serve/ServeSystemActorDetailPage.tsx → python/ray/dashboard/client/src/pages/serve/ServeSystemDetailPage.tsx → python/ray/dashboard/client/src/pages/serve/ServeSystemDetailRows.tsx → python/ray/dashboard/client/src/pages/serve/ServeSystemDetails.tsx → python/ray/dashboard/client/src/pages/serve/hook/useServeApplications.ts → python/ray/dashboard/client/src/pages/task/TaskPage.tsx → python/ray/dashboard/client/src/App.tsx — App.tsx
- python/ray/dashboard/client/src/type/actor.ts → python/ray/dashboard/client/src/type/node.d.ts → python/ray/dashboard/client/src/type/actor.ts — actor.ts
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
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 | 75% | Adequate — gated by D4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 63% | Adequate — gated by R9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 73% | Strong | Strongest area. |
| Readiness | 20% | Critical — gated by D9, D13, P2, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 60% | Adequate — gated by D31, D38 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not included — 60 check(s) not relevant to this codebase
- AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC7 A11y enforcement — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- 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.
- D10 Test Quality — ~499373 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
- D15 Churn × Complexity Hotspots — single-commit history — no usable git history window to measure hotspots
- D16 Bus Factor — single-maintainer — knowledge-concentration (bus factor) risk
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — Dimension evaluation failed
- 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 1 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.
- D34 Knowledge Freshness — early-stage repository — too little history to judge knowledge freshness
- D35 Change Coupling — no production change history to mine for change-coupling
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a NuGet package, a container image, a GitHub release).
- 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 — only 1/3 markers (17 value object(s))
- 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
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
- 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- 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.
- SC1 Supply-chain hygiene — no data
- X2 Cancellation propagation — no async methods found
- X5 Nullable reference types — no NRT-eligible projects
Appendix A — Findings (grouped)
Issue — 107 finding(s)
D31 · IaC & Container Security
- High IaC: DS-0002 .buildkite/release-automation/forge_arm64.Dockerfile
- High IaC: DS-0029 .buildkite/release-automation/forge_arm64.Dockerfile
- High IaC: DS-0029 .buildkite/release-automation/forge_x86_64.Dockerfile
- High IaC: DS-0002 ci/docker/base.build.Dockerfile
- High IaC: DS-0029 ci/docker/base.build.Dockerfile
- High IaC: DS-0002 ci/docker/base.gpu.Dockerfile
- High IaC: DS-0029 ci/docker/base.gpu.Dockerfile
- High IaC: DS-0002 ci/docker/base.ml.Dockerfile
- High IaC: DS-0002 ci/docker/base.test.Dockerfile
- High IaC: DS-0029 ci/docker/base.test.Dockerfile
- High IaC: DS-0002 ci/docker/core.build.Dockerfile
- High IaC: DS-0002 ci/docker/custom-vllm-plugin.build.Dockerfile
- High IaC: DS-0002 ci/docker/data.build.Dockerfile
- High IaC: DS-0029 ci/docker/data.build.Dockerfile
- High IaC: DS-0002 ci/docker/datatfds.build.Dockerfile
- High IaC: DS-0002 ci/docker/doc.build.Dockerfile
- High IaC: DS-0002 ci/docker/docgpu.build.Dockerfile
- High IaC: DS-0002 ci/docker/doctest.build.Dockerfile
- High IaC: DS-0029 ci/docker/doctest.build.Dockerfile
- High IaC: DS-0029 ci/docker/forge.Dockerfile
- High IaC: DS-0002 ci/docker/k8s.build.Dockerfile
- High IaC: DS-0002 ci/docker/llm.build.Dockerfile
- High IaC: DS-0002 ci/docker/manylinux-retag.Dockerfile
- High IaC: DS-0015 ci/docker/manylinux.Dockerfile
- High IaC: DS-0002 ci/docker/min.build.Dockerfile
D38 · OSV Dependency Vulnerabilities
- High CVE: [GHSA redacted] ci/raydepsets/tests/test_data/requirements_compiled_large_test.txt
- High CVE: [GHSA redacted] ci/raydepsets/tests/test_data/requirements_compiled_large_test.txt
- High CVE: [GHSA redacted] ci/raydepsets/tests/test_data/requirements_compiled_large_test.txt
- High CVE: [GHSA redacted] ci/raydepsets/tests/test_data/requirements_compiled_large_test.txt
- High CVE: [GHSA redacted] ci/raydepsets/tests/test_data/requirements_compiled_large_test.txt
- High CVE: [GHSA redacted] ci/raydepsets/tests/test_data/requirements_compiled_large_test.txt
- High CVE: [GHSA redacted] ci/raydepsets/tests/test_data/requirements_compiled_large_test.txt
- High CVE: [GHSA redacted] ci/raydepsets/tests/test_data/requirements_compiled_large_test.txt
- High CVE: [GHSA redacted] ci/raydepsets/tests/test_data/requirements_compiled_large_test.txt
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- High CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
D38 · OSV Dependency Vulnerabilities
- Critical CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- Critical CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- Critical CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- Critical CVE: [GHSA redacted] python/ray/dashboard/client/package-lock.json
- Critical CVE: [GHSA redacted] python/requirements/ml/core-requirements.txt
- Critical CVE: [GHSA redacted] python/requirements/ml/core-requirements.txt
- Critical CVE: [GHSA redacted] python/requirements/ml/core-requirements.txt
- Critical CVE: [GHSA redacted] python/requirements/ml/core-requirements.txt
- Critical CVE: [GHSA redacted] python/requirements/ml/core-requirements.txt
- Critical CVE: [GHSA redacted] python/requirements/ml/core-requirements.txt
- Critical CVE: [GHSA redacted] python/requirements/ml/core-requirements.txt
- Critical CVE: [GHSA redacted] python/requirements/ml/train-requirements.txt
- Critical CVE: [GHSA redacted] python/requirements/ml/tune-test-requirements.txt
- Critical CVE: [GHSA redacted] python/requirements/ml/tune-test-requirements.txt
- Critical CVE: [GHSA redacted] python/requirements/test-requirements.txt
- Critical CVE: [GHSA redacted] python/requirements/test-requirements.txt
- Critical CVE: [GHSA redacted] python/requirements/test-requirements.txt
- Critical CVE: [GHSA redacted] python/requirements_compiled.txt
- Critical CVE: [GHSA redacted] release/air_examples/dreambooth/dreambooth/requirements.txt
- Critical CVE: [GHSA redacted] release/air_examples/dreambooth/dreambooth/requirements.txt
- Critical CVE: [GHSA redacted] release/ray_release/byod/requirements_ml_byod_3.10.txt
- Critical CVE: [GHSA redacted] release/ray_release/byod/requirements_ml_byod_3.10.txt
D31 · IaC & Container Security
- Critical IaC: DS-0010 ci/docker/ml.build.Dockerfile
- Critical IaC: DS-0010 ci/docker/rllib.build.Dockerfile
- Critical IaC: DS-0010 ci/docker/runtime_env_container/Dockerfile
- Critical IaC: DS-0010 doc/source/templates/testing/docker/04_finetuning_llms_with_deepspeed/Dockerfile
- Critical IaC: DS-0010 doc/source/templates/testing/docker/04_finetuning_llms_with_deepspeed/Dockerfile
- Critical IaC: DS-0010 docker/ray-llm/Dockerfile
- Critical IaC: DS-0010 docker/ray-ml/Dockerfile
- Critical IaC: DS-0010 docker/ray-torch/Dockerfile
- Critical IaC: DS-0010 docker/ray/Dockerfile
- Critical IaC: DS-0010 release/workspace_templates/testing/docker/04_finetuning_llms_with_deepspeed/Dockerfile
- Critical IaC: DS-0010 release/workspace_templates/testing/docker/04_finetuning_llms_with_deepspeed/Dockerfile
D28 · Secrets (history)
- Secret: square-access-token doc/requirements-doc.lock.txt:978
- Secret: square-access-token python/deplocks/docs/docbuild_depset_py3.11.lock:978
- Secret: square-access-token python/deplocks/ray-torch/ray-torch-cu128_base_py3.14.lock:3085
- Secret: square-access-token release/ray_release/byod/ml_torchft_py3.13.lock:6112
D13 · Secret Scanning
- Leaked secret: hardcoded-credential doc/source/serve/doc_code/fault_tolerance/k8s_config.yaml:89
- Leaked secret: hardcoded-credential java/runtime/src/main/resources/ray.default.conf:117
D18 · Solution Shape
- Dimension evaluation failed
Warning — 42 finding(s)
D4 · Code Duplication
- Duplicated block (23 lines × 2) java/api/src/main/java/io/ray/api/parallelactor/Call.java:21
- Duplicated block (23 lines × 2) java/serve/src/main/java/io/ray/serve/config/DeploymentConfig.java:121
- Duplicated block (23 lines × 2) java/serve/src/main/java/io/ray/serve/config/DeploymentConfig.java:121
- Duplicated block (23 lines × 2) java/serve/src/main/java/io/ray/serve/config/DeploymentConfig.java:121
- Duplicated block (23 lines × 2) java/serve/src/main/java/io/ray/serve/config/DeploymentConfig.java:121
- Duplicated block (23 lines × 2) java/serve/src/main/java/io/ray/serve/config/DeploymentConfig.java:121
- Duplicated block (23 lines × 2) java/serve/src/main/java/io/ray/serve/config/DeploymentConfig.java:121
- Duplicated block (23 lines × 2) java/serve/src/main/java/io/ray/serve/config/DeploymentConfig.java:121
- Duplicated block (23 lines × 2) java/serve/src/main/java/io/ray/serve/config/DeploymentConfig.java:133
D4 · Code Duplication
- Duplicated block (6 lines × 2) java/api/src/main/java/io/ray/api/PyActorCall.java:19
- Duplicated block (6 lines × 2) java/runtime/src/main/java/io/ray/runtime/gcs/GcsClient.java:84
- Duplicated block (6 lines × 2) java/serve/src/main/java/io/ray/serve/api/ServeControllerClient.java:236
D4 · Code Duplication
- Duplicated block (5 lines × 2) java/api/src/main/java/io/ray/api/PyActorCall.java:30
- Duplicated block (5 lines × 2) java/runtime/src/main/java/io/ray/runtime/task/NativeTaskSubmitter.java:32
- Duplicated block (5 lines × 2) java/runtime/src/main/java/io/ray/runtime/AbstractRayRuntime.java:325
D4 · Code Duplication
- Duplicated block (117 lines × 2) java/runtime/src/main/java/io/ray/runtime/util/generator/RayCallGenerator.java:230
- Duplicated block (117 lines × 2) java/serve/src/main/java/io/ray/serve/deployment/DeploymentCreator.java:126
D4 · Code Duplication
- Duplicated block (22 lines × 2) java/serve/src/main/java/io/ray/serve/config/DeploymentConfig.java:121
- Duplicated block (22 lines × 2) java/serve/src/main/java/io/ray/serve/config/DeploymentConfig.java:122
D4 · Code Duplication
- Duplicated block (9 lines × 2) java/runtime/src/main/java/io/ray/runtime/util/generator/ParallelActorCallGenerator.java:24
- Duplicated block (9 lines × 2) java/serve/src/main/java/io/ray/serve/config/DeploymentConfig.java:243
D1 · Cyclomatic Complexity
- constructor (cyclomatic 19) doc/source/_static/js/termynal.js:30
D16 · Bus Factor
- single-maintainer — knowledge-concentration (bus factor) risk
D2 · Cognitive Complexity
- constructor (cognitive 18) doc/source/_static/js/termynal.js:30
D2 · Cognitive Complexity
- (anonymous) (cognitive 17) doc/source/_static/api-nav-loader.js:26
D20 · ADR Quality
- This is a duplicate 'Page not found' title with no context/problem and no decision; only an orphan metadata marker explains its purpose doc/source/404.md
D4 · Code Duplication
- Duplicated block (980 lines × 3) java/api/src/main/java/io/ray/api/parallelactor/Call.java:208
D4 · Code Duplication
- Duplicated block (790 lines × 3) java/api/src/main/java/io/ray/api/RayCall.java:510
D4 · Code Duplication
- Duplicated block (744 lines × 2) java/api/src/main/java/io/ray/api/parallelactor/ActorCall.java:322
D4 · Code Duplication
- Duplicated block (470 lines × 3) java/api/src/main/java/io/ray/api/RayCall.java:1468
D4 · Code Duplication
- Duplicated block (396 lines × 2) java/api/src/main/java/io/ray/api/ActorCall.java:76
D4 · Code Duplication
- Duplicated block (97 lines × 2) java/runtime/src/main/java/io/ray/runtime/functionmanager/FunctionManager.java:65
D4 · Code Duplication
- Duplicated block (92 lines × 2) java/runtime/src/main/java/io/ray/runtime/metric/Metrics.java:2
D4 · Code Duplication
- Duplicated block (40 lines × 2) java/runtime/src/main/java/io/ray/runtime/util/generator/RayCallGenerator.java:107
D4 · Code Duplication
- Duplicated block (39 lines × 2) java/serve/src/main/java/io/ray/serve/deployment/DeploymentWrapper.java:30
D4 · Code Duplication
- Duplicated block (24 lines × 2) java/api/src/main/java/io/ray/api/concurrencygroup/BaseConcurrencyGroupBuilder.java:25
D4 · Code Duplication
- Duplicated block (20 lines × 2) java/api/src/main/java/io/ray/api/RayCall.java:1313
D4 · Code Duplication
- Duplicated block (13 lines × 3) java/runtime/src/main/java/io/ray/runtime/util/generator/RayCallGenerator.java:18
D4 · Code Duplication
- Duplicated block (12 lines × 2) java/api/src/main/java/io/ray/api/CppActorCall.java:23
D4 · Code Duplication
- Duplicated block (8 lines × 2) java/runtime/src/main/java/io/ray/runtime/util/generator/ParallelActorCallGenerator.java:160
D4 · Code Duplication
- Duplicated block (7 lines × 3) java/runtime/src/main/java/io/ray/runtime/util/generator/RayCallGenerator.java:96
D8 · Code Coverage
- Coverage not measured — test suite did not build
Recommendation — 5 finding(s)
D11 · Test Reliability
- Test reliability not included
D15 · Churn × Complexity Hotspots
- single-commit history — no usable git history window to measure hotspots
D19 · Documentation Quality
- The Java test instructions are cut mid-sentence, so the full run command and custom-test subcommand are not visible. java/README.md
D34 · Knowledge Freshness
- early-stage repository — too little history to judge knowledge freshness
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 . | 4 | 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 . | 0 | — |
| 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 . | 222 | 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 fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a NuGet package, a container image, a GitHub release). | 0 | — |
| D38 · OSV Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive . | 787 | artifacts/raw/osv-scanner.json |