All issues

Search results

gitlab-sast: every finding is reported at the repository root

Status: Open.

#705 In awslabs/ferret-scan;

· 2018-lonely-droid opened on Sep 18, 2026

ASH integration follow-ups: seven ferret-scan decisions the contract guard deliberately does not make

Status: Open.

#704 In awslabs/ferret-scan;

· sectoramen opened on Sep 18, 2026

ASH integration: five environment variables silently change what ASH gets, our next minor release would strand every ASH user, and nothing in this repo referenced ASH at all

Status: Open.

#702 In awslabs/ferret-scan;

· sectoramen opened on Sep 17, 2026

metadata: a provenance value reaches 100 HIGH when the product name contains a validator keyword (7 validators)

Status: Open.

#692 In awslabs/ferret-scan;

· sectoramen opened on Sep 15, 2026

cross-validator deconfliction: 5.15% of findings are sub-spans of a wider, more-confident finding, and only redaction knows it

Status: Open.

#687 In awslabs/ferret-scan;

· sectoramen opened on Sep 15, 2026

complexity guard: two maxGrowthRatio controls sit under the 1.5x margin convention on macos, and the linear control's 6.40x is unexplained

Status: Open.

#649 In awslabs/ferret-scan;

· sectoramen opened on Sep 10, 2026

CHANGELOG: [Unreleased] has swallowed 27 releases — promote it at release time instead of generating it

Status: Open.

#647 In awslabs/ferret-scan;

· sectoramen opened on Sep 9, 2026

validators: every finding's metadata map sits exactly at a Go bucket cliff — the next key added costs ~342 B per finding

Status: Open.

#621 In awslabs/ferret-scan;

· sectoramen opened on Sep 9, 2026

Trust-boundary decision for a config discovered inside the scan target: opt-in gating, a THREAT_MODEL entry, and the pre-commit gate that silences the provenance disclosure

Status: Open.

#293 In awslabs/ferret-scan;

· sectoramen opened on Aug 12, 2026