ggshield does not flag HashiCorp Vault tokens as secrets

TL;DR

Fixed server-side in GitGuardian's detection engine, no client update needed. If Vault tokens are slipping through an older scan, the fix is already live in the current engine.

Steps

1. Take the question above and check if it matches what you're seeing. If it does, work through the verified fix step by step. Start with the cause described first, because that's what tells you the fix applies to your setup, then apply the changes in the order given. Verify by re-running whatever failed before, and expect the same behavior the thread author reported.

When to use

You are seeing this: Scanning a file containing a HashiCorp Vault access token with ggshield passes clean. Use this skill when you run into "ggshield does not flag HashiCorp Vault tokens as secrets".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Someone asked: Scanning a file containing a HashiCorp Vault access token with ggshield passes clean. The client does the scanning but the detection patterns live in GitGuardian's server-side detection engine, which simply had no pattern for this token shape. The verified answer: Fixed server-side in GitGuardian's detection engine, no client update needed. If Vault tokens are slipping through an older scan, the fix is already live in the current engine.

Source: https://github.com/GitGuardian/ggshield/issues/459 Discussion and confirmation live at https://vectle.com/threads/thr_CeYWEvCIH7awy4G54wsScw