Plays4. PlaysWhat you can do nowTo doDoneDismissedDeadlinesSince you lookedChecking Plays…Plays could not be checked. This does not mean there is nothing to do.Plays are held while the actionability and safety checks are measured.Personal Plays are held until the measured rollout checks pass.Deadline reminders are held until the measured rollout checks pass.Sign in to see Plays for your saved tools.Personal Plays and Deadlines are included with Practitioner, Researcher and Business.Sign inSee plansRetrySave a tool in Your stack to see Plays for it.We have not checked every saved tool yet. There is no all-clear to report.No new action was found in the checked release sources. Checked as ofNo published Plays for this tool in the last 90 days. This is not an all-clear for the version you run.No Plays in this view.No dated Plays for your saved tools.Why it mattersDo thisBefore you startEstimated effortEffort has not been measured.Read the sourceSource evidenceAct before it breaksNot for meRemind me next weekHidden from To do until next week.That change was not saved. Try again.Keep my Play answers in my accountOptional: save Done, Not for me and reminders privately in your account. Your tools are matched in this browser. No answers are sent until you opt in.Erase my Play answersYour Play answers and private calendar link have been erased.Create a private calendar linkReplace calendar linkRevoke calendar linkAnyone with this link can read generic deadline events. It contains no tool names, versions or answers. Revoke it any time.Private calendar feedWithin 30 daysWithin 7 daysPast the published dateMore than 30 days awayAct byNo earlier visit saved for this tool.breakingtotal Plays since your last reviewReview this toolMark this tool reviewedReview dates stay in this browser. Opening this list does not mark a tool reviewed.Category moves this monthThere is not enough documented history to call a category move this month.Category history is unavailable. No monthly comparison can be made.Category moves are held until the measured rollout checks pass.The documented monthly history shows no category move.What we got wrongThere are too few reviewed Plays to report a correction rate.Play corrections have not been measured for this month.Plays reviewedcorrectedPublished in the last 90 days. Breaking changes come first.Saved tools are matched in this browser; your versions are not sent.Your Plays{count} PlaysWhat you can do with the tools you runRelease sources for {checked} of {total} saved tools checked; no new plays match this edition.Add your toolsRead the details on the webIn {count} daysWe corrected {wrong} of {count} reviewed Plays.
Summary
cortex-analyzers is an open-source AGPL repository of Cortex analyzers and responders for DFIRDFIRDigital forensics and incident response, investigating what happened during a security incident and containing it. The work includes preserving evidence, reconstructing activity and restoring systems. teams, used alongside TheHive and Cortex rather than as a standalone application. It connects incident-response workflows to services such as VirusTotal, AbuseIPDB, OpenCVE, CrowdStrike Falcon, OpenCTI, and Zscaler, including enrichment, malware analysis, URL intelligence, and actions such as submitting abuse reports or saving IDSIDSAn intrusion detection system, monitoring traffic or host activity for suspicious behavior and producing alerts. Detection alone does not necessarily block the activity. and YARA rules. Its documentation supports analyzers written in Linux-compatible languages including Python, Ruby, and Perl, so SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. and incident-response analysts can configure or extend it. The project had five tracked releases, with the last released this week.
Collection of Cortex analyzers and responders for automating observable analysis and response actions in TheHive Project.
Which protocols or versions are active on a specific server?
a port scanner answers this by listing what is listening and its version
Which manifests would be blocked by a specific policy?
the analyzer runs the entire rule set against a directory of YAML and lists every violation found by file and rule
Which workloads request privileges that were not approved?
the analyzer compares each pod spec against the rule set and names the containers requesting host access or root, along with the rule that was violated
Did a recent rule change accidentally expose something?
the analyzer replays a saved set of manifests against both versions of a rule and displays any discrepancies in the resulting verdict
Are all pipelines using the same security rules?
every run records the git reference of the policies it used, showing a mismatch if a pipeline judges against an outdated set of rules
What intelligence can be gathered about an IP address or domain?
the analyzer can use specialized integrations to look up threat intelligence, such as querying services or analyzing specific records.
Built from cortex-analyzers'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.
cortex-analyzers covers 3 of the 8 investigation and response capabilities we track.
What cortex-analyzers offers you
Command-line interface
No capabilities match.
+Response playbook automation2 featuresInvestigation and responsesince 2024▸
+Active response and blockingNot checked yet · Date unknownExecutes automated actions to block indicators, revoke sessions, or trigger takedowns in external systems.12 releases · first seen Nov 2024▸
Shared capability: Response playbook automation
+Verdict-based automated responseNot checked yet · Date unknownTriggers automated response actions based on analysis verdicts via the Suspicious_Verdict responder.5 releases · 1 other source · first seen Nov 2024▸
Shared capability: Response playbook automation
+Threat indicator matching2 featuresInvestigation and responsesince 2024▸
+Threat intelligence enrichmentNot checked yet · Date unknownQueries external threat intelligence platforms to enrich observables with context such as indicators, vulnerabilities, or malicious status.23 releases · first seen Feb 2024▸
Shared capability: Threat indicator matching
+Email breach lookupsNot checked yet · Date unknownChecks whether email addresses appear in known data breaches via the XposedOrNot analyzer, without requiring an API key.3 releases · first seen Mar 2025▸
Shared capability: Threat indicator matching
+Malware sandbox analysis1 featureInvestigation and responsesince 2026▸
+Sandbox analysisNot checked yet · Date unknownSubmits observables to the ANY.RUN sandbox for dynamic analysis, with support for proxy configuration, alternative domains, and automated interactivity options.1 release · first seen Oct 2026▸
Shared capability: Malware sandbox analysis
+Other / not yet classified4 featuresFeatures we have not matched to a capability yet. A suggested match is marked.▸
+Domain and IP registration lookupsNot checked yet · Date unknownRetrieves domain and IP registration data using the RDAP protocol via the RDAP analyzer.12 releases · first seen Feb 2024▸
+Malware scanningNot checked yet · Date unknownsuggestedScans observables for malware via the ScanMalware analyzer.5 releases · first seen Nov 2024▸
Suggested capability: Static malware analysis. This is our guess, not confirmed.
+MAC address enrichmentNot checked yet · Date unknownsuggestedLooks up MAC address metadata via the macaddress.com analyzer.2 releases · first seen Oct 2026▸
Suggested capability: Threat indicator matching. This is our guess, not confirmed.
+Analyzer development toolingNot checked yet · Date unknownProvides a TestAnalyzer utility that supports artifact-based observable testing to aid in developing and validating custom analyzers.1 release · first seen Oct 2026▸
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.
Command line
View
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
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 velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian time to a maintainer’s first reply
Nine scores for cortex-analyzers, 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.
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 cortex-analyzers 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.
Add XposedOrNot analyzer (email breach lookup, no API key required) by @DevaOnBreaches in https://github.com/TheHive-Project/Cortex-Analyzers/pull/1471
Nothing first seen in this window. That doesn't mean cortex-analyzers shipped nothing, only that we found no record of it.
Changes per month New Updated Retired
2026-09
3
2026-10
6
How we count
Read from 4 of 51 release notes and docs updates we hold for cortex-analyzers. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through cortex-analyzers's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Issue, contributor and maintainer activity in thehive-project/cortex-analyzers, 2023-12 – 2026-11,
as of 2026-11-03. Twelve-month figures first; the trend lines run
the whole window.
Contributorsnot measureddistinct committers, last 12 months
Maintainersnot measuredcore set, last 12 months
Bus factornot measuredcommitters behind half the commits
Community-filed100%of issues opened, last 12 months
Median time to close28 daysfirst maintainer reply 14 days
Open backlog116of 738 issues ever filed
Issues opened / month4 · 0communitymaintainers
Open backlog116
Contributors / monthnot measured
Commits / monthnot measured
Starsnot measured
Issue themes, last 12 months
other 100%
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
Libraries its release ships
What its latest release locks, checked against known advisories.
No high or critical advisory in the lockfiles we checked.
Fixed in cortex-analyzers 3.10.2 (it locked pillow 13.0.0, which has GHSA-332p-7hrc-92wf).
Fixed in cortex-analyzers 3.10.2 (it locked pillow 13.0.0, which has GHSA-332p-7hrc-92wf).
Fixed in cortex-analyzers 3.10.2 (it locked black 26.10.1, which has GHSA-cg8m-r9f2-5wm2).
Fixed in cortex-analyzers 3.10.2 (it locked nbconvert 7.17.2, which has GHSA-pjvx-prjx-h659).
Fixed in cortex-analyzers 3.10.4 (it locked pillow 13.0.0, which has GHSA-332p-7hrc-92wf).
We check the lockfiles its release builds images from: 22 Python. Go modules, other lockfiles and vendored code aren't checked.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can
follow every release here.
Copy this, send it to your AI assistant, then come back with its reply.
Nothing is sent from here. You paste the reply in the next step.
1 Copy
2 Paste
3 Confirm
Paste the reply
One tool per line is best. Versions are optional, and any format works. Names we don’t track are sent to us, without versions, so we can consider adding them.