Project intelligence
Identify languages, manifests, frameworks, scripts, dependency counts and important project configuration before you start changing code.
forge inspectFORGE helps you understand unfamiliar codebases, map architecture, inspect change risk, review proposed patches and verify outcomes — with evidence at every step and you in control.
Clone the open-source project and build it locally. Node.js 22+ required.
git clone https://github.com/ansh44233/FORGE-ECC.git && cd FORGE-ECC && npm install && npm run buildExplore the capabilities currently documented in the FORGE repository. Each tool is designed to surface useful evidence, explain its limits and leave consequential decisions with the developer.
Identify languages, manifests, frameworks, scripts, dependency counts and important project configuration before you start changing code.
forge inspectExplore source modules, import relationships, external packages, likely entry points and circular dependency groups.
forge map · forge deepParse JavaScript and TypeScript syntax to find declarations, exports, circular imports and transitive file-impact candidates.
TypeScript ASTConnect working-tree changes with downstream modules, structural hotspots, repository signals and candidate tests.
forge git · change-riskSave review snapshots, inspect individual findings and compare reviews to understand how static findings change over time.
forge review-historyCheck proposed unified diffs for target paths, hunk structure, line counts and source context — without applying the patch.
forge patch-checkChoose a named project script, run it deliberately and record output, exit status, duration and timestamps.
forge verifyCompare saved verification outcomes to identify regressions, recoveries, persistent failures and stable checks.
forge regressionCombine available quality, verification and dependency evidence with explicit coverage so missing evidence is not mistaken for a pass.
forge healthInspect npm manifests and lockfiles, and import local audit/outdated reports to review vulnerability, version and license signals.
forge depsPrioritize dependency findings and suggest review steps. FORGE does not silently install, upgrade or remove packages.
forge remediateCapture local snapshots and compare architecture size, hotspot counts, quality findings and selected project signals.
forge snapshot · timelineBring project health, architecture, saved runs, reviews, task activity and workspace exploration into a local control center.
forge dashboardBrowse supported project files and folders, inspect sizes and preview source or documentation in the local dashboard.
Read-only explorerInspect saved orchestration runs, task activity and run details, with explicit approval controls for recorded workflow tasks.
Dashboard workflow viewUse a configured provider for review suggestions and single-file patch proposals. Selected source context may be sent to that provider.
Optional provider setupA visual preview of the core objects FORGE works with: connected modules, code signals, security checks and verification history. These panels are product illustrations, not live scan results.
FORGE is more than a logo and a terminal. These are the product areas developers can explore in the repository today.
Understand manifests, scripts, source layout and project signals.
Inspect module relationships, imports, symbols and impact candidates.
Review Git changes, risk signals, diffs and remediation plans.
Run named checks, save results and compare regressions over time.
The full dashboard runs on your machine and connects to the project directory you choose. It is not a mock screen and it does not upload your repository to this public website.
Replace ./your-project with the local project you want to inspect. Open the localhost URL printed in your terminal.
Provider-backed execution still requires your own provider credentials and explicit permission configuration.
A product system built around understanding repositories, guiding engineering work and verifying outcomes.
Repository inspection, AST and symbol analysis, dependency relationships, architecture mapping, Git-aware impact candidates and snapshots.
CURRENT TOOLINGChange-risk signals, review history, patch validation, remediation plans, named checks and regression comparisons.
CURRENT TOOLINGReusable specialist workflows, agent run visibility, shared project guidance and policy-aware orchestration.
ROADMAP · NOT SHIPPEDA proposed catalog connecting planning, implementation, review and verification. These modules are planned, not available in the current release.
Turn a feature request into scoped tasks, dependencies, acceptance criteria and a verification plan.
PLANNEDReview diffs for correctness, maintainability, security-sensitive patterns and missing tests with evidence-linked findings.
PLANNED EXPANSIONRecommend tests from changed modules and impact candidates, then track which checks actually ran.
PLANNED EXPANSIONAuditable local review for agent configuration, risky permissions and unsafe project defaults.
PLANNED · SCOPE TBDExplain outdated or vulnerable packages, compatibility concerns and human-reviewed upgrade options.
PLANNED EXPANSIONCapture recurring fixes and team conventions as reviewable guidance with provenance and confidence.
PLANNEDProposed milestones inspired by the breadth of the ECC product experience. Nothing here is called shipped until code, tests and docs exist.
Green CI, reliable local dashboard, command discovery, docs and first-run onboarding.
Versioned workflow packs, specialist roles, install profiles and explicit permissions.
Local configuration auditing, severity-ranked findings, policy checks and reproducible reports.
Opt-in learning from accepted fixes, pruning controls, provenance and portable team guidance.
Choose a stage to preview the kind of evidence and workflow FORGE brings together. This is an illustrative product tour, not a live repository scan.
Inspect the repository before making assumptions about how it works.
FORGE connects discovery, architecture, review and verification into a workflow you can inspect and repeat.
Discover the stack, scripts, dependencies, project structure and available evidence.
Explore imports, symbols, hotspots and likely downstream impact before editing.
Inspect risk signals, review findings and remediation suggestions. Decide what to accept.
Run selected checks, save results and compare with prior verification history.
.forge directory.FORGE is an independent TypeScript project with a CLI and a local dashboard. Use it against a trusted local workspace and review every suggested action.
From first inspection to post-change verification, FORGE keeps the evidence and the next decision in one place.
Profile a repository, explore source structure, imports, symbols and likely impact paths.
AVAILABLE IN CLIReview health snapshots, architecture, saved runs, task activity and a read-only workspace explorer.
AVAILABLE LOCALLYRun a selected project script, preserve its result and compare it with the previous recorded run.
AVAILABLE IN CLIFORGE supports provider-backed runs and exposes a local, read-only MCP tool server. Editor compatibility is through MCP configuration, not a claim of a native editor extension.
Provider credentials and model access are controlled by the provider account you configure.
Provider setup guide ↗.cursor/mcp.json or global MCP configuration.FORGE is an independent, MIT-licensed engineering workbench. Explore the implementation, inspect the roadmap, report issues and contribute improvements directly in the repository.
FORGE is published under the MIT license. There are no paid tiers or hosted-service claims on this page.
Use the open-source CLI and local dashboard on your own machine.
Requires Node.js 22+. Clone the repository, install dependencies and build the CLI.
No. The public website explains FORGE and contains illustrative previews. The full engineering dashboard runs locally against a project you select.
No. Patch validation is a dry run. Remediation output is a plan. Verification runs only when you select a named script.
Current architecture and deep AST analysis focus on JavaScript and TypeScript. Other project signals are based on recognized manifests, files and configuration.
No. It is an evidence-based prioritization heuristic. Missing audit reports are marked not assessed, and a score is not a certification.
AI review sends selected source excerpts to the provider you configure. Review your provider's data handling terms before enabling it.
The CLI and engineering dashboard are local tools. The public Vercel site is a separate static product page.
Explore the code, inspect the roadmap and help shape the next engineering workbench.