Lomo CodeSecurity

VS CODE / CODESECURITY

Follow the finding. Read the evidence.

Two recordings follow the same finding through VS Code, the workbench and a saved Advisor explanation. The repository contains deliberately vulnerable SRE examples, so there is something concrete to investigate.

Inspect the finding

A critical Python finding in VS Code, from the source line to its details in the workbench.

Start at the reported line, open the finding from its VS Code hover and inspect the source evidence in the workbench.

Finding review guide

Read the saved Advisor review

The saved Advisor explanation and suggested correction for the same critical Python finding.

Compare the saved explanation and suggested fix with the same source. The advice adds another reading; it does not decide the gate or verify a repair.

Advisor guide

NEXT / PUSH PROTECTION

Take the review to outgoing history.

A reviewed finding is one part of the decision. Next, set the repository policy and deliberately apply protection to its clone. The guide explains what the local hook checks and how to read a block.

Set up push protection