All Reports
Chi
Go
go-chi/chi
Pass Rate
31%
Lightweight, idiomatic and composable router for building Go HTTP services
L1100%
L255%
L30%
L40%
L50%
Strong Build System
Chi reaches Level 2 with 50% Build System pass rate. Currently building team readiness with 17/54 criteria passing (31%). Key areas for improvement include the opportunities listed below.
Strengths
01
Formatter
CONTRIBUTING.md mentions goimports for formatting. Go fmt is standard.
02
Strict Typing
Go has strict typing enforced by compiler by default.
03
Type Check
Go is statically typed by default with compile-time type checking.
Opportunities
01
Cyclomatic Complexity
No complexity analysis tools configured. No gocyclo, go-critic, or SonarQube.
02
Dead Code Detection
No dead code detection tools configured. No staticcheck or similar tools in CI.
03
Duplicate Code Detection
No duplicate code detection tools configured. No jscpd, PMD CPD, or SonarQube.
All Criteria
Style & Validation3/11 (27%)
—code_modularizationSmall library project where module boundaries are not meaningful. Skipped.
✗cyclomatic_complexityNo complexity analysis tools configured. No gocyclo, go-critic, or SonarQube.
✗dead_code_detectionNo dead code detection tools configured. No staticcheck or similar tools in CI.
✗duplicate_code_detectionNo duplicate code detection tools configured. No jscpd, PMD CPD, or SonarQube.
✓formatterCONTRIBUTING.md mentions goimports for formatting. Go fmt is standard.
✗large_file_detectionNo large file detection configured. No git hooks, CI checks, or LFS setup.
✗lint_configNo linter configured. No golangci-lint, staticcheck, or other Go linters in CI or project config.
—n_plus_one_detectionHTTP router library with no database/ORM usage. Not applicable, skipped.
✗naming_consistencyNo enforced naming conventions via linter rules or documented conventions.
✗pre_commit_hooksNo pre-commit hooks configured. No .pre-commit-config.yaml or husky setup.
✓strict_typingGo has strict typing enforced by compiler by default.
✗tech_debt_trackingNo tech debt tracking configured. No TODO/FIXME scanner in CI or SonarQube.
✓type_checkGo is statically typed by default with compile-time type checking.
Build System5/10 (50%)
✗agentic_developmentNo agent co-authorship in git log. No factory-droid or other agent identifiers found.
—automated_pr_reviewNo evidence of automated review bots or danger.js in PRs. Skipped (requires gh CLI).
✓build_cmd_docREADME documents installation with 'go get -u github.com/go-chi/chi/v5'. Makefile has test commands.
—build_performance_trackingNo build caching or performance tracking configured. Skipped (requires gh CLI).
—dead_feature_flag_detectionNo feature flag infrastructure exists, so dead flag detection is not applicable. Skipped.
—deployment_frequencyLibrary repository, not a deployed service. Deployment frequency not applicable, skipped.
✓deps_pinnedGo module with go.mod. Library has no external dependencies to pin. Satisfied by go.mod existence.
✓fast_ci_feedbackCI completes in ~2 minutes based on PR status checks (well under 10 min threshold).
✗feature_flag_infrastructureNo feature flag infrastructure. No LaunchDarkly, Statsig, Unleash, or GrowthBook.
—heavy_dependency_detectionBackend library, not a bundled application. Bundle size analysis not applicable, skipped.
—monorepo_toolingSingle application repository, not a monorepo. Not applicable, skipped.
—progressive_rolloutLibrary repository, not an infrastructure/deployed service. Not applicable, skipped.
✗release_automationNo automated release pipeline. Releases are manual, no CD workflow or semantic-release.
✗release_notes_automationReleases exist but no automation. No semantic-release, standard-version, or changesets.
—rollback_automationLibrary repository, not an infrastructure/deployed service. Not applicable, skipped.
✓single_command_setupREADME documents single command setup: 'go get -u github.com/go-chi/chi/v5'.
✗unused_dependencies_detectionNo unused dependency detection. No 'go mod tidy' in CI or dependency analysis tools.
✓vcs_cli_toolsgh CLI available and authenticated (verified with gh auth status).
—version_drift_detectionSingle application repository, not a monorepo. Not applicable, skipped.
Testing3/7 (43%)
—flaky_test_detectionNo flaky test detection configured. No retry mechanisms or tracking. Skipped (requires gh CLI).
✗integration_tests_existNo integration tests found. No e2e test frameworks like cypress or playwright.
✗test_coverage_thresholdsNo coverage thresholds enforced. No jest.config, pytest --cov-fail-under, or CI coverage gates.
✗test_isolationNo test isolation enforcement. No t.Parallel() usage or parallel test execution configured.
✓test_naming_conventionsGo's *_test.go naming convention enforced by tooling. Built-in test framework pattern.
✗test_performance_trackingNo test performance tracking. No test timing output or analytics platform integration.
✓unit_tests_existMany *_test.go files exist in root and middleware directories.
✓unit_tests_runnableTests runnable with 'go test' command. Verified tests can list successfully.
Documentation2/6 (33%)
✗agents_mdNo AGENTS.md file exists in repository root.
—agents_md_validationNo AGENTS.md exists, so validation not applicable. Prerequisite not met, skipped.
—api_schema_docsLibrary doesn't expose HTTP API. No OpenAPI/Swagger or GraphQL schema applicable, skipped.
✗automated_doc_generationNo automated doc generation. No godoc in CI, API doc generators, or doc automation workflows.
✓documentation_freshnessCONTRIBUTING.md modified within last 180 days (key documentation recently updated).
✓readmeComprehensive README.md exists with installation, usage, examples, and API documentation.
✗service_flow_documentedNo architecture diagrams or service flow documentation. No .mermaid, .puml, or diagram files.
✗skillsNo skills configured. No .factory/skills, .skills, or .claude/skills directories found.
Dev Environment1/2 (50%)
—database_schemaNo database usage. HTTP router library without database. Not applicable, skipped.
✗devcontainerNo devcontainer configured. No .devcontainer directory or devcontainer.json.
—devcontainer_runnableNo devcontainer configured, so runnability cannot be tested. Skipped.
✓env_templateNo environment variables required for library. No .env.example needed as no env vars block usage.
—local_services_setupLibrary has no external service dependencies. No database, Redis, etc. Not applicable, skipped.
Debugging & Observability3/7 (43%)
✗alerting_configuredNo alerting configured. No PagerDuty, OpsGenie, or custom alerting rules.
—circuit_breakersNo external service dependencies requiring circuit breakers. Not applicable, skipped.
—code_quality_metricsCode scanning API requires admin scope (403). Cannot verify without access. Skipped.
—deployment_observabilityLibrary repository, not a deployed service. Deployment observability not applicable, skipped.
✓distributed_tracingRequestID middleware propagates request IDs (X-Request-Id header) for distributed tracing.
✗error_tracking_contextualizedNo error tracking configured. No Sentry, Bugsnag, or Rollbar integration.
—health_checksLibrary, not a deployed service. Health check endpoints not applicable, skipped.
✗metrics_collectionNo metrics instrumentation. No Datadog, Prometheus, New Relic, or CloudWatch integration.
✓profiling_instrumentationProfiler middleware provides pprof instrumentation for performance profiling.
✗runbooks_documentedNo runbook documentation. No references to runbooks, playbooks, or incident procedures.
✓structured_loggingBuilt-in Logger middleware provides structured logging capabilities.
Security0/6 (0%)
—automated_security_reviewCode scanning API requires admin:repo_hook scope (403). Cannot verify, skipped.
—branch_protectionRequires GitHub admin API access to verify branch protection rules (skipped).
✗codeownersNo CODEOWNERS file in root or .github directory.
—dast_scanningLibrary, not a deployed web service. DAST scanning not applicable, skipped.
✗dependency_update_automationNo dependency update automation. No Dependabot or Renovate configuration found.
✗gitignore_comprehensiveBasic .gitignore with only IDE configs. Missing .env, .DS_Store, common build artifacts.
✗log_scrubbingNo log scrubbing mechanisms configured. No redaction or sanitization in logging code.
—pii_handlingLibrary doesn't process personal/user data. PII handling not applicable, skipped.
—privacy_complianceLibrary without end-user data collection. Privacy compliance not applicable, skipped.
—secret_scanningRequires GitHub admin API access to verify secret scanning configuration (skipped).
—secrets_managementLibrary doesn't handle secrets. Secrets management not applicable, skipped.
Task Discovery0/3 (0%)
—backlog_healthIssues have no labels. Cannot evaluate backlog health without labeling. Skipped.
✗issue_labeling_systemNo consistent labeling system. Open issues have no labels.
✗issue_templatesNo issue templates. No .github/ISSUE_TEMPLATE directory.
✗pr_templatesNo PR templates. No .github/pull_request_template.md or merge request templates.
Product & Analytics0/2 (0%)
✗error_to_insight_pipelineNo error-to-insight pipeline. No Sentry-GitHub integration or error tracking automation.
✗product_analytics_instrumentationNo product analytics. No Mixpanel, Amplitude, PostHog, Heap, or GA4 instrumentation.