PAGES
← all tools
◆ SAST / SCA / Code Security

Wiz Code

2026-08-13-8ecb9077 commercial

Wiz Code is a developer security tool that scans code and infrastructure-as-code for vulnerabilities and misconfigurations during the development lifecycle.

Summary

Wiz Code is a commercial appsec platform, run as a SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. service, that scans code, pipelines, and cloud deployments to find and fix vulnerabilities before and after they ship. It combines deterministic rule-based SASTSASTStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment. with agentic AI analysis: Atlas, its autonomous research engine, maps attack surfacesattack surfacesThe exposed systems, interfaces and access points an attacker could try to use. It includes internet-facing services as well as identities, software and other reachable resources. and validates findings with working exploits, while a multi-engine orchestration layer routes analysis across first- and third-party scanners, including Google CodeMender, correlating results on the Wiz Security Graph. Shift-left tracing links production vulnerabilities back to their source repository or image, and it also inventories secrets exposed in developers' personal GitHub repositories, tying them to identities and downstream blast radius. It targets application security and platform teams responsible for code and pipeline risk across large codebases. Launched in 2020, with its latest release 44 days ago, the product is under active development.

Wiz Code is a developer security tool that scans code and infrastructure-as-code for vulnerabilities and misconfigurations during the development lifecycle.

How Wiz Code helps

Which vulnerabilities in this codebase are actually exploitable versus theoretical?

maps the surrounding attack surface and generates a working exploit to confirm each finding before it reaches a developer, cutting down flags that never posed real risk

Which business logic flaws would a pattern-matching scanner miss?

models application entry points, trust boundaries, and data flows across the codebase to surface logic errors that don't match a known bad-code signature

Where in our production environment did this vulnerability actually come from?

traces the flaw back through deployment context to the originating repository or container image so the fix happens at the source instead of downstream

Are secrets sitting exposed in a developer's personal GitHub repositories outside our org's control?

inventories personal repos tied to known developer identities and correlates any exposed credentials against the organization's own resources

Whose commit leaked this credential and can someone act on it right now?

pinpoints the exact commit, GitHub user, and email behind the exposed secret and can open a ticket or notification so the owner rotates or revokes it without manual digging

Which repositories deserve deep investigation versus a quick automated check?

uses runtime, identity, deployment, and attack-surface context on the security graph to rank repositories for deterministic, continuous, or deep agentic analysis

all 8 features, with the evidence for each →

Features

8 capabilities

Built from Wiz Code's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • Wiz Code covers 1 of the 2 secrets and credential hygiene capabilities we track.

What Wiz Code offers you

  • CI/CD pipeline integration1
  • Ticketing integration1
All capabilities 8 capabilities
Agentic deep-code pentesting shipped Uses the Atlas autonomous vulnerability research system — with specialised agents that map attack surfaces, hunt in parallel, and adversarially validate findings — to produce confirmed exploits for high-value or critical code targets. 3 releases · first seen Jul 2026

release

  • Introduces exploitability validation via the Wiz Red Agent — an AI-powered attacker that actively tests whether an exposed credential is live and what it can reach, going beyond traditional validity checks. changelog · Aug 2026 · source · release history
  • Atlas vulnerability research system is being productized as a first-party deep-analysis engine for targeted agentic pentesting of high-value applications and critical code. changelog · Jul 2026 · source · release history
  • Introduces Atlas, an autonomous AI vulnerability research system that uses specialized agents to map attack surfaces, hunt in parallel, and adversarially validate findings — each confirmed with a dynamically generated, working exploit. changelog · Jul 2026 · source · release history
Multi-engine agentic scanning orchestration shipped Routes code analysis across first- and third-party agentic engines (including Google CodeMender), correlates all findings on the Wiz Security Graph, and feeds results through existing AppSec validation and remediation workflows. 3 releases · first seen Jul 2026

