caldera
5.3.0 open-sourceThe section your link pointed to isn't on caldera's page any more, so we've brought you to the top.
Cyber security platform built on MITRE ATT&CKMITRE ATT&CKA publicly maintained knowledge base of adversary tactics and techniques observed in real attacks, maintained by MITRE. Cyber tools use it as a common taxonomy to classify, map, and communicate threat behavior. for automating adversary emulation, assisting red teams, and automating incident response.
./caldera --fresh
# In your plugin's __init__.py or hook file:
def enable(app_svc, services):
# ... initialization logic ...
pass
# Note: 'app' is no longer passed directly; access it via app_svc.application if needed.
# When configuring the 54ndc47 C2 channel in your adversary profile or operation settings:
# "sleep": 10
# This delays the agent's first check-in by 10 seconds.
Summary
Caldera is an open-source adversary emulation platform, self-hosted as a command-and-control server with a REST APIREST APIA web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services. and web interface, extended through plugins for agents, TTPTTPTactics, techniques and procedures, the goals, methods and specific behaviors used by an attacker. They describe how an attack works, rather than only the files or addresses it leaves behind. collections, and reporting. Built on the MITREMITREA US federally funded research and development center that maintains public frameworks—ATT&CK, CVE, D3FEND—that cyber tools use to classify threats, vulnerabilities, and defensive techniques in a common language. ATT&CKATT&CKA publicly maintained knowledge base by MITRE cataloguing adversary tactics, techniques, and procedures observed in real attacks, giving cyber tools a common taxonomy for classifying and correlating threat behavior. framework, it runs autonomous breach-and-attack simulations or supports manual engagements, making it a fit for red teamers and incident-response teams rather than platform engineers or developers. Started in 2017 and still active, with 160 contributors and 361 commits in the past year, though its most recent release was 484 days ago, worth checking release cadence before committing.
Cyber security platform built on MITRE ATT&CK for automating adversary emulation, assisting red teams, and automating incident response.
How caldera helps
Can our defenses actually catch an adversary before one shows up for real?
executes chained ATT&CK techniques against live agents on real hosts and records which steps succeeded, failed, or triggered an alert, mapped back to the technique that caused it
Which of our endpoints can be reached from one that is already compromised?
agents installed on hosts attempt lateral movement techniques between them and the operation report shows which machines were reachable and by what path
What would an incident-response team actually see if this technique ran on our network?
runs the ability on a live agent and logs the resulting events so the output can be checked against what the monitoring stack captured
Which techniques in our playbook have never actually been tested against our own hosts?
adversary profiles group abilities by ATT&CK technique, and past operation results show which ones have been run and which have only ever been documented
Did we close the gap the last engagement found?
operation logs from prior runs record which steps succeeded or were caught, so a new run against the same profile shows whether the same steps still get through
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for caldera, 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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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 caldera 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…
Releases
17 entries
No entries match these filters.
- April 20251
- February 20251
- February 20241
- June 20231
- September 20221
- June 20221
- January 20221
- April 20211
- February 20211
- October 20201
- March 20202
- February 20201
- January 20202
- December 20191
- August 20191
Project health
Issue, contributor and maintainer activity in mitre/caldera, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 14 +1 vs prior 12 months
- Maintainers 2 +1 joined · −2 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog not measured open issues today
- Issues opened / month not measured
- Open backlog not measured
- Contributors / month 0
- Commits / month 0
- Stars 7,269
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Articles
1 article · updated Nov 4, 2026Where caldera turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.
Tutorials & guides 1
-
Caldera: Red Team Emulation (Part 1)
Caldera is an open-source framework that assists in Red Team Emulation.
2 more quotes
Table of Contents MITRE Att&ck Caldera Pre-requisite & dependencies Interface Installation Plugins Campaigns Step1: Deploy an Agent Step2: Abilities Step3: Setting up Operations Step4: Exporting the result Conclusion…
Caldera CALDERA breach & emulation tool designed to easily automate adversary emulation, assist manual red-teams and automate incident response.
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →