Skip to content
| Marketplace
Sign in
Visual Studio Code>SCM Providers>Git TriageNew to Visual Studio Code? Get it now.
Git Triage

Git Triage

Conduit

| (0) | Free
Git status, changes, branches, history, and credential triage in one VS Code sidebar.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Git Triage

GitLab patched the CVE. Your leaked token is still valid.

Git Triage is a free, local-first VS Code extension for the 2026 GitLab credential leaks and the VS Code folder-open malware wave. It finds leaked GitLab credentials and hidden folder-open tasks, publishes them to the Problems panel and a dedicated view, and gives you a revoke → rotate → purge → verify runbook.

This extension wraps the open-source git-triage scanner. It reads workspace files locally. No account, no telemetry, and no scanner network calls. Git fetch/pull/push only contact your remotes when you run them.


Why this exists

GitLab shipped three CVSS 10.0 fixes in six weeks in 2026, including CVE-2026-85706, which let an unauthenticated attacker read /etc/gitlab/gitlab-secrets.json and decrypt CI/CD variables, deploy keys, and integration tokens.

Patching the server did not revoke the credentials that had already leaked.

The worst case is GitLab's incoming-email token: the glimt- string inside an incoming+...@incoming.gitlab.com address is account-wide, never expires, and is not checked against the sender. Change -issue to -merge-request, attach a .patch, and GitLab commits it as you and runs CI. It bypasses IP allow-lists and 2FA because it arrives by email.

GitLab's automatic revocation does not cover this token. The only fix is a manual reset.

Git Triage makes the credential and the execution surface visible before you trust the workspace.

Read the launch analysis: GitLab patched the CVE. Your leaked token is still valid.


Features

  • Find leaked GitLab credentials in the working tree: glimt- incoming-email tokens, glpat- PATs, and other GitLab token prefixes.
  • Find other leaked credentials: GitHub PATs, AWS access keys, npm tokens, OpenAI/Anthropic keys, SSH private keys.
  • Catch the folder-open malware pattern: hidden .vscode/tasks.json tasks with runOn: folderOpen, fake fonts/images that are scripts, malicious Git hooks, dangerous .git/config, submodule commands, and CI exfiltration patterns.
  • Problems panel integration: every finding with a file and line becomes a diagnostic.
  • Git Triage sidebar: a dashboard plus findings grouped by severity and the fix runbook.
  • Folder-open warning: a modal warning when the workspace contains a hidden task that runs a script disguised as an asset.
  • Fix runbook: a Markdown checklist for revoke → rotate → purge → verify.
  • History scan: optionally scan every commit with git log -p.
  • Secret-safe output: values are masked, deduped by SHA-256 fingerprint, and never sent anywhere.
  • CI-friendly core: the same engine powers the git-triage CLI and --ci mode.

Dashboard

The activity bar opens a single Git Triage dashboard. It has six tabs:

  • Overview — current branch, ahead/behind, staged/unstaged/untracked counts, latest commit, remotes, quick actions, and triage summary.
  • Changes — every changed file with status, stage/unstage/diff actions, bulk stage/unstage, and a commit box.
  • Branches — local branches with upstream and subject, checkout, and create-and-switch.
  • History — recent commits with author, relative time, and a commit view.
  • Triage — severity cards, findings, scan/scan-history, and the fix runbook.
  • Commands — a searchable Git command helper with syntax, examples, copy/run actions, and a git console that executes git commands in the workspace. Includes an Open Git Bash button for interactive commands.

The Findings tree remains available below the dashboard, and file/line findings are also published to the Problems panel.


Install

Search for Git Triage in the VS Code Marketplace, or install from the command line:

code --install-extension ps-aditya.git-triage

On Open VSX-based editors (VSCodium, Cursor, and others):

ovsx install ps-aditya.git-triage
# or use the Extensions view in your editor

Commands

Command What it does
Git Triage: Open Dashboard Focus the Git Triage dashboard.
Git Triage: Refresh Refresh status, changes, branches, history, and remotes.
Git Triage: Commit… Prompt for a message and commit staged changes.
Git Triage: Fetch Fetch all remotes and prune.
Git Triage: Pull Pull the current branch.
Git Triage: Push Push the current branch.
Git Triage: Checkout Branch… Pick a local branch to check out.
Git Triage: Create Branch… Create and switch to a new branch.
Git Triage: Initialize Repository Run git init in the workspace.
Git Triage: Open Terminal Open a terminal at the workspace root.
Git Triage: Open Git Bash Open Git Bash at the workspace root (falls back to the default shell).
Git Triage: Scan Workspace Scan the working tree.
Git Triage: Scan Workspace + History Scan the working tree and up to 500 commits.
Git Triage: Show Fix Runbook Open the remediation checklist as Markdown.
Git Triage: Open Settings Jump to the Git Triage settings.
Git Triage: Show Output Show the redacted scan log.
Git Triage: Reload in Restricted Mode Explain how to reload without trusting the workspace.

The extension adds a Git Triage activity bar view with the Dashboard and Findings views.


Settings

Setting Default Description
gitTriage.scanOnOpen true Scan when the extension activates.
gitTriage.history false Include git history in automatic scans.
gitTriage.maxCommits 500 Maximum commits to scan when history is enabled.
gitTriage.showProblems true Publish findings to the Problems panel.
gitTriage.warnOnFolderOpen true Warn when a hidden folder-open task or fake asset is found.
gitTriage.pollInterval 3000 Dashboard refresh interval while visible, in milliseconds.
gitTriage.logLimit 20 Number of recent commits in the History tab.
gitTriage.openDashboardOnStartup false Focus the dashboard when the extension activates.

What it detects

Credentials

  • GitLab incoming-email tokens (glimt-) and full incoming addresses
  • GitLab PATs (glpat-) and other GitLab tokens (glrt-, glcbt-, glptt-, gldt-, glsoat-, glffct-)
  • GitHub fine-grained PATs and classic tokens
  • AWS access key IDs
  • npm tokens
  • OpenAI and Anthropic API keys
  • SSH private keys

VS Code execution surface

  • Hidden folderOpen tasks that run a shell command
  • Hidden folderOpen tasks that run a script disguised as a font/image
  • Any folderOpen task
  • Fonts/images that contain JavaScript, shell, or Node.js code
  • Fonts/images that are ZIP archives or text mismatches

Git configuration and hooks

  • Non-sample Git hooks, especially post-checkout, post-merge, pre-commit, pre-push
  • core.fsmonitor, core.sshCommand, core.editor, core.pager
  • include.path / includeIf
  • url.*.insteadOf
  • Credential helpers that start with !
  • Submodule update = !command, ext:: URLs, and file:// URLs

CI exfiltration patterns

  • curl … | bash, wget … | sh
  • Base64-decoded execution
  • CI token names near network commands
  • History greps for credentials
  • runs-on: self-hosted, pull_request_target, secrets: inherit, permissions: write-all

Safety and limitations

  • Local-first: the extension reads workspace files and prints findings. It does not upload code or telemetry.
  • No automatic execution: scanning never runs repository tasks, scripts, hooks, or tests. Git actions you explicitly trigger run the git CLI in the workspace, so your configured Git hooks may run as usual.
  • Detector, not sandbox: it cannot stop a task from running if you trust the workspace and ignore the warning.
  • Not automatic: v0.1 finds and guides. It does not revoke credentials, rotate them, or rewrite history.
  • Pattern-based: a new loader with a different file name or task label may evade detection.
  • Single root: v0.1 scans the first workspace folder. Multi-root support is on the roadmap.
  • Workspace Trust: the folder-open task only executes after the workspace is trusted. The extension warns, but it cannot change VS Code's trust model.
  • Restricted git console: the Commands tab only runs git commands, one at a time. Shell pipes, redirects, chaining, and non-git programs are rejected. Interactive commands (git add -p, git rebase -i, git mergetool, a git commit without -m, …) are routed to Open Git Bash.
  • Destructive commands ask first: hard resets, forced cleans, force-pushes, branch deletes, restores, stash drops, and history rewrites require a modal confirmation before they run.

If you open an untrusted repository, review the findings before clicking Trust. If you already trusted a malicious repo, treat the credentials on that machine as exposed and rotate them from a clean machine.


Development

cd vscode-extension
npm install
npm run typecheck
npm run test:dashboard
npm run build
npm run package

Node.js 22.22+ or 24 is required for the jsdom-based dashboard smoke test.

The extension bundles the published git-triage scanner. The source lives in ps-aditya/git-triage.

Package and publish

npm run package
npx @vscode/vsce publish git-triage-vscode.vsix -p "$VSCE_PAT"   # VS Code Marketplace
npx ovsx publish git-triage-vscode.vsix -p "$OVSX_PAT"           # Open VSX

For the VS Code Marketplace, create the ps-aditya publisher at https://marketplace.visualstudio.com/manage and an Azure DevOps personal access token with Marketplace → Manage scope. For Open VSX, create the ps-aditya namespace and a token at https://open-vsx.org. In GitHub Actions, add VSCE_PAT / OVSX_PAT as repository secrets and run the corresponding publish workflow, or run the commands above locally.


Links

  • GitHub: https://github.com/ps-aditya/git-triage
  • npm CLI: https://www.npmjs.com/package/git-triage
  • Launch post: https://github.com/ps-aditya/git-triage/blob/main/blog/2026-11-01-gitlab-patched-the-cve-your-token-is-still-valid.md
  • Teardown: https://github.com/ps-aditya/git-triage/blob/main/docs/gitlab-glimt-teardown.md

License

MIT. See LICENSE.

Git Triage is an independent project. It is not affiliated with GitLab, GitHub, GitKraken, Microsoft, or VS Code. “GitLab,” “GitHub,” and “VS Code” are trademarks of their respective owners.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft