ForgeScope
Evidence before edits.
Java 21 · C# / .NET 10 · Local Java and C# analysis

Understand the change. Follow the evidence.

Explore potential impact, investigate diagnostics and review the evidence before editing code.

sample · ForgeScope 0.3.0

Start demonstration →Open local workbenchHow it worksGuided demonstrationTools catalog
9Source modules
10Changed / affected files
2Test candidates
21Review findings

What could this change affect?

.github/workflows/ci.yml
csharp/Pricing.cs
java/src/shop/Pricing.java
csharp/Legacy.cs
csharp/Legacy.cs:5 → csharp/Pricing.cs
csharp/Orders.cs
csharp/Orders.cs:4 → csharp/Pricing.cs
java/src/shop/Legacy.java
java/src/shop/Legacy.java:4 → java/src/shop/Pricing.java
java/src/shop/Orders.java
java/src/shop/Orders.java:3 → java/src/shop/Pricing.java
csharp/tests/OrdersTests.cs
csharp/Legacy.cs:5 → csharp/Pricing.cs
csharp/tests/OrdersTests.cs:1 → csharp/Legacy.cs
java/src/shop/Api.java
java/src/shop/Orders.java:3 → java/src/shop/Pricing.java
java/src/shop/Api.java:3 → java/src/shop/Orders.java
java/tests/shop/OrdersTest.java
java/src/shop/Orders.java:3 → java/src/shop/Pricing.java
java/tests/shop/OrdersTest.java:4 → java/src/shop/Orders.java

Source reachability does not prove breakage or test coverage.

Tests to investigate

csharp/tests/OrdersTests.cs

java/tests/shop/OrdersTest.java

Analysis engines

revscope · ok

patchscope · ok

reporelief · ok

cifuse · ok

devrescue · ok

impact-java · ok

impact-python · skipped

impact-csharp · ok

Local reference review

Pricing.totalV1
java/src/shop/Legacy.java:4 → java/src/shop/Pricing.java

Invocation did not resolve against a supplied local source type; missing dependencies can affect binding.

Pricing.TotalV1
csharp/Legacy.cs:5 → csharp/Pricing.cs

Call did not resolve against a supplied local C# type. Review overloads, signatures and missing references.

Source-resolved call candidates

shop.Orders.checkout
java/src/shop/Api.java:3 → java/src/shop/Orders.java
shop.Api.submit · java
shop.Pricing.total
java/src/shop/Orders.java:3 → java/src/shop/Pricing.java
shop.Orders.checkout · java
shop.Orders.checkout
java/tests/shop/OrdersTest.java:4 → java/src/shop/Orders.java
shop.OrdersTest.main · java
Shop.Pricing.Total(int, int)
csharp/Orders.cs:4 → csharp/Pricing.cs
Shop.Orders.Checkout(int, int) · csharp
Shop.Orders.Checkout(int, int)
csharp/tests/OrdersTests.cs:4 → csharp/Orders.cs
Shop.Tests.OrdersTests.VerifyTotal() · csharp

Evidence and next steps

patchscopehighSame file in impact set

Review this workflow privilege boundary

.github/workflows/ci.yml:1
Evidence & action

Broad permissions or pull_request_target added

Check token scope and whether untrusted code can run.

patchscopemediumSame file in impact set

Dynamic code or process execution was added

java/src/shop/Pricing.java:3
Evidence & action

Execution boundary changed

Trace the input, argument boundaries and trust assumptions.

patchscopemediumSame file in impact set

Dynamic code or process execution was added

csharp/Pricing.cs:4
Evidence & action

Execution boundary changed

Trace the input, argument boundaries and trust assumptions.

patchscopemediumSame file in impact set

GitHub Actions behavior changed

.github/workflows/ci.yml:
Evidence & action

Workflow file changed

Review triggers, permissions and action pinning.

patchscopemediumSame file in impact set

Confirm behavior is covered

java/src/shop/Pricing.java:
Evidence & action

Source changed without changed test files in this patch

Check existing tests or add a regression case. This does not measure coverage.

patchscopemediumSame file in impact set

Confirm behavior is covered

csharp/Pricing.cs:
Evidence & action

Source changed without changed test files in this patch

Check existing tests or add a regression case. This does not measure coverage.

reporeliefmediumSame file in impact set

Review a module without a matching test name

csharp/Legacy.cs:
Evidence & action

No conventional test filename match

Find existing coverage or add a behavior test; this is not measured coverage.

reporeliefmediumSame file in impact set

Review a module without a matching test name

csharp/Pricing.cs:
Evidence & action

No conventional test filename match

Find existing coverage or add a behavior test; this is not measured coverage.

reporeliefmediumSame file in impact set

Review a module without a matching test name

java/src/shop/Api.java:
Evidence & action

No conventional test filename match

