PAGES
← all tools
◆ Malware Analysis

YARA

v4.6.0 open-source

YARA is a tool that helps malware researchers identify and classify malware samples using rules based on textual or binary patterns.

Summary

YARA is an open-source pattern-matching tool that helps malware researchers identify and classify malware samples by writing rules combining textual or binary patterns with boolean logic. It runs as a command-line scanner, matching rulesets against a single file or recursively across a directory, and can also be driven from Python scripts via the yara-python extension. It is built for malware analysts and threat researchers who need to fingerprint files by content rather than by hash. The project is multi-platform, running on Windows, Linux, and Mac OS X, and README notes complementary tools like YARA-CI for testing rules and yextend for scanning inside compressed archives. Now in maintenance mode as development shifts to YARA-X, it still sees active upkeep, with 250 contributors and a release cut just 24 days ago.

YARA is a tool that helps malware researchers identify and classify malware samples using rules based on textual or binary patterns.

How YARA helps

Which of my files contain a known-malicious pattern?

scans a file or directory recursively against a ruleset and reports every match by rule name and file path, down to the exact byte offset where the pattern occurred

Did a secret or hardcoded credential leak into my source tree?

matches string and boolean-logic rules against a codebase and names each file that contains the pattern, along with the matched string and its offset

Which files in this batch can I rule out so I only review the real hits?

tags every scanned file with a match count, letting the files that scored zero be filtered out and the remainder narrowed to the ones worth inspecting by hand

What exactly matched, and is it obfuscated or plaintext?

reports the matched string's length and offset and can compute an XOR key against the surrounding bytes, showing whether the content sits in the clear or was disguised

Which malware family does this sample belong to, based on more than its hash?

evaluates the sample's content against rules built from textual or binary patterns and boolean conditions, so a match holds even when the file has been repacked or renamed

Can I classify a sample from inside my own analysis pipeline rather than the command line?

the same ruleset and matching engine is callable from a Python script, returning matches programmatically so classification can run as a step in a larger tool

all 35 features, with the evidence for each →

Languages

Not documented

Features

35 capabilities across 4 capability groups · 4 backed by code, an API document or a real run

Built from YARA'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 →

  • YARA covers 4 of the 8 investigation and response capabilities we track.

What YARA offers you

  • Command-line interface5
Static malware analysis 5 features Investigation and response since 2014
ELF binary scanning shipped Enables the parsing and analysis of ELF (Executable and Linkable Format) file structures for pattern matching within YARA rules. 6 releases · 1 other source · first seen Nov 2014

Shared capability: Static malware analysis

release

  • Exposes nine new elf.machine named constants in the elf module: EM_PARISC (15), EM_SPARC32PLUS (18), EM_S390 (22), EM_MCORE/EM_RCE (39), EM_SH (42), EM_SPARCV9 (43), EM_ARC_COMPACT (93), EM_BPF (247), and EM_LOONGARCH (258), replacing the need to hardcode raw numbers in rules. v4.6.0 · Oct 2026 · source · release history
  • Adds telfhash() function to the elf module v4.3.0 · Mar 2023 · source · release history
  • Adds --no-follow-links command-line option to prevent following symbolic links during scans v4.1.0 · Apr 2021 · source · release history
  • Functions import_ordinal, is_dll, is_32bit and is_64bit added to PE module v3.5.0 · Sep 2016 · source · release history
  • Fields rich_signature.toolid and rich_signature.version added to PE module v3.5.0 · Sep 2016 · source · release history
  • Adds elf module for scanning ELF binaries v3.2.0 · Nov 2014 · source · release history

example

  • Scan a directory without following symbolic links to prevent unintended file access. yara --no-follow-links rules.yar /path/to/directory v4.1.0 · Apr 2021 · source
.NET module support shipped Enables the parsing and analysis of .NET binary structures for pattern matching within YARA rules. 4 releases · first seen May 2017

Shared capability: Static malware analysis

release

  • Adds parsing of .NET user types from the .NET metadata stream in the dotnet module v4.3.0 · Mar 2023 · source · release history
  • Adds is_dotnet field to the dotnet module output v4.2.0 · Mar 2022 · source · release history
  • Builds the dotnet module into YARA by default instead of requiring external loading v4.2.0 · Mar 2022 · source · release history
  • Introduces a new .NET module for scanning v3.6.0 · May 2017 · source · release history
Module data dumping capability shipped Allows users to print module-specific data (such as PE headers) to stdout for debugging purposes. 2 releases · 1 other source · first seen Jun 2015

Shared capability: Static malware analysis

