repo-review-security

A bounded security review scopes the audit to trust boundaries, secret handling, injection risks, privilege failures, unsafe IO, deserialization, and supply-chain exposure. You provide a repository slice, and the reviewer generates a structured findings artifact without implementing remediation.

An abuse-path review identifies how a system might be maliciously exploited rather than just checking for functional bugs. It generates findings with severity, affected surface, and abuse scenarios, enabling targeted risk assessment within a larger security workflow.

Yes, you can automate checks for secret handling and injection risks by scoping a security review to those specific trust boundaries. The reviewer outputs a structured artifact containing validation status and residual risk for governance and audit purposes.

No, this security review tool does not implement remediation. It performs a bounded assessment to identify findings, including privilege and permission failures, and emits a structured review artifact containing the affected surface and residual risk for downstream handling.

The best way to assess supply-chain exposure is to run a bounded security review scoped to supply-chain risks. This generates a structured artifact detailing the affected surface, validation status, and residual risk without applying any code remediation.

You need a trust-boundary analysis when scoping a security investigation to determine where data crosses privilege levels. It outputs a structured review artifact with findings and abuse scenarios, suitable for integration into governance and audit workflows.