Find existing coverage or add a behavior test; this is not measured coverage.

reporeliefmediumSame file in impact set

Review a module without a matching test name

java/src/shop/Legacy.java:
Evidence & action

No conventional test filename match

Find existing coverage or add a behavior test; this is not measured coverage.

reporeliefmediumSame file in impact set

Review a module without a matching test name

java/src/shop/Pricing.java:
Evidence & action

No conventional test filename match

Find existing coverage or add a behavior test; this is not measured coverage.

cifusemediumSame file in impact set

Java compilation failed

java/src/shop/Legacy.java:4
Evidence & action

Original source evidence

java/src/shop/Legacy.java:4: error: cannot find symbol

Use the file and line diagnostics. Check package paths, declarations and the JDK/toolchain configured in Maven or Gradle.

cifusemediumSame file in impact set

C# or MSBuild diagnostic

csharp/Legacy.cs:5
Evidence & action

Original source evidence

csharp/Legacy.cs(5,43): error CS0117: 'Pricing' does not contain a definition for 'TotalV1'

Inspect the compiler diagnostic, target framework and references. Reproduce using the same .NET SDK as CI.

devrescuemediumSame file in impact set

Java compilation failed

java/src/shop/Legacy.java:4
Evidence & action

Original source evidence

java/src/shop/Legacy.java:4: error: cannot find symbol

Use the file and line diagnostics. Check package paths, declarations and the JDK/toolchain configured in Maven or Gradle.

devrescuemediumSame file in impact set

C# or MSBuild diagnostic

csharp/Legacy.cs:5
Evidence & action

Original source evidence

csharp/Legacy.cs(5,43): error CS0117: 'Pricing' does not contain a definition for 'TotalV1'

Inspect the compiler diagnostic, target framework and references. Reproduce using the same .NET SDK as CI.

impactmediumSame file in impact set

Review an unresolved local reference

java/src/shop/Legacy.java:4
Evidence & action

Original source evidence

Pricing.totalV1

Invocation did not resolve against a supplied local source type; missing dependencies can affect binding.

Inspect the declaration, signature, imports and missing dependency diagnostics. This is not a proof of root cause.

impactmediumSame file in impact set

Review an unresolved local reference

csharp/Legacy.cs:5
Evidence & action

Original source evidence

Pricing.TotalV1

Call did not resolve against a supplied local C# type. Review overloads, signatures and missing references.

Inspect the declaration, signature, imports and missing dependency diagnostics. This is not a proof of root cause.

reporeliefhigh

Make checks repeatable

:
Evidence & action

No GitHub workflow found

Add a workflow for the real test/build commands.

reporeliefmedium

Document usage

README.md:
Evidence & action

Section keywords not found

Add commands verified by a maintainer; keyword matching is heuristic.

reporeliefmedium

Clarify reuse permissions

:
Evidence & action

No root license file found

Choose and document an appropriate license.

reporeliefmedium

Repair a missing local Markdown target

README.md:5
Evidence & action

Original source evidence

docs/setup.md -> docs/setup.md

Restore the target or correct the relative link.

RevScope · analysis guidance

Wireshark · Capture and inspect network protocols in traffic you are authorized to analyze.

Tools are recommendations. No binaries are executed.

Coverage & limitations

Correlations are shared source evidence, not proof of root cause.

Java/C# source binding runs with an isolated classpath; project builds and external dependencies are not evaluated.

Python compatibility is import-only and lexical; the previous Python AST implementation is retained in Git history, not in this runtime.

Test candidates are source-reachable, not measured coverage.

Redaction is best effort. Inspect reports before sharing.

RevScope uses metadata and bounded header triage to recommend external tools; no binaries or captures are analyzed or executed.

Compiler diagnostics and skipped files

Original compiler diagnostics

[{"path":"java/src/shop/Legacy.java","line":4,"reason":"Java compiler diagnostic in isolated analysis","code":"compiler.err.cant.resolve.location.args","detail":"cannot find symbol\n  symbol:   method totalV1(int,int)\n  location: class shop.Pricing"},{"path":"csharp/Legacy.cs","line":5,"reason":"C# compiler diagnostic in isolated analysis","code":"CS0117","detail":"'Pricing' does not contain a definition for 'TotalV1'"}]

Skipped files

[{"path":"traces/empty.pcap","reason":"binary"}]

See what ForgeScope actually finds

Every sample below is read from this report, not a fabricated success score. Pages contains the public fixture; scans of your own project require the local CLI.

1 / 6 · Live report evidence

PatchScope · Review the change

Reads the supplied unified diff. Flags review prompts such as workflow privilege changes and missing tests; no patch is applied.

Review this workflow privilege boundary

.github/workflows/ci.yml:1

Check token scope and whether untrusted code can run.