release

  • Adds pdb_path field and export_details array/exports_index() function to the pe module v4.0.0 · Apr 2020 · source · release history
  • Adds --print-module-data CLI option to print module-specific data during scanning v3.4.0 · Jun 2015 · source · release history

example

  • Scan a file and dump module data (e.g., PE headers) to stdout for debugging. yara --print-module-data rules.yar target.bin v3.4.0 · Jun 2015 · source
PE module field extensions shipped Adds specific fields to the PE module, including rich signature tool ID and version information. 2 releases · first seen Sep 2016

Shared capability: Static malware analysis

release

  • Exposes the RVA function in the pe.export_details module. v4.5.0 · Feb 2024 · source · release history
  • Fields rich_signature.toolid and rich_signature.version added to PE module v3.5.0 · Sep 2016 · source · release history
DotNET PE offset analysis shipped Provides access to field offsets for PE structures within the DotNET module, facilitating detailed binary analysis. 1 release · first seen Oct 2019

Shared capability: Static malware analysis

release

Threat indicator matching 4 features Investigation and response since 2014
Match offset and string reporting verified Reports the byte offset, XOR key, and matched string content for each pattern found within a scanned file. 4 releases · 5 other sources · first seen Mar 2014

Shared capability: Threat indicator matching

release

  • Enables of statement usage with at for positional matching v4.3.0 · Mar 2023 · source · release history
  • Adds --print-xor-key (-X) CLI flag to output the XOR key for xored strings in rule matches v4.3.0 · Mar 2023 · source · release history
  • yara and yarac support reading rules from stdin by using - as the file name v3.8.0 · Aug 2018 · source · release history
  • Added recognition of x64 PE file format for rule evaluation. v2.1.0 · Mar 2014 · source · release history

we ran it

  • Two files matched the aws_key rule: app/settings.py (offset 0x12b) and Dockerfile (offset 0x95). Both matches report a string length of 20 characters for the $a pattern. Aug 2026 · the full run
  • Two files matched the rule: Dockerfile (offset 0x95) and app/settings.py (offset 0x12b), each containing the exact AWS key string. Exit status 0 indicates successful execution. Aug 2026 · the full run
  • Two files matched: Dockerfile at offset 0x95 and app/settings.py at offset 0x12b, both showing an XOR key of 0x00 (plaintext, no obfuscation). Aug 2026 · the full run

example

  • Pipe YARA rules directly into the scanner without creating a temporary file. echo 'rule test { strings: $a = "hello" condition: $a }' | yara - /tmp/sample.bin v3.8.0 · Aug 2018 · source
  • Print the matching strings, not just the rule yara -s rule.yar suspicious.bin
Hash-based rule matching shipped Supports computing and using MD4, MD5, SHA1, SHA256, SHA384, and SHA512 hashes of file contents within YARA rules for detection. 2 releases · first seen Nov 2014

Shared capability: Threat indicator matching

release

  • Implements crc32 function in hash module v3.11.0 · Oct 2019 · source · release history
  • Adds hash module supporting MD4, MD5, SHA1, SHA256, SHA384, and SHA512 v3.2.0 · Nov 2014 · source · release history
Iterative hex string matching shipped Allows 'for' statements to iterate over sets of literal strings in hex rules. 1 release · first seen Mar 2023

Shared capability: Threat indicator matching

release

  • Allows for statements to iterate over sets of literal strings in hex rules v4.3.0 · Mar 2023 · source · release history
Multi-threaded scanning shipped Utilizes multiple CPU cores to parallelize file scanning operations, significantly improving performance on large datasets. 1 release · first seen Aug 2014

Shared capability: Threat indicator matching

Also counts toward: Command-line interface

release

  • Command-line scanner (yara) is now multi-threaded, leveraging multiple CPU cores for faster matching. v2.0.0 · Aug 2014 · source · release history
Malware sandbox analysis 2 features Investigation and response since 2014
Sandboxed API integration shipped Provides a sandboxed application programming interface to enable secure execution of YARA rules. 1 release · first seen Oct 2019

Shared capability: Malware sandbox analysis

release

  • Adds sandboxed API (SAPI) integration for secure execution v3.11.0 · Oct 2019 · source · release history
Cuckoo Sandbox integration shipped Provides access to Cuckoo Sandbox malware analysis reports within YARA rules, allowing rules to reference dynamic analysis data. 1 release · first seen Aug 2014

Shared capability: Malware sandbox analysis

release

  • Adds Cuckoo module to access Cuckoo Sandbox report data from rules v3.0.0 · Aug 2014 · source · release history
Memory forensics 1 feature Investigation and response since 2017
Process memory scanning for FreeBSD and OpenBSD shipped Extends live process memory analysis capabilities to FreeBSD and OpenBSD operating systems. 2 releases · first seen Nov 2017

Shared capability: Memory forensics

release

Other / not yet classified 23 features Features we have not matched to a capability yet. A suggested match is marked.
Rule-based file scanning verified suggested Scans files against YARA rules and reports which files match, including match counts and rule names. 5 releases · 7 other sources · first seen Aug 2014

Suggested capability: Threat indicator matching. This is our guess, not confirmed.

release

  • Adds --no-follow-symlinks option on Windows, preventing YARA from following symbolic links during scans. v4.5.5 · Oct 2025 · source · release history
  • Adds --scan-list command-line option to scan multiple files from a list file v4.0.0 · Apr 2020 · source · release history
  • Duplicated string modifiers are now an error (previously ignored or allowed) v3.11.0 · Oct 2019 · source · release history
  • Zero-length files are now treated as normal files v3.1.0 · Aug 2014 · source · release history
  • Adds PE module to parse Portable Executable file structures for rule matching v3.0.0 · Aug 2014 · source · release history

docs

  • Pattern-matching cyber tool for identifying and classifying malware samples using text/binary rules with boolean logic.

we ran it

  • Two files matched the aws_key rule: app/settings.py and Dockerfile. Both are shown with an empty tag list ([]). Exit status 0 confirms the scan completed successfully. Aug 2026 · the full run
  • The rule matched in two files: app/settings.py and Dockerfile. No warnings were raised, so the tool exited 0. The output shows the rule name alongside each matching file path, with no match counts. Aug 2026 · the full run
  • Six files were scanned; two returned a count of 1 — Dockerfile and app/settings.py — while the remaining four scored 0. Exit status 0 indicates the scan completed successfully. Aug 2026 · the full run
  • The rule matched in two files: Dockerfile and app/settings.py. The empty brackets indicate no rule metadata was defined. Exit status 0 confirms successful execution with matches found. Aug 2026 · the full run

example

  • Scan a directory on Windows without following symlinks, avoiding out-of-scope paths or potential symlink loops. yara --no-follow-symlinks rules.yar C:\Targets\ v4.5.5 · Oct 2025 · source
  • Match a ruleset against a directory of files yara rules.yar ./samples
Module API extensions shipped Enables custom modules to declare dictionary objects and accept overloaded functions, enhancing extensibility for complex data sources. 6 releases · first seen Aug 2014

