Starting material
Authorized app or staging URL + scope
Factoriessecurity
Working14-day run0
read-only, inside your scope
0
1 high severity
0
new or changed, 38 clean
$0.00
of $25.00 cost budget
0probes sent0 confirmed
| Task | Status |
|---|---|
| Find the latest deployment | Idle |
| Probe new API routes for exposed data | Idle |
| Review 3 draft patch pull requests | Idle |
| Redact tokens from the evidence | Idle |
| Write a regression test for the auth fix | Idle |
Run plan
Each factory run probes new and changed routes in your latest deployment with safe, read-only requests, then patches each confirmed finding.
Ready for your review
Review 3 draft patch pull requests
Each one has the redacted request and response, severity, fix, and test result.
Sample run: Security
A sample run, start to finish. It maps what the deploy exposed, confirms a finding with the exact request and response, redacts the evidence, and reports which earlier findings are fixed.
FactoriesSecurity run
IdleIllustrative runGET /api/invoices/inv_1042
Require a session on GET /api/invoices/[id]
Start with your source
The trial begins with the material below. No mandatory OAuth connection is needed for accessible public sources or material you supply.
Authorized app or staging URL + scope
Set the targets, questions, acceptance criteria, and exclusions. The scope controls what the report investigates. Inspect only targets you own or have explicit permission to test. Stay within the authorized scope and use non-destructive checks. Enter the authorized target boundaries before running this template.
Manual is the default. Choose hourly, daily, or weekly recurrence when repeated observation is useful.
How the trial runs
Map what the deploy exposed, probe what changed, retest open findings, then confirm each one before it reaches the report.
List reachable routes, forms, and endpoints within your scope and note what changed since the last run.
Run passive and in-scope checks against what changed, recording each request and response.
Replay earlier findings to see which the deploy fixed and which remain open.
Keep only findings reproduced with an exact request and response, rate their impact, and redact secrets.
Return confirmed findings, their reproduction, and the fixed or open status of earlier ones.
What you review
Scoped security findings, reproduction evidence, impact explanations, and unresolved retest requirements.
Public sources can be read again. Uploaded files remain snapshots: provide a fresh upload to assess new private facts. Earlier saved evidence provides a comparison baseline, not a live connection to the original system.
Browser interaction, code execution, authenticated access, and unsupported file formats may be unavailable in a run. Missing access or tools appear as coverage gaps, never as a passed test. Proposed fixes and drafts remain in the report.
Returns a report and proposed next steps for your review. External messages, source changes, payments, and submissions are outside this trial. Inspect only targets you own or have explicit permission to test. Stay within the authorized scope and use non-destructive checks. Enter the authorized target boundaries before running this template.
Inputs, recurrence, evidence, and the boundary of the report.
Need help defining the source or scope? Contact us
Supply the source, review the scope, and get an initial report before choosing a recurring cadence.