Read the change.
See what supports it.

A useful review connects a changed line to evidence, context and the questions that still need your judgment.

A fine monochrome source structure unfolds into selected evidence and bounded connections. — Conceptual illustration · inspect the changed line and its supporting evidence.

01 / EVIDENCE

Read the source.

Each finding identifies its location, reviewed commit, severity and explanation. Security analysis separates observed patterns, inferred exposure and proposed hardening.

02 / CONTEXT

Follow the connection.

Bounded JavaScript and TypeScript context links supported imports, calls and tests. Each connection has source evidence; dynamic calls and uninspected dependencies remain unknown.

03 / DECISION

Record your judgment.

Accept an issue, explain a false positive, record a fix assessment, or accept risk. These decisions remain tied to the repository and review; they do not silently change security rules.

A useful report includes
what it could not check.

Missing source, omitted files, unsupported syntax and unavailable CI remain visible. A high evidence score is not permission to merge.

Measured checks

Inspect eligible touched-function documentation and available GitHub check results. Skipped and unavailable checks are separate from passes. The report explains the scope of each measurement.

Understand the security boundary →