← All package workshops
Developer tools / INTERACTIVE WORKSHOP

Inspect declarations, source and directed differences

MrLaravel v1.1.1

Choose fixed scanner snapshots, filter every collection, inspect source evidence and download actual package reports and comparisons.

01 / CONFIGURE

Choose a scenario. Change the inputs or build a sequence of commands.

02 / RUN

Execute the installed package against a new fictional example.

03 / INSPECT

Follow the result, actual calls, generated output and integration code.

THE WORKBENCH

Make it your example.

Your server-side changes are temporary. External-service examples use local response fixtures. Start with sample data.

Execution result

Waiting for your first run
No execution yetEdit inputs ↑

Start with a preset, or change the input and run it.

The behavior is the example.

Your result will show the values, decisions and generated output from the actual package.

EXPLORE THE PACKAGE

What you can exercise here.

INTERACTIVE

Scanner and comparison engine

Four actual scanner outputs and all directed/same-snapshot comparisons are built with Scanner::run; local traits and middleware evidence included.

INTERACTIVE

Report rendering and evidence

Real ReportRenderer with an explicitly supplied approved fictional source bundle, embedded file browser and exact-line dialogs, collection filters, bounded paging and declaration/edge focus.

HOST INTEGRATION

Analysis boundaries

The downloadable HTML embeds the approved fictional source, disclosed in the report and response. Static declarations are not execution proof. Production scanning requires trusted source and Node 22+; submitted PHP and arbitrary paths are never accepted.

UNDERSTAND THE BEHAVIOR

Static declarations and connected source can be inspected precisely.

Explore actual scanner snapshots of fictional procurement and delivery apps, compare either direction between versions, and inspect the packaged report alongside its exact declaration data.

01

The scanner actually ran on committed source

Snapshots were generated with the real Scanner against fixed fictional source trees, including local traits and bootstrap middleware. Runtime calls render those results; the scanner is not rerun on visitor-submitted PHP or shell commands.

02

Collections expose different kinds of finding

Choose declaration collections, filter literal text, page results and focus an exact declaration ID. Connected edges show scanner-resolved relationships. A static finding describes discovered source structure; dynamic application behavior still needs runtime inspection and tests.

03

Comparison direction is explicit

before_snapshot and after_snapshot independently select baseline or changed. Forward, reverse and same-snapshot comparisons come from actual package comparison output prepared for these fixtures. Same-to-same should be empty; reversing the direction reverses additions and removals.

04

Source browsing stays within fixed fictional files

The source selector admits only files already present in the selected atlas and committed fixture map. Those reviewed fictional text files are explicitly supplied to ReportRenderer and embedded in its HTML, with a privacy disclosure: anyone receiving the download can read them. The actual package file browser and declaration dialogs show exact source lines. No arbitrary path or uploaded source is accepted; the preview is sandboxed without network or same-origin access.

GO FURTHER

Try the boundary cases.

  1. Follow a declaration into its connections

    Choose procurement baseline, select models or relationships and filter Proposal. Copy a returned exact declaration ID into the focus control. Expected: the focus and connected edges refer to that declaration. Switch to middleware or traits to inspect the bootstrap/local-trait findings.

  2. Compare forward, reverse and identical snapshots

    Choose the comparison scenario, set before=baseline and after=changed, run, then reverse both. Expected: the diff describes opposite changes. Set both to baseline: the comparison reports no changes. Switching the displayed snapshot does not silently rewrite the explicitly selected comparison endpoints.

  3. Read the trusted source behind a finding

    Choose an available source_file or focus a declaration, then open that file or source reference inside the packaged report. Expected: its embedded file browser and dialog display the committed fictional text at the declaration line. source_bundle reports file/byte counts and the sharing disclosure. Try ../.env in Full example input: the host rejects it. Downloaded HTML deliberately contains the approved source; it is not a metadata-only report.

  4. Inspect and export without changing source

    Change collection, filter, offset and limit, then compare runs. Expected: only the visible declaration slice changes; the selected atlas remains intact. Download full snapshot JSON, comparison JSON and the actual self-contained report HTML to compare their different purposes.

COMPOSE THE RESPONSIBILITIES

Useful alone.
Better when the boundaries fit.

MrLaravel maps trusted source and produces reviewable reports. Repo supplies provider metadata; Preflight checks deployment configuration. Before sharing a source-bearing report from a real application, review the content and its disclosure policy.

Preflight Repo Read every API and recipe