CodeGuard
CodeGuard / workflow

Check a public URL. Manage client pages in projects.

Check one public page without an account. Agencies can manage selected project pages and review saved reports and in-app findings. See what static checks cover and what they leave out.

Check a public URL for freeView monthly plans

No-account check

Check one public URL and review the evidence

Enter a public URL on the homepage. CodeGuard runs a bounded static check and reports the evidence for each check it performed. A clear result applies only to that evidence.

  • Start from the homepage without creating an account.
  • CodeGuard makes read-only requests to the public page and the allowed same-host references.
  • See performed checks, findings and evidence. Save the same result to an account if you choose to sign up.
  • The check does not exercise JavaScript, browser-rendered mobile layouts, forms, sign-ins or purchases.

For agencies

Manage selected client pages

The native job is listed for 08:00 UTC daily. Enabled projects, eligibility, and recorded job outcomes are shown separately.

  • Create an account-scoped project and select the public pages to monitor.
  • The checker uses read-only GET requests against static HTML, without cookies or credentials.
  • Review project reports and in-app notifications for confirmed issues from an authorized account.
  • Monitoring does not exercise JavaScript, browser-rendered mobile layouts, forms, sign-ins or purchases. A clear result covers only the checks performed.
  • Monthly subscriptions are open. Compare plan limits and choose a tier on the pricing page.
View monthly plans

Separate Code Health file analysis

Pay once → upload files → review the report

  1. 01
    Pay

    Open the project page and pay $79 USD through hosted Stripe Checkout. Uploads unlock only after verification.

  2. 02
    Upload inputs

    Send package.json, a lockfile and a build log. CodeGuard fetches npm vulnerability data without running project code.

  3. 03
    Get the report

    Once the inputs can be read, CodeGuard reviews the findings and shows a summary, evidence, explanation and next action.

the inputs

Files for the one-time analysis

The $79 USD file analysis uses files from one project after the purchase is verified.

  • Required: package.json with the project's dependencies and devDependencies.
  • Required: package-lock.json, yarn.lock or pnpm-lock.yaml.
  • Required: a build log with a .log or .txt suffix.
  • The lockfile is checked server-side against npm vulnerability data.

the result

The report shows what to do next.

Findings are separated by severity and tied back to the input where they appear.

  • A summary of dependency and build findings.
  • An evidence excerpt with a file reference.
  • An explanation of what the finding means.
  • A concrete remediation suggestion.

when input is missing

Invalid or incomplete files stop the next step.

Filenames, formats and content are checked before the scan. If a required input is missing or unreadable, you fix it and try again; the report does not pretend to be complete.