release

  • Surfaces identity-attached findings with the exact commit, GitHub user, and email that pushed a secret, enabling immediate owner-assigned remediation without manual investigation. changelog · Aug 2026 · source · release history
  • New orchestration of Google CodeMender as a third-party agentic engine for complementary code analysis and remediation. changelog · Jul 2026 · source · release history
  • New open, multi-engine orchestration layer routes analysis across first- and third-party agentic scanning engines, with all findings correlated on the Wiz Security Graph and flowing through existing AppSec validation and remediation workflows. changelog · Jul 2026 · source · release history
Security Graph–driven code prioritisation shipped Connects code findings with runtime, identity, deployment, and attack surface context to determine which repositories are routed to deterministic, continuous AI, or deep agentic analysis. 3 releases · first seen Jul 2026

Also counts toward: Ticketing integration

release

  • Integrates personal-repo findings into existing remediation workflows including Jira ticket creation, Slack developer notification, and tracked token rotation and revocation. changelog · Aug 2026 · source · release history
  • Enriches secrets found in personal repositories onto the Wiz Security Graph to show the full attack path and blast radius of a compromised credential, including downstream resource access. changelog · Aug 2026 · source · release history
  • Wiz Security Graph now connects code findings with runtime, identity, deployment, and attack surface context to prioritize which repositories receive deterministic, continuous AI, or deep agentic investigation. changelog · Jul 2026 · source · release history
AI-powered SAST shipped Continuously analyses code using AI to model entry points, trust boundaries, and data flows, surfacing complex business logic flaws that pattern-matching scanners miss. 2 releases · 1 other source · first seen Jul 2026

release

  • New Wiz AI SAST (Private Preview): continuous AI-powered first-party code analysis that models application entry points, trust boundaries, and data flows to surface complex business logic flaws missed by pattern-matching scanners. changelog · Jul 2026 · source · release history
  • Adds AI SAST at scale: Atlas performs continuous, cost-efficient deep code scanning across entire enterprise codebases using a code property graph (CPG) for call- and data-flow–grounded analysis. changelog · Jul 2026 · source · release history

example

  • Enroll your organization in broad, continuous AI code scanning to catch business logic flaws on every PR without custom configuration. In the Wiz console, go to Wiz Code settings and join the Wiz AI SAST Private Preview to enable continuous AI scanning within your existing Wiz Code workflows. changelog · Jul 2026 · source
Outbound identity and secret correlation shipped Surveys developer public repositories outside organization boundaries to identify exposed secrets and correlate them with internal assets. 1 release · first seen Aug 2026

release

  • Adds automated inventory and correlation of developer identities to their personal public GitHub repositories outside org boundaries, closing the visibility gap where unmanaged secret exposure lives. changelog · Aug 2026 · source · release history
Rule-based SAST shipped Deterministically scans code to block known vulnerability patterns, insecure code, and hardcoded secrets before changes are merged. 1 release · first seen Jul 2026

Shared capability: Secret scanning

release

  • New Wiz Rule-Based SAST (GA): deterministic scanning that automatically blocks known vulnerability patterns, insecure code, and hardcoded secrets before code is merged. changelog · Jul 2026 · source · release history
Pipeline scanning for AI applications and model deployments shipped Extends pipeline scanning beyond container images, packages, and IaC to cover AI application configurations and model deployments, enforcing Secure by Design guardrails. 1 release · first seen Jul 2026

Also counts toward: CI/CD pipeline integration

release

  • Extends pipeline scanning to AI application configurations and model deployments, in addition to container images, software packages, and IaC, to enforce Secure by Design guardrails. changelog · Jul 2026 · source · release history
Shift-left tracing from production to source shipped Links vulnerabilities discovered in production back to their originating code repository or container image so that fixes can be applied at the source. 1 release · first seen Jul 2026

release

  • Adds shift-left tracing that links vulnerabilities discovered in production back to their originating code repository or container image, enabling fixes at the source. changelog · Jul 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface

Five scores for Wiz Code, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Wiz Code puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Website history

wiz.io, every change

Wiz's home page and 21 more pages as they looked each month from September 2021 to October 2026: 94 renders, 19 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Releases

4 entries

  1. August 20262
  2. July 20262

    4 entries

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →