One small finding.
A useful next action.

1. Compare two exact files

Prerequisites: a browser and a text editor. No package installation or program execution is needed. Each file is an independent three-line TypeScript input. Review one variant at a time; selecting both would produce different file-level scope.

import https from "node:https";
export const createExampleRequest = () =>
  https.get("https://example.invalid", { rejectUnauthorized: false });

import https from "node:https";
export const createExampleRequest = () =>
  https.get("https://example.invalid", { rejectUnauthorized: true });

The only configuration change is false → true. Both retain an unresolved-or-external node:https import; dependencies, a real endpoint and runtime behavior are unverified.

2. Know what the result means

This three-line example is separate from the nine-file published topology map. An upload digest identifies selected files; it is not a Git commit or repository permission. Explore the separate topology example →

3. Turn evidence into a reasoned plan

1. ReviewRead path, line and exact scope.
2. TriageInvestigate the condition; dismiss only with a reason.
3. ExplainSeparate the stored fact from an unproven impact.
4. SecureRead partial, disabled and unavailable checks.
5. EngineerPlan a change and record your own observed outcome.

Suggested manual plan: inspect why the option was disabled, retain certificate verification, then run appropriate hostname, trust-chain and regression checks in your own project. Record the actual outcome only after performing those checks; this tutorial does not perform them.

Download the reusable decision and validation checklist ↓

Optional: hand off a retained finding

Inside the full dashboard, open your saved report in any of the five workflows. Select findings, preview the exact handoff, then download Markdown, JSON or print-ready HTML. Use your browser’s Print / Save as PDF command for HTML. Notes, dismissal reasons, dismissed findings and history default to excluded. Opening, saving and exporting use no additional review allowance.

4. Review selected files when you are ready

Use CodHub or Cloudburg identity sign-in and your own workspace. Reopen an existing workspace with its original provider; accounts are not automatically linked. A separate repository connection is not required for file uploads. New workspace owners review the existing Terms before acceptance.

1. Download the original file above.
2. Open your workspace and select Upload review. If signed out, choose your original sign-in provider (CodHub or Cloudburg), then return to Upload review.
3. Select that file, inspect its path and size, and submit only if you choose to use one available review.
4. Open the completed report and compare the declared rule and line. Read coverage before recording your next decision.

Limits: 40 selected JS/TS files, 32 KiB and 1,000 lines per file, 512 KiB total, at most 80 retained findings. Remove secrets and personal data. Raw source is processed transiently; reports retain findings and metadata, not uploaded source excerpts.

Which task are you doing?

These are independent product choices. Accounts, access, quotas and reports are not automatically shared. An optional CodHub metadata connection is separate from selected-file analysis. Repository source sync, automatic PR reviews and fix publishing are not yet available.

If the result is different