CodeGuard
Start the code health check
CodeGuard / workflow

From project input to a report you can act on.

The code health check is built around one concrete project: understand the next step, provide the input, then get a readable priority list.

Start the code health checkAsk about payment

three steps

Pay → upload → get the report

  1. 01
    Pay

    Open the project page and pay 199 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

What exactly should be submitted?

The check starts with three files from one concrete project.

  • 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.