PAGES
← all tools
◆ Software Supply Chain Security

Legit Security

Your AI Agent Has New Skills. Can You Trust Them? (2026-08-20) commercial

Legit Security is a platform that secures software development pipelines by detecting and preventing supply chain attacks across code, build, and deployment stages.

Summary

Legit Security is a commercial application security posture managementapplication security posture managementApplication security posture management, combining findings about applications from multiple tools and relating them to business context. It helps teams decide which fixes matter most. platform that inventories and governs the software supply chainsoftware supply chainThe dependencies, tools and processes used to build and deliver software. Compromising one part can affect the products or organizations that rely on it., including, through its VibeGuard capability, the AI agents, models, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers, and skills running on developer endpoints. It runs as an agent on developer machines feeding into a central management layer, and is aimed at security teams responsible for CI/CD and supply-chain risk rather than at individual developers, though it surfaces sensitive or destructive agent actions — deleting code, altering database data, touching production systems — to developers directly for human review before execution. This lets security teams set organizational policy over which AI agents and models are permitted in development, sitting at the intersection of ASPMASPMApplication security posture management, combining findings about applications from multiple tools and relating them to business context. It helps teams decide which fixes matter most., secrets detection, and the newer problem of agentic development tooling. The company shipped its latest release, VibeGuard 2.0, 16 days ago, suggesting active development.

Legit Security is a platform that secures software development pipelines by detecting and preventing supply chain attacks across code, build, and deployment stages.

Legit Security publishes no documentation we track, so the description above is written from general knowledge rather than the vendor's own words.

How Legit Security helps

Which AI agents, models, MCP servers, and skills are actually running on developer machines right now?

an agent on each endpoint discovers and inventories what's installed and active in the agentic environment, feeding a central view security teams can check against what's actually permitted

Which agents are running that nobody in security ever approved?

compares the discovered inventory against organizational policy and flags agents, skills, and models operating outside what's been sanctioned

Is an agent about to delete code, alter database data, or touch a production system before it happens?

flags the action at runtime and surfaces it to the developer for human review before execution, rather than logging it after the fact

Who let a given AI model or MCP server onto a developer machine, and when?

the endpoint inventory ties each discovered agent, model, or skill to the machine it was found on, giving security teams a record to check enforcement against

Does a new package or dependency pulled into a project carry a known flaw or an exposed secret?

sits across the software supply chain, correlating dependency and secrets data with the same posture-management layer used for agent governance

Are the same permitted-agent rules being enforced consistently across every developer's machine?

the central management layer aggregates what each endpoint agent reports, so a machine running an unsanctioned or outdated policy set shows up against the rest

all 3 features, with the evidence for each →

Languages

Not documented

Features

3 capabilities

Built from Legit Security's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date.

Compare with peers →

All capabilities 3 capabilities
AI agent and model discovery shipped Discovers and inventories AI agents, models, MCP servers, and skills running in the agentic environment on developer endpoints. 1 release · first seen Aug 2026

release

  • Legit VibeGuard 2.0 extends developer endpoint security to discover and inventory AI agents, models, MCP servers, and skills running in the agentic environment on developer endpoints. Your AI Agent Has New Skills. Can You Trust Them? (2026-08-20) · Aug 2026 · source · release history
AI agent and model policy enforcement shipped Lets security teams enforce organizational policy over which AI agents, skills, and models are permitted in the development environment. 1 release · first seen Aug 2026

release

  • Enables security teams to enforce organizational policy over which AI agents, skills, and models are permitted in the development environment. Your AI Agent Has New Skills. Can You Trust Them? (2026-08-20) · Aug 2026 · source · release history
Sensitive agent action interception shipped Surfaces sensitive or destructive agent actions at runtime for human-in-the-loop review before they are executed. 1 release · first seen Aug 2026

release

  • Surfaces sensitive or destructive agent actions — such as deleting code, altering database data, or touching production resources — to the developer at runtime for human-in-the-loop review before execution. Your AI Agent Has New Skills. Can You Trust Them? (2026-08-20) · Aug 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 Legit Security, 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 Legit Security 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

legitsecurity.com, every change

Legit Security's home page and 24 more pages as they looked each month from December 2021 to October 2026: 35 renders, 4 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

1 entry

  1. August 20261

    1 entry

    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 →