GitGuardian SaaS is a cloud-based security platform that detects and prevents secret leaks in Git repositories and source code.
GitGuardian SaaS added new API endpoints for secret location listing and live scan progress, plus a custom secret-validity API, honeytoken protection for developer endpoints, and programmatic PATPATA personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it./SAT token management.
what's the number?
Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.
- depth0–40 what it does and how it works or what changed
- specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
- actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.
New GET /v1/incidents/secrets/{incident_id}/locations endpoint lists every file on a source's default branch still holding a secret for a given incident, with exact line positions, filterable by source, number_of_mentions_min, number_of_mentions_max, code_fix_request_status (processing, created, error), and search (filepath substring), sortable by last_updated_at, number_of_mentions, or source. A companion GET /v1/sources/{source_id}/locations endpoint lists all files in a single source with any secret on the default branch, carrying the same per-match line positions, filters, and sort options.
$ curl -s -H 'Authorization: Token <api_key>' 'https://api.gitguardian.com/v1/incidents/secrets/42/locations?monitored=true&number_of_mentions_min=2&ordering=-number_of_mentions'
$ curl -s -H 'Authorization: Token <api_key>' 'https://api.gitguardian.com/v1/sources/5523/locations?search=settings.py&code_fix_request_status=created'
The ggshield honeytoken plant command (via the existing agent binary) plants a decoy AWS credential on developer endpoints; any use of the decoy triggers an alert naming the compromised machine, its IP address, user agent, and timestamp, with no new agent required. A new Honeytoken protection card in the Endpoints dashboard reports fleet coverage percentage and lists unprotected endpoints.
$ ggshield honeytoken plant
New beta GET /v1/scans/{scan_id}/live-progress endpoint returns the live status (queued, in_progress, completed) and real-time counters (elements_scanned, elements_total, elements_skipped, elements_failed, data_downloaded_bytes, data_scanned_bytes) for a running historical scan, including an audit_url field once the scan completes.
completed is returned, then fetch the audit summary from audit_url.$ curl -s -H 'Authorization: Token <api_key>' 'https://api.gitguardian.com/v1/scans/<scan_id>/live-progress'
A new API endpoint lets teams push their own validity status (valid or invalid) for secrets on unreachable internal systems, authenticated with a personal access tokenpersonal access tokenA personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. scoped to secrets:write; the status propagates to all incidents for that secret, appears as Custom validity with a datestamp, and is recorded in the incident activity log and audit log.
The API now supports creating Personal Access Tokens (PATsPATsA personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it.) and Service Account Tokens (SATs) programmatically for automated token rotation workflows; tokens created via the API must have a finite TTLTTLTime to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit.. Scans triggered via a Personal Access Token now also emit an audit log event.