All Reports
Zed
Rust
zed-industries/zed
Pass Rate
50%
High-performance, multiplayer code editor
L1100%
L2100%
L350%
L40%
L50%
Strong Testing
Zed reaches Level 3 with 67% Testing pass rate. Currently becoming autonomous-capable with 28/56 criteria passing (50%). Key areas for improvement include the opportunities listed below.
Strengths
01
Dead Code Detection
Rust compiler has built-in dead code detection via warnings for all applications.
02
Formatter
Formatter configured for all applications via rustfmt component in rust-toolchain.toml. Prettier also configured for non-Rust files.
03
Lint Config
Linter configured for all applications via clippy.toml at workspace root with disallowed methods and types.
Opportunities
01
Cyclomatic Complexity
Add complexity analysis to identify and refactor overly complex functions.
02
Monorepo Tooling
Consider Turborepo or Nx for better caching, incremental builds, and dependency graph awareness.
03
Test Coverage Thresholds
Establish minimum test coverage thresholds to prevent regression and maintain code quality.
All Criteria
Style & Validation6/11 (55%)
—code_modularizationSkipped: Rust compiler enforces module visibility and boundaries. No additional tooling needed.
✗cyclomatic_complexityNo cyclomatic complexity analysis configured. clippy.toml does not include complexity rules.
✓dead_code_detectionRust compiler has built-in dead code detection via warnings for all applications.
✗duplicate_code_detectionNo duplicate code detection tooling found. No jscpd, PMD CPD, or similar tools configured.
✓formatterFormatter configured for all applications via rustfmt component in rust-toolchain.toml. Prettier also configured for non-Rust files.
✗large_file_detectionNo large file detection tooling found. No Git LFS config, no CI checks for file size, no pre-commit hooks checking file size.
✓lint_configLinter configured for all applications via clippy.toml at workspace root with disallowed methods and types.
—n_plus_one_detectionSkipped: N+1 detection is for ORM/database usage. Only collab uses database (sea-orm) but no N+1 detection configured.
✗naming_consistencyNo naming consistency enforcement found beyond standard Rust conventions. No clippy naming rules, no documented conventions.
✗pre_commit_hooksNo pre-commit hooks configured. No .pre-commit-config.yaml, husky, or lint-staged found.
✓strict_typingRust enforces strict typing by default for all applications. Language compiler provides strong type safety.
✓tech_debt_trackingTech debt tracking via check-todos script in CI that enforces TODO/FIXME comments do not appear without proper tracking.
✓type_checkType checking via Rust compiler for all applications. rust-toolchain.toml specifies Rust 1.92 with clippy component.
Build System5/10 (50%)
✗agentic_developmentNo evidence of agent co-authorship in recent 100 commits. No factory-droid or other agent identifiers found in git log.
—automated_pr_reviewSkipped: No evidence of automated PR review generation tools found despite gh CLI being available.
✓build_cmd_docBuild command is documented under the docs/ folder
—build_performance_trackingSkipped: No build performance tracking or caching metrics found. No evidence of deliberate build time monitoring.
—dead_feature_flag_detectionSkipped: No dead feature flag detection tooling found despite feature_flag_infrastructure passing.
—deployment_frequencySkipped: Would require analyzing release frequency and workflow runs via gh CLI with repo-specific access.
✓deps_pinnedDependencies pinned via Cargo.lock which is committed to the repository.
—fast_ci_feedbackSkipped: Would require analyzing CI check durations via gh CLI, which requires repository-specific API access.
✓feature_flag_infrastructureFeature flag infrastructure exists via crates/feature_flags workspace member.
—heavy_dependency_detectionSkipped: Bundle size analysis not applicable for compiled Rust applications.
✗monorepo_toolingCargo workspace is used but no specialized monorepo tooling like Turborepo, Nx, or Lerna is configured.
—progressive_rolloutSkipped: Not applicable for desktop editor application. Progressive rollout is for deployed services, not packaged applications.
✓release_automationRelease automation exists via .github/workflows/release.yml triggered on version tags.
✗release_notes_automationNo automated release notes generation found. No semantic-release, standard-version, changesets, or release-please configuration.
—rollback_automationSkipped: Not applicable for desktop editor application. Rollback automation is for infrastructure, not desktop software.
✗single_command_setupREADME points to separate build docs per platform. No single command documented in README or AGENTS.md to go from clone to running dev server.
✗unused_dependencies_detectionNo unused dependencies detection configured. No cargo-udeps or similar tooling found in CI or scripts.
✓vcs_cli_toolsGitHub CLI (gh) is installed and available at /opt/homebrew/bin/gh.
—version_drift_detectionSkipped: Cargo workspace handles dependency versions uniformly, no drift detection tooling needed for Rust workspaces.
Testing4/6 (67%)
—flaky_test_detectionSkipped: No flaky test detection configured and gh CLI API access needed to analyze retry patterns.
✓integration_tests_existIntegration tests exist. collab has tests/integration_tests.rs, remote_server has remote_editing_tests.rs.
✗test_coverage_thresholdsNo test coverage thresholds configured. No coverage enforcement in CI, no codecov/coveralls integration.
✓test_isolationTest isolation via cargo nextest which runs tests in parallel for all applications.
✓test_naming_conventionsTest naming enforced by Rust #[test] attribute for all applications. Compiler requires proper test structure.
✗test_performance_trackingNo test performance tracking configured. CI runs nextest but does not output timing, upload reports, or track duration.
✓unit_tests_existUnit tests exist in all applications. Found #[test] and #[cfg(test)] in zed, cli, collab, and remote_server.
—unit_tests_runnableSkipped: requires admin access or fully configured local development environment for OSS evaluation.
Documentation3/7 (43%)
✓agents_mdAGENTS.md exists at repository root with substantial content (>100 chars) documenting Rust coding guidelines and GPUI framework.
✗agents_md_validationNo AGENTS.md validation automation found. No CI jobs testing commands, no pre-commit hooks, no automated updates.
—api_schema_docsSkipped: No OpenAPI/Swagger schemas found. Applications are desktop/server tools, not HTTP APIs.
✗automated_doc_generationNo automated documentation generation found. Docs are manually maintained, no doc generation workflows or tools configured.
✓documentation_freshnessDocumentation is fresh. README.md, AGENTS.md, and CONTRIBUTING.md all updated within last 180 days.
✓readmeREADME.md exists at repository root with installation instructions and links to platform-specific build documentation.
✗service_flow_documentedNo architecture diagrams found. Searched for .mermaid, .puml, .plantuml files and architecture documentation - none exist.
✗skillsNo skills directory found. Checked .factory/skills/, .skills/, .claude/skills/ - none exist.
Dev Environment1/4 (25%)
✗database_schemaDatabase schema exists for collab via sea-orm. Other applications (zed, cli, remote_server) do not use databases.
✗devcontainerNo dev container configuration found. No .devcontainer/devcontainer.json or .devcontainer.json exists.
—devcontainer_runnableSkipped: No devcontainer configuration exists, so runnability cannot be tested.
✗env_templateNo environment template file found. No .env.example, .env.sample, or environment variable documentation in README/AGENTS.md.
✓local_services_setupLocal services setup via compose.yml providing postgres, blob storage (minio), livekit server, and stripe-mock.
Debugging & Observability5/9 (56%)
✗alerting_configuredNo alerting infrastructure found. No PagerDuty, OpsGenie, or custom alerting rules configured.
—circuit_breakersSkipped: No circuit breaker pattern found. Desktop editor applications typically do not require resilience patterns for external calls.
—code_quality_metricsSkipped: requires admin API access not available for OSS evaluation.
✗deployment_observabilityNo deployment observability found. No dashboard links in docs, no deployment annotations or notifications configured.
✓distributed_tracingDistributed tracing implemented via trace_id and request_id propagation found in remote_client.rs and editor.rs.
✗error_tracking_contextualizedNo error tracking service configured. No Sentry, Bugsnag, or Rollbar integration found in any application.
✓health_checksHealth checks exist for collab server (found in main.rs). Desktop apps (zed, cli) and remote_server do not need health checks.
✓metrics_collectionMetrics collection via telemetry and telemetry_events workspace crates used across all applications.
✓profiling_instrumentationProfiling instrumentation exists. Performance.md documents profiling, tracy feature in zed crate, profiling crate in workspace.
✗runbooks_documentedNo runbook or playbook documentation found. No references to incident response procedures in README, AGENTS.md, or docs/.
✓structured_loggingStructured logging configured for all applications via zlog crate, env_logger, and tracing crate in workspace.
Security2/5 (40%)
—automated_security_reviewSkipped: requires admin API access not available for OSS evaluation.
—branch_protectionSkipped: requires admin API access not available for OSS evaluation.
✗codeownersNo CODEOWNERS file found in repository root or .github/ directory.
—dast_scanningSkipped: Not applicable for desktop applications and development servers. DAST is for deployed web services.
✓dependency_update_automationDependency update automation configured via renovate.json at repository root.
✓gitignore_comprehensiveComprehensive .gitignore properly excludes .env files, target/, .DS_Store, node_modules/, .idea, .vscode, and build artifacts.
✗log_scrubbingNo log scrubbing or sanitization mechanisms found. No redaction, masking, or filtering configured in zlog or logging setup.
—pii_handlingSkipped: No PII handling tooling found. Desktop applications do not typically require PII detection infrastructure.
—privacy_complianceSkipped: Not applicable for desktop editor application. Privacy policy exists but no user data collection infrastructure to evaluate.
—secret_scanningSkipped: requires admin API access not available for OSS evaluation.
✗secrets_managementNo secrets management infrastructure found. No integration with AWS Secrets Manager, GCP Secret Manager, Vault, or SOPS.
Task Discovery2/2 (100%)
—backlog_healthSkipped: requires gh CLI API access to analyze open issues for titles, labels, and staleness.
—issue_labeling_systemSkipped: Cannot verify consistent labeling system without API access.
✓issue_templatesIssue templates exist in .github/ISSUE_TEMPLATE/ with bug_report.yml and crash_report.yml.
✓pr_templatesPR template exists at .github/pull_request_template.md with sections for description and release notes.
Product & Analytics0/2 (0%)
✗error_to_insight_pipelineNo error-to-insight pipeline found. No Sentry-GitHub integration, no error-to-issue automation configured.
✗product_analytics_instrumentationNo product analytics SDK found. No Mixpanel, Amplitude, PostHog, Heap, or GA4 instrumentation detected.