THE FIRST PRODUCT BY OFFENSE

Find the gap.
Build the fix.

Your runtime has the signals. Your repository has the context. Purple brings them together so your agents can get to work.

EARLY ACCESS · BUILT FOR CLOUDFLARE WORKERS

FROM SIGNAL TO NEXT STEPEXAMPLE
SOURCE WORKERyour-api
LINKED
FOLLOW THE DEPENDENCY
your repository└─ parent package   └─ affected dependency
AGENT UPGRADE BRIEF
  1. Confirm the graph & advisory
  2. Resolve parent constraints
  3. Patch, reproduce & run tests
  4. Recheck resolved versions
WORKS WITH YOUR STACK
CloudflareGitHubOpenRouter

THE WORKFLOW

Context before action.

01 / CONNECT

See what’s happening.

Connect Cloudflare, link each Worker to its GitHub repository, and bring your OpenRouter key. Collect redacted events from the services you choose.

02 / UNDERSTAND

Follow the evidence.

Group related security signals into investigations. Map npm dependencies, check known advisories, and find the parent packages standing between you and a fix.

03 / ACT

Give agents a real brief.

Get an upgrade plan with dependency paths, release changes, and testing instructions. Copy the prompt into your agent, or review a runtime investigation’s patch and test results.

MORE THAN A VERSION BUMP

An upgrade path.
With the context attached.

A fixed version is only the start. Purple traces the dependency chain, surfaces parent constraints, and inspects the changes between releases.

Your handoff includes the evidence, proposed changes, and checks an agent needs to perform. Compatibility is established by testing the actual repository.

Explore the dependency map

PURPLE BY OFFENSE

Put your signals to work.

Open Purple