Skip to content

W008 false positive: redaction marker treated as proof of a secret (v0.5.16) #412

Open

Description

@sgaabdu4

Scanning a public skill with v0.5.16 produces a W008 high at risk 1.00, and the finding's own text says no secret was found.

Command:

uvx snyk-agent-scan@latest <repo>/skills/building-flutter-apps

Output:

Secret detected (high risk: 1.00). The pre-filtered potential matches include literal redaction markers of the form "**REDACTED_SECRET_*...**". Per the scanning rules a redaction marker of that exact form indicates a real credential was found and then stripped before scanning, and must be treated as a true secret (not a placeholder). I found no actual high-entropy secret values in the visible file contents, so there is no file/line to point to inside the provided skill files; the evidence comes from the separate <potential_matches> redaction markers.

The reasoning looks circular. The pre-filter redacts something, then the judge reads its own redaction marker as evidence that a credential was there.

What I checked in the source:

The string REDACTED does not appear anywhere in the skill. There are no secret-shaped values either, nothing matching ghp_, gho_, github_pat_, sk-, AKIA, xox, or a PEM header. The only hits for secret-like terms are GitHub Actions references such as ${{ secrets.WINDOWS_PUBLISHER_TOKEN }} in assets/windows-installer-workflow.yml, and prose telling readers to keep tokens out of source, for example "SENTRY_AUTH_TOKEN = build-only secret; never source + app config + runtime bundle" in references/error-reporting.md.

Repro is public: https://github.com/sgaabdu4/building-flutter-apps, skill at skills/building-flutter-apps, 41 instruction files and 8 assets.

Two reasons this matters. A high at risk 1.00 with no file or line isn't actionable by the author, and these results feed the public security panels on skills.sh.

Version 0.5.16, macOS, run via uvx.

Activity

  1. wkeifenheim commented on Aug 7, 2026

    @wkeifenheim

    Skills managed with the gh CLI add frontmatter metadata to the SKILL.md file, I assume to aide in version tracking and facilitate updating them.

    Examples of the metadata added by gh skills install..

    metadata:
        github-path: skills/dagster-expert/skills/dagster-expert
        github-ref: refs/tags/v1.13.14
        github-repo: https://github.com/dagster-io/skills
        github-tree-sha: 5f6d9abbdfdeb438fcd9e62714c247964ce864bf
    metadata:
        github-path: skills/caveman
        github-ref: refs/tags/v1.10.0
        github-repo: https://github.com/JuliusBrussee/caveman
        github-tree-sha: 3e4386ca694c65a65ba84024f0fe2646a8c9076a

    This results in a W008 finding on github-tree-sha when running agent-scan.

    I do not have any specific recommendation on how not to trigger on this scenario, but did want to include it for consideration on a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions