All Reports
Express
TypeScript
expressjs/express
Pass Rate
28%
Node.js web framework with routing, middleware, and HTTP utilities
L1100%
L240%
L30%
L40%
L50%
Strong Testing
Express reaches Level 2 with 63% Testing pass rate. Currently building team readiness with 17/61 criteria passing (28%). Key areas for improvement include the opportunities listed below.
Strengths
01
Lint Config
ESLint configured via .eslintrc.yml with rules for code quality
02
Deployment Frequency
Multiple releases per month - v5.2.1 on Dec 1, frequent npm releases
03
Fast Ci Feedback
CI completes in ~22 seconds (well under 10 minute threshold)
Opportunities
01
Cyclomatic Complexity
Add complexity analysis to identify and refactor overly complex functions.
02
Feature Flag Infrastructure
Add feature flags to enable safer deployments and gradual rollouts.
03
Skills
Create .factory/skills to give agents reusable, tested capabilities for common tasks.
All Criteria
Style & Validation1/10 (10%)
—code_modularizationSkipped - small library (~2772 lines), module boundaries not meaningful
✗cyclomatic_complexityNo ESLint complexity rule or code complexity analysis tools configured
✗dead_code_detectionNo knip, ts-prune, unimported, or similar dead code detection tools
✗duplicate_code_detectionNo jscpd or duplicate code detection configured
✗formatterNo Prettier or Black configuration files found
✗large_file_detectionNo git hooks, CI checks, LFS config, or linter rules for file size detection
✓lint_configESLint configured via .eslintrc.yml with rules for code quality
—n_plus_one_detectionSkipped - no database or ORM usage in this framework library
✗naming_consistencyNo ESLint naming-convention rule or documented naming standards
✗pre_commit_hooksNo Husky or pre-commit config detected
—strict_typingSkipped - JavaScript project without type system
✗tech_debt_trackingNo TODO/FIXME scanner, SonarQube, or tech debt tracking tools detected
✗type_checkJavaScript project without TypeScript or mypy configuration
Build System4/12 (33%)
✗agentic_developmentNo agent co-authorship in git history, no agent workflow evidence
—automated_pr_reviewSkipped - insufficient evidence of automated review comment generation
✗build_cmd_docREADME documents npm install but no build command (library distributed as-is)
✗build_performance_trackingNo build caching, metrics export, or deliberate build performance monitoring
—dead_feature_flag_detectionSkipped - prerequisite feature_flag_infrastructure not configured
✓deployment_frequencyMultiple releases per month - v5.2.1 on Dec 1, frequent npm releases
✗deps_pinnedNo lockfile committed - package-lock.json intentionally gitignored
✓fast_ci_feedbackCI completes in ~22 seconds (well under 10 minute threshold)
✗feature_flag_infrastructureNo LaunchDarkly, Statsig, Unleash, or feature flag system configured
—heavy_dependency_detectionSkipped - backend library, not bundled for browsers
—monorepo_toolingSkipped - single-application repo without workspaces
—progressive_rolloutSkipped - library repo, not infrastructure deployment
✗release_automationNo automated CD pipeline, semantic-release, or GitOps detected
✗release_notes_automationNo semantic-release, standard-version, changesets, or automated changelog
—rollback_automationSkipped - library repo, not infrastructure deployment
✓single_command_setupREADME documents 'npm install' for setup
✗unused_dependencies_detectionNo depcheck, npm-check, or knip configured
✓vcs_cli_toolsgh CLI available and authenticated successfully
—version_drift_detectionSkipped - single-application repo
Testing5/8 (63%)
✗flaky_test_detectionNo test retry config, flaky test tracking, or quarantine mechanisms
✓integration_tests_existIntegration tests in test/acceptance/ directory
✓test_coverage_thresholdsCoveralls integration in CI enforces coverage tracking via test-ci script
✗test_isolationNo Mocha parallel execution or test sharding configured
✓test_naming_conventionsMocha tests follow test/*.js and test/acceptance/*.js naming patterns
✗test_performance_trackingNo test timing output, analytics platforms, or performance tracking configured
✓unit_tests_existExtensive test suite in test/ directory with ~16,221 lines
✓unit_tests_runnableTest script configured in package.json running Mocha test runner
Documentation2/7 (29%)
✗agents_mdNo AGENTS.md file at repository root
✗agents_md_validationNo validation - prerequisite agents_md not present
—api_schema_docsSkipped - framework library, not a service with API endpoints
✗automated_doc_generationNo automated documentation generation tools or workflows detected
✓documentation_freshnessReadme.md updated within last 180 days
✓readmeReadme.md exists with comprehensive setup and usage instructions
✗service_flow_documentedNo architecture diagrams or service dependency documentation found
✗skillsNo skills directory found in .factory/, .skills/, or .claude/skills/
Dev Environment0/2 (0%)
—database_schemaSkipped - no database usage
✗devcontainerNo .devcontainer/devcontainer.json configuration
—devcontainer_runnableSkipped - no devcontainer configured
✗env_templateNo .env.example or environment variable documentation (library may not need)
—local_services_setupSkipped - no external service dependencies for this framework library
Debugging & Observability2/8 (25%)
✗alerting_configuredNo PagerDuty, OpsGenie, or alerting rules defined
—circuit_breakersSkipped - library without external service dependencies
✓code_quality_metricsCoveralls tracks coverage, CodeQL provides quality analysis
✗deployment_observabilityNo dashboard links or deployment notification integrations
✗distributed_tracingNo trace ID or request ID propagation implementation
✗error_tracking_contextualizedNo Sentry, Bugsnag, or Rollbar error tracking configured
—health_checksSkipped - library, not deployed service
✗metrics_collectionNo metrics/telemetry instrumentation (Datadog, Prometheus, etc.)
—profiling_instrumentationSkipped - library, profiling not applicable
✗runbooks_documentedNo runbook or playbook references in documentation
✓structured_loggingdebug library in dependencies for structured logging capabilities
Security2/8 (25%)
✓automated_security_reviewCodeQL SAST configured in .github/workflows/codeql.yml
—branch_protectionRequires GitHub admin API access to verify branch protection rules (skipped).
✗codeownersNo CODEOWNERS file in root or .github/
—dast_scanningSkipped - library, not deployed web service
✓dependency_update_automationDependabot configured for npm and github-actions updates
✗gitignore_comprehensiveMissing .env, .DS_Store, .idea, .vscode - only has node_modules and logs
✗log_scrubbingNo log sanitization or scrubbing mechanisms configured
—pii_handlingSkipped - framework library without personal data processing
—privacy_complianceSkipped - library without end-user data collection
—secret_scanningRequires GitHub admin API access to verify secret scanning configuration (skipped).
✗secrets_managementNo secrets manager integration or encrypted secrets pattern
Task Discovery1/4 (25%)
✗backlog_healthOnly 63% issues have good title+labels (need >70%), old issues >365 days
✓issue_labeling_systemConsistent labels: bug, enhancement, discuss, ideas, 6.x, module:router, etc.
✗issue_templatesNo .github/ISSUE_TEMPLATE/ directory
✗pr_templatesNo .github/pull_request_template.md
Product & Analytics0/2 (0%)
✗error_to_insight_pipelineNo error-to-issue automation or Sentry-GitHub integration
✗product_analytics_instrumentationNo Mixpanel, Amplitude, PostHog, or analytics tools configured
