How it works

From your app to
a useful next step.

Connect an app you own. See what needs attention. Give your builder something concrete to work with.

01

Connect your app

Add its address, verify ownership and connect a dedicated test account if needed.

02

Run a check

Choose the scope and test permissions. Argive explores your app and records its results.

03

Review and improve

Inspect findings, share a builder message and check the affected behavior again.

Before the first check

You choose the access.

Verify ownership with the token in the setup checklist. For signed-in pages, connect a dedicated test account.

Some checks submit forms or create test records. Review the permissions and use disposable data.

Connect an app →

App setup

✓ App address added

✓ Ownership verified

✓ Test account connected

✓ Test permissions reviewed

Illustrative setup

After the check

A finding you can act on.

Harbor · /projects/newProblem

A blank project name is accepted

Submitting the form without a project name creates an unnamed project. The form should ask for a name before saving.

HARBOR

Projects

Untitled projectJust created
✓ Project created
Illustrative frame · 0:04

Send to your builder

On /projects/new, submitting an empty Project name creates a record. Require a non-blank name, show a clear validation message, and prevent creation until the name is valid. Validate this on the server as well as in the form. Re-test empty and whitespace-only names.

Illustrative exampleOpen the example finding →

A few useful terms

Flow

A sequence of actions, such as creating a project or submitting a form.

Finding

An issue or observation from a check. Open it to inspect the explanation and available evidence.

Evidence

Recorded screenshots, video, events or technical details that support a finding.

Check history

The results of a particular app run, including what completed and why it stopped.

Scheduling

Eligible plans can check daily or weekly, with verified access and enough credits.