release

  • Adds iterator support for dictionaries and arrays in rules (#1141) v4.0.0 · Apr 2020 · source · release history
  • Allows modules to declare dictionary objects via the new module API v3.2.0 · Nov 2014 · source · release history
  • Allows modules to accept overloaded functions in their API v3.2.0 · Nov 2014 · source · release history
  • module_initialize and module_finalize functions are now required for module implementation v3.1.0 · Aug 2014 · source · release history
  • Modules can now accept functions without arguments v3.1.0 · Aug 2014 · source · release history
  • Module implementations must now define module_initialize and module_finalize functions; previously they were optional. v3.1.0 · Aug 2014 · source · release history
Warning handling configuration shipped Allows control over whether rule evaluation warnings should be treated as fatal errors, providing stricter error checking for rule authors. 3 releases · 2 other sources · first seen Mar 2014

Also counts toward: Command-line interface

release

  • Adds --strict-escape command-line option to raise warnings on unknown escape sequences in rules. v4.5.0 · Feb 2024 · source · release history
  • Adds --fail-on-warnings command-line option v3.6.0 · May 2017 · source · release history
  • match in yara-python now accepts an error_on_warning argument to control warning handling. v2.1.0 · Mar 2014 · source · release history

example

  • Catch typos in regex escape sequences during rule development. yara --strict-escape rules.yar target_file v4.5.0 · Feb 2024 · source
  • Invoke yara-python's match function with error_on_warning=True to treat warnings as fatal errors. yara.match('rules.yar', 'target.bin', error_on_warning=True) v2.1.0 · Mar 2014 · source
Compiled rule support shipped Allows rules to be compiled and saved to files for efficient loading in future executions, reducing rule processing time. 4 releases · 1 other source · first seen Aug 2014

release

  • Updates yara-python load() and save() methods to accept file-like objects v3.4.0 · Jun 2015 · source · release history
  • Adds yr_rules_save_stream and yr_rules_load_stream C API functions for stream-based rule handling v3.4.0 · Jun 2015 · source · release history
  • Adds support for negative integers and floating point numbers in rule expressions v3.3.0 · Feb 2015 · source · release history
  • Compiled rules can now be saved to and loaded from a file, enabling rule caching across executions. v2.0.0 · Aug 2014 · source · release history

example

  • Use the new C API to load rules from a stream instead of a disk file. yr_rules_load_stream(rules_fp, &rules); v3.4.0 · Jun 2015 · source
Enhanced regular expression features shipped suggested Adds word boundary anchors and string comparison operators to YARA rules. 4 releases · first seen Feb 2015

Suggested capability: Threat indicator matching. This is our guess, not confirmed.

release

  • Adds #a in (0..100) syntax for counting string occurrences within a range of offsets v4.2.0 · Mar 2022 · source · release history
  • Adds icontains, endswith, iendswith, startswith, istartswith string comparison operators to YARA rules v4.1.0 · Apr 2021 · source · release history
  • Implements word boundary anchors (\b, \B) in regular expression rules v3.3.0 · Feb 2015 · source · release history
  • Implements greater than (>), less than (<), greater than or equal to (>=), and less than or equal to (<=) operators for strings in YARA rules v3.3.0 · Feb 2015 · source · release history
Inverted match filtering verified Lists files that do not match a rule, allowing users to identify files excluded from a match set. 2 releases · 1 other source · first seen Mar 2022

release

  • Adds none of ($a*) syntactic sugar as equivalent to 0 of ($a) v4.2.0 · Mar 2022 · source · release history
  • Adds abs, count, percentage and mode functions to the math module v4.2.0 · Mar 2022 · source · release history

we ran it

  • Four files are listed — requirements.txt, k8s/deployment.yaml, app/db.py, and package.json — meaning the rule did not match in those four files. Aug 2026 · the full run
Enhanced regex matching modes shipped Extends the `matches` operator with mode flags for case-insensitive comparison and treating newlines as regular characters. 3 releases · first seen Mar 2014

release

  • BUGFIX: matches operator was not matching empty strings (c80cd9d). v4.5.1 · May 2024 · source · release history
  • Support for unbounded jumps in YARA rules. v2.0.0 · Aug 2014 · source · release history
  • matches operator supports single-line (. matches newline) matching for its regexps via new mode flags. v2.1.0 · Mar 2014 · source · release history
Scanner API shipped Provides a programmatic interface for integrating YARA scanning into other applications. 3 releases · first seen Aug 2018

release

  • Implements non-blocking scanning API for asynchronous rule evaluation v4.1.0 · Apr 2021 · source · release history
  • Multiple backward-incompatible API changes are introduced; see Backward-incompatible-changes-in-YARA-4.0-API for details v4.0.0 · Apr 2020 · source · release history
  • Scanner API v3.8.0 · Aug 2018 · source · release history
Recursive filesystem scanning verified suggested Recursively traverses directories to scan all files within a filesystem subtree against a ruleset. 2 other sources · first seen Aug 2026

Suggested capability: Threat indicator matching. This is our guess, not confirmed.

we ran it

  • The rule fired on two files: source-corpus/Dockerfile and source-corpus/app/settings.py. The statistics show 1 rule, 1 string, and 1 AC match entry with an average match-list length of 1.0. Aug 2026 · the full run

example

  • Recursively scan a filesystem yara -r malware.yar /home
Namespace output capability shipped Outputs rule namespaces via a dedicated command-line argument. 2 releases · first seen Feb 2015

Also counts toward: Command-line interface

release

  • BUGFIX: Issue while parsing rich header in some PE files (4793b49). v4.5.1 · May 2024 · source · release history
  • Adds --print-namespace command-line argument to output rule namespaces v3.3.0 · Feb 2015 · source · release history
Short-circuit evaluation support shipped Enables short-circuit evaluation logic within YARA conditions to optimize rule execution. 2 releases · first seen Jun 2015

release

  • Improves performance by avoiding execution of rule conditions that can't match. v4.5.0 · Feb 2024 · source · release history
  • Enables short-circuit evaluation for YARA conditions v3.4.0 · Jun 2015 · source · release history
Unbounded jump support shipped suggested Allows YARA rules to use unbounded jumps (wildcards) between conditions, increasing the flexibility of pattern definitions. 2 releases · first seen Aug 2014

Suggested capability: Static malware analysis. This is our guess, not confirmed.

release

Private strings modifier support shipped Enables the use of private strings modifiers in modular rules to restrict string visibility to specific rules within a module. 2 releases · first seen Oct 2019

release

  • Adds base64, base64wide, and private string modifiers for rule writers v4.0.0 · Apr 2020 · source · release history
  • Implements private strings modifier for modular rules (#1096) v3.11.0 · Oct 2019 · source · release history
XOR string modifier support shipped suggested Enables matching strings that have been XOR-encoded within binary files. 2 releases · first seen Aug 2018

Suggested capability: Static malware analysis. This is our guess, not confirmed.

release

Runtime version querying shipped Provides a C API function to retrieve the major, minor, and micro version of the loaded libyara library at runtime, callable before initialization and with optional null pointers for unused components. 1 release · first seen Oct 2026

release

  • Adds yr_get_version(int* major, int* minor, int* micro) API to report the version of libyara loaded at runtime, allowing any pointer to be NULL and working before yr_initialize.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v4.6.0 · Oct 2026 · source · release history
Scanner performance monitoring shipped Provides callbacks and notifications to alert users when rule evaluation is too slow, aiding in optimization. 1 release · first seen Feb 2024

release

  • New callback message CALLBACK_MSG_TOO_SLOW_SCANNING notifies users about slow rules. v4.5.0 · Feb 2024 · source · release history
Unreferenced string support shipped Allows rules to define strings that are not used in conditions, provided their identifier starts with an underscore. 1 release · first seen Feb 2024

release

  • Unreferenced strings are now allowed if their identifier starts with _. v4.5.0 · Feb 2024 · source · release history
Mathematical conversion functions shipped Provides to_int() and to_string() functions within the math module for data type conversion. 1 release · first seen Mar 2023

release

  • Adds to_int() and to_string() functions to the math module v4.3.0 · Mar 2023 · source · release history
Windows CLI option support shipped Extends command-line options such as --skip-larger to be functional on Windows operating systems. 1 release · first seen Mar 2023

Also counts toward: Command-line interface

release

  • Implements Windows support for the existing --skip-larger command-line option v4.3.0 · Mar 2023 · source · release history
Configurable strings per rule limit shipped Allows users to set a maximum number of strings allowed in a single YARA rule via command-line options. 1 release · first seen Nov 2017

Also counts toward: Command-line interface

release

  • Allow a configurable limit for the number of strings per rule (option --max-strings-per-rule) v3.7.0 · Nov 2017 · source · release history
Unbounded thread limits shipped Removes the previous hard cap on the maximum number of threads, allowing users to arbitrarily increase multithreaded scanning capacity. 1 release · first seen May 2017

release

  • Removes the previous hard cap on the MAX_THREADS limit, allowing it to be arbitrarily increased v3.6.0 · May 2017 · source · release history
Rule match length operator shipped Provides an operator to determine the length of matched strings within YARA rules. 1 release · first seen Sep 2016

release

  • Match length operator for rule writing (http://yara.readthedocs.io/en/v3.5.0/writingrules.html#match-length) v3.5.0 · Sep 2016 · source · release history
Big-endian integer support shipped Adds big-endian variants for integer comparison operators, enabling accurate pattern matching for data formats requiring big-endian byte ordering. 1 release · first seen Nov 2014

release

  • Adds big-endian variants intXX_be and uintXX_be (e.g., uint32_be) for integer comparison functions v3.2.0 · Nov 2014 · 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
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for YARA, 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 YARA 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 →

Coverage

Missing something? Tell us

What YARA connects to, runs on and detects, read from its release notes and docs. So far: 1 new supported platform.

Show

1 change, tracked since Oct 27, 2026.

  • Oct 272026

    new Nine new ELF e_machine architecture constants in the elf module

    Expose nine more `e_machine` values in `elf` module (#2248).

    v4.6.0 Source ↗

How we count

Read from 1 of 21 release notes and docs updates we hold for YARA. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through YARA'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.

Releases

Show
Coverage in all entries

21 entries

  1. October 20261
  2. October 20251
  3. May 20241
  4. February 20241
  5. March 20231
  6. April 20221
  7. March 20221
  8. April 20211
  9. April 20201
  10. October 20191
  11. August 20181
  12. November 20171
  13. May 20171
  14. September 20161
  15. June 20151
  16. February 20151
  17. November 20141
  18. August 20143
  19. March 20141
    Show
    Coverage in all entries

    21 entries

    Project health

    Issue, contributor and maintainer activity in VirusTotal/yara, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 12 ±0 vs prior 12 months
    2. Maintainers 2 +1 joined · −0 left, last 12 months
    3. Bus factor 2 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 59 days first maintainer reply 2.5 days
    6. Open backlog 149 of 1,107 issues ever filed
    1. Issues opened / month 1 · 0 communitymaintainers
    2. Open backlog 149
    3. Contributors / month 1
    4. Commits / month 2
    5. Stars 9,868
    Issue themes, last 12 months
    • bugs 69%
    • other 31%

    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

    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 →