Source evidence
Broad permissions or pull_request_target added
Dynamic code or process execution was added

java/src/shop/Pricing.java:3

Trace the input, argument boundaries and trust assumptions.

Source evidence
Execution boundary changed
Dynamic code or process execution was added

csharp/Pricing.cs:4

Trace the input, argument boundaries and trust assumptions.

Source evidence
Execution boundary changed

6 finding(s) in this report

2 / 6 · Live report evidence

CIFuse · Diagnose CI and source imports

Groups error patterns from supplied CI logs, records log positions and checks relative JS/TS imports. A diagnostic is not a proven root cause.

Java compilation failed

java/src/shop/Legacy.java:4

Use the file and line diagnostics. Check package paths, declarations and the JDK/toolchain configured in Maven or Gradle.

Source evidence
java/src/shop/Legacy.java:4: error: cannot find symbol
C# or MSBuild diagnostic

csharp/Legacy.cs:5

Inspect the compiler diagnostic, target framework and references. Reproduce using the same .NET SDK as CI.

Source evidence
csharp/Legacy.cs(5,43): error CS0117: 'Pricing' does not contain a definition for 'TotalV1'

Occurrences: 2

2 finding(s) in this report

3 / 6 · Live report evidence

RepoRelief · Audit maintenance

Inspects the local source snapshot for missing docs, broken relative Markdown links, missing workflows and conventional test-name gaps.

Review a module without a matching test name

csharp/Legacy.cs

Find existing coverage or add a behavior test; this is not measured coverage.

Source evidence
No conventional test filename match
Review a module without a matching test name

csharp/Pricing.cs

Find existing coverage or add a behavior test; this is not measured coverage.

Source evidence
No conventional test filename match
Review a module without a matching test name

java/src/shop/Api.java

Find existing coverage or add a behavior test; this is not measured coverage.

Source evidence
No conventional test filename match

9 finding(s) in this report

4 / 6 · Live report evidence

Impact · Trace Java and C# dependencies

Uses the JDK compiler and Roslyn to identify source-level dependency paths and test candidates. Paths show possible reachability, not test coverage.

Affected source paths: 10 · Candidate tests: 2

.github/workflows/ci.yml

csharp/Pricing.cs

java/src/shop/Pricing.java

5 / 6 · Live report evidence

RevScope · Identify external investigation tools

Checks artifact extensions and bounded file headers, then selects matching entries from the pinned RevScope catalog. It never runs binaries or decodes traffic.

1 artifact signal(s)

Recognized capture header

traces/empty.pcap

pcap header

Wireshark · Capture and inspect network protocols in traffic you are authorized to analyze.

RevScope · Tools catalog

Browse the 22 curated tools by category. Each entry includes purpose, learning level and official documentation. No binary analysis or remote scripts run here.

Disassembly & decompilation (4)

Ghidra

Disassemble, decompile, and analyze compiled code with a collaborative desktop workbench.

Best for: Static analysis of native binaries

Platform: Windows · macOS · Linux · Level: Intermediate · Free

Official documentation

IDA Free

Interactive disassembler with broad processor coverage and a familiar analysis workflow.

Best for: Inspecting supported binary formats

Platform: Windows · macOS · Linux · Level: Intermediate · Free tier

Official documentation

Cutter

Accessible reverse-engineering GUI built around the Rizin framework.

Best for: A graphical entry point to Rizin

Platform: Windows · macOS · Linux · Level: Beginner · Free

Official documentation

radare2

Portable command-line framework for binary analysis, debugging, and data inspection.

Best for: Scriptable binary workflows

Platform: Windows · macOS · Linux · Level: Advanced · Free

Official documentation

Debugging (1)

x64dbg

Open-source debugger for Windows applications and executables.

Best for: Runtime debugging on Windows

Platform: Windows · Level: Intermediate · Free

Official documentation

Triage & identification (3)

Detect It Easy

Identify executable formats, compilers, packers, and related file properties.

Best for: First-pass executable triage

Platform: Windows · macOS · Linux · Level: Beginner · Free

Official documentation

capa

Identify capabilities in executable files, shellcode, and sandbox reports.

Best for: A fast behavior-oriented first look

Platform: Windows · macOS · Linux · Level: Intermediate · Free

Official documentation

FLOSS

Extract strings that are statically or stack-decoded from malware samples.

Best for: Finding obfuscated strings during triage

Platform: Windows · macOS · Linux · Level: Beginner · Free

Official documentation

Detection & rules (1)

YARA

Describe and match patterns in files using readable, shareable rules.

Best for: Creating repeatable file detection rules

Platform: Windows · macOS · Linux · Level: Intermediate · Free

Official documentation

Dynamic instrumentation (1)

Frida

Instrument applications at runtime with a programmable toolkit for developers and researchers.

Best for: Observing runtime behavior in a test environment

Platform: Windows · macOS · Linux · Android · iOS · Level: Advanced · Free

Official documentation

Android & mobile (3)

JADX

Read Java-like source and resources recovered from Android DEX and APK files.

Best for: Static inspection of Android packages

Platform: Windows · macOS · Linux · Level: Beginner · Free

Official documentation

Apktool

Decode Android resources and rebuild packages for analysis and development workflows.

Best for: Inspecting resources and manifests

Platform: Windows · macOS · Linux · Level: Intermediate · Free

Official documentation

MobSF

Automate mobile application security checks and organize static or dynamic analysis findings.

Best for: A repeatable mobile app assessment workflow

Platform: Windows · macOS · Linux · Level: Intermediate · Free

Official documentation

.NET & managed code (2)

ILSpy

Open-source .NET assembly browser and decompiler with a desktop interface.

Best for: Exploring managed .NET assemblies

Platform: Windows · macOS · Linux · Level: Beginner · Free

Official documentation

dnSpyEx

Community-maintained .NET debugger and assembly editor derived from dnSpy.

Best for: Debugging managed .NET applications

Platform: Windows · Level: Intermediate · Free

Official documentation

Network & protocols (4)

Wireshark

Capture and inspect network protocols in traffic you are authorized to analyze.

Best for: Understanding protocol behavior in a lab

Platform: Windows · macOS · Linux · Level: Beginner · Free

Official documentation

mitmproxy

Inspect, modify, and replay HTTP(S) traffic in your own test setup.

Best for: Debugging API and web traffic

Platform: Windows · macOS · Linux · Level: Intermediate · Free

Official documentation

Burp Suite Community

A manual toolkit for testing web applications that you own or have permission to assess.

Best for: Hands-on web security testing

Platform: Windows · macOS · Linux · Level: Intermediate · Free tier

Official documentation

PCAPdroid

Capture Android app traffic without root, inspect HTTP requests, and export PCAP files. HTTPS inspection requires extra TLS setup and app compatibility.

Best for: Per-app Android traffic analysis and PCAP export

Platform: Android · Level: Beginner · Free tier · paid extras

Official documentation

Firmware & embedded (2)

Binwalk

Search firmware images for embedded filesystems, signatures, and other structures.

Best for: Initial inspection of firmware images

Platform: Windows · macOS · Linux · Level: Intermediate · Free

Official documentation

OpenOCD

Debug and program microcontrollers through supported on-chip debug adapters.

Best for: Hardware you own or are authorized to service

Platform: Windows · macOS · Linux · Level: Advanced · Free

Official documentation

Emulation & lab (1)

QEMU

Emulate machines and run isolated test environments across many architectures.

Best for: Safe, repeatable analysis labs

Platform: Windows · macOS · Linux · Level: Advanced · Free

Official documentation

External projects remain independent and are never executed by ForgeScope.

How ForgeScope works

Follow seven practical steps from setup to a report. Expand a step to copy the exact commands.

01Explore the sample

Click Start demonstration to walk through overview, impact, tests, references, findings and limitations.

Open guided tour
02Install requirements

Install JDK 21, .NET 10 SDK and Git. These are needed on your computer, not on GitHub Pages.

03Clone and build

Run this block in a terminal. The Java CLI, Roslyn worker and ASP.NET workbench will be built.

git clone https://github.com/brunnojob/forgescope.git
cd forgescope
dotnet build dotnet/ForgeScope.Worker -c Release
dotnet build dotnet/ForgeScope.Workbench -c Release
java tools/Build.java
04Run a sample scan

Analyze the bundled Java/C# fixture, supplied patch and CI log. Results are written to .forgescope.

java -jar build/forgescope.jar examples/sample --changed java/src/shop/Pricing.java --changed csharp/Pricing.cs --diff examples/change.diff --log examples/build.log --csharp-worker dotnet/ForgeScope.Worker/bin/Release/net10.0/ForgeScope.Worker.dll --output .forgescope
05Read the report

Open the generated HTML in a browser. Check affected files, candidate tests, engine status, compiler evidence and limitations.

.forgescope/index.html

06Open the local workbench

Start ASP.NET Core and open http://127.0.0.1:8765. Filter findings and rescan only the repository configured at startup.

dotnet dotnet/ForgeScope.Workbench/bin/Release/net10.0/ForgeScope.Workbench.dll --report .forgescope/report.json --repo examples/sample --jar build/forgescope.jar --worker dotnet/ForgeScope.Worker/bin/Release/net10.0/ForgeScope.Worker.dll
07Review and export

Use JSON, SARIF or Markdown after reviewing the evidence. Potential impact is not proof of a defect; reports may contain sensitive paths or snippets.

Pages displays example evidence. Actual scans use Java and .NET locally; the offline report works without JavaScript.