pentest-2026-06-12-2827f2be
mbarbine/jc-pentest-harness · api-multi-model
Plan Status
dry_run_plan_complete
Execution
not_executed
Storage
neon_persisted
Spend
$0.0000
Classes
0 / 44
Updated
Jun 12, 2026, 10:12 PM
Execution Boundary
- 01 / setupplan recorded
Dry-run setup was persisted; model execution did not run.
View detailsHide details
- run id
- pentest-2026-06-12-2827f2be
- target repo
- mbarbine/jc-pentest-harness
- execution mode
- api-multi-model
- planned classes
- 44
- budget usd
- 5
- created
- Jun 12, 2026, 10:12 PM
- 02 / scope validationplan recorded
Scope was validated for planning only; no target or model execution ran.
View detailsHide details
- target name
- PlatPhormNews authorized public surface
- base url
- https://platphormnews.com
- repos
- mbarbine/jc-pentest-harness
- allowed hosts
- platphormnews.com
- responsible use accepted
- no
- 03 / reconqueued
Passive recon did not run during this dry-run plan.
View detailsHide details
- fetched routes
- 0
- recon errors
- 0
- 04 / huntoperator checkpoint
Model Hunt has not executed. Start a protected real run or rerun with AI Gateway credentials.
View detailsHide details
- attempted classes
- not recorded
- completed classes
- not recorded
- model cost events
- 0
- spend usd
- 0.0000
- pipeline errors
- 0
- 05 / validatequeued
Validate waits for model Hunt findings.
View detailsHide details
- candidate findings
- 0
- persisted findings
- 0
- confirmed findings
- 0
- persistence complete
- no
- 06 / gapfillqueued
Refusals or uncovered cells require operator review.
- 07 / tracequeued
Reachability analysis links findings to trust boundaries.
- 08 / reportqueued
Reports require real findings or persisted execution artifacts.
View detailsHide details
- artifact source
- none yet
- 09 / scorecardqueued
Scorecard waits for findings, class evidence, or scorecard rows.
View detailsHide details
- scorecards
- 0
- findings scored
- 0
- confirmed findings
- 0
Operator Checkpoint
Dry-run planning is complete. Model execution has not started; rerun as a protected real run when scope, budget, responsible-use confirmation, and AI Gateway credentials are ready.
To continue from the browser, use the rerun action. A real-run rerun requires responsible-use acceptance, typed authorization, valid scope, budget, and model credentials; a dry-run rerun validates the plan only.
Execution Log
dry-run plan completeDry-run plan pentest-2026-06-12-2827f2be was persisted for mbarbine/jc-pentest-harness; model execution did not run.
Dry-run planning completed. No model execution, class evidence, findings, scorecard, or cost events are persisted for this run.