PAGES
← all tools
◆ Digital Forensics & Incident Response

Mobile Verification Toolkit

v2026.10.26 open-source

MVT (Mobile Verification Toolkit) helps with conducting forensics of mobile devices in order to find signs of a potential compromise.

Summary

Mobile Verification Toolkit is an open-source command-line toolkit for forensic analysis of Android and iOS devices, free to use, built to surface traces of compromise such as spyware infections. It is run via the mvt-ios and mvt-android commands, checking device backups and extractions against public indicators of compromiseindicators of compromiseAn indicator of compromise, an observable clue that may point to malicious activity, such as a suspicious file hash or domain. It is evidence to investigate, rather than proof by itself., and its documentation is explicit that it targets technologists and investigators comfortable with digital forensics and command-line tools rather than end users assessing their own phones. It was developed by Amnesty International's Security Lab out of the Pegasus Project, placing it in the mobile forensics and spyware-detection space rather than general device security software. Development is active: first committed in 2021, it has drawn 78 contributors, with 181 commits and 21 releases in the past year, the latest just 23 days ago, including a recent v3 refactor that changed its output format.

MVT (Mobile Verification Toolkit) helps with conducting forensics of mobile devices in order to find signs of a potential compromise.

How Mobile Verification Toolkit helps

Does a backup or extraction from this phone contain traces matched to known spyware campaigns?

checks the device data against public indicators of compromise from Amnesty International and other research groups and flags matches, though a clean result does not rule out compromise since public IOCs alone cannot confirm a device is clean

Which apps on this Android device were removed or quietly downgraded before the investigation started?

analyses battery daily history and uninstalled-app records from Dumpsys data to reconstruct install and removal events outside the current app list

Has this iOS device been talking to domains or IPs already linked to a spyware operator?

runs URL and IP indicator checks concurrently against the extracted data and reports each match against the loaded indicator set

Can this Android device be trusted to have an intact, unmodified system given root access or tampered packages?

inspects root-related binaries, APK certificate hashes, and package data to surface signs of rooting or tampered applications

What happened on this device around the time of a suspected compromise?

combines timezone info, file modification events, and shutdown or crash logs into a timeline of device activity for the investigator to review

Is the alert a device generates a hard yes/no or does it need my judgement?

reports findings through a multi-level alert system rather than a binary detected/not-detected result, so heuristic matches are distinguished from confirmed indicator hits

all 24 features, with the evidence for each →

Languages

Not documented

Features

24 capabilities across 3 capability groups · 6 backed by code, an API document or a real run

Built from Mobile Verification Toolkit'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 →

  • Mobile Verification Toolkit covers 3 of the 8 investigation and response capabilities we track.

What Mobile Verification Toolkit offers you

  • Command-line interface6
  • Plugin system3
  • JSON data export1
  • Plugin API support1
  • Python scripting support1
  • Scripting language support1
Threat indicator matching 3 features Investigation and response since 2024
IOC matching verified Compares device artifacts against a set of indicators of compromise, running URL and package-based checks to identify matches. 9 releases · 3 other sources · first seen Jan 2025

Shared capability: Threat indicator matching

release 9 total

  • Parses dumpsys settings output as per-record results in Android analysis, capturing multi-line values and metadata that per-line regex previously truncated or dropped. v2026.9.7 · Sep 2026 · source · release history
  • Parallelizes URL indicator checks for faster IOC scanning. v2026.7.29 · Jul 2026 · source · release history
  • Matches Android receiver indicators by package ID. v2026.7.29 · Jul 2026 · source · release history
  • Extends IoC matching to check broadcast receiver names. v2026.4.28 · Apr 2026 · source · release history
  • Extends VirusTotal checks to work with androidqf extractions in addition to ADB. v2.7.0 · Dec 2025 · source · release history
  • Adds additional Android security warnings to surface more suspicious indicators during device checks. v2.6.1 · Dec 2025 · source · release history

docs

  • request. URL checks are deduplicated and run concurrently, with at most 20 requests in progress at a time. Redirects within an individual URL chain are still followed sequentially. The following environment variables control these requests: docs update · Jul 2026 · source
  • Forensic cyber tool that gathers traces from Android and iOS devices to identify potential compromise by spyware such as Pegasus.

command line

External threat intelligence lookup shipped Sends forensic analysis results to VirusTotal for external threat matching via a configurable CLI flag. 2 releases · 1 other source · first seen Apr 2024

Shared capability: Threat indicator matching

Also counts toward: Command-line interface

release

  • The VirusTotal integration is now triggered with -V instead of --virustotal; using the old long flag will fail. v2.5.1 · Apr 2024 · source · release history
  • Shortens the VirusTotal integration flag from --virustotal to -V for quicker CLI access. v2.5.1 · Apr 2024 · source · release history

example

  • Run an iOS forensic analysis and send results to VirusTotal using the new short flag. mvt-ios check-bootstash --bootstash <path> -V v2.5.1 · Apr 2024 · source
STIX2 indicator support shipped Loads STIX2 indicators from directories to match against forensic artifacts during analysis. 2 releases · first seen Jan 2025

Shared capability: Threat indicator matching

release

  • STIX2 indicator loading via MVT_STIX2 environment variable now recursively searches directories, not just individual files. v2.6.0 · Jan 2025 · source · release history
  • Improved STIX2 indicator support with broader indicator-type coverage and expanded test coverage. v2.6.0 · Jan 2025 · source · release history
Disk and filesystem forensics 2 features Investigation and response since 2025
iOS backup and filesystem analysis shipped Analyses iOS backups and filesystem extractions, including browsing history and shutdown logs, to surface forensic evidence. 9 releases · 5 other sources · first seen Dec 2025

Shared capability: Disk and filesystem forensics

release 9 total

  • Replaces the unmaintained iOSbackup dependency with iphone_backup_decrypt for iOS backup decryption, fixing decrypted-file truncation caused by inaccurate sizes in backup metadata. v2026.9.7 · Sep 2026 · source · release history
  • Adds --jobs option to mvt-ios decrypt-backup to control the number of concurrent decryption workers (integer, 1 to MAX_DECRYPT_WORKERS, defaults to DEFAULT_DECRYPT_WORKERS). v2026.9.7 · Sep 2026 · source · release history
  • Adds a WhatsApp contacts forensic module. v2026.9.1 · Sep 2026 · source · release history
  • Add WhatsApp contacts module using InteractionC and WhatsAppDB databases on iOS v2026.9.1 · Sep 2026 · source · release history
  • Supports rotated iOS shutdown logs. v2026.7.29 · Jul 2026 · source · release history
  • Enables scanning Safari profile databases (com.apple.Safari*) in iOS backups for history and browser state v2026.7.29 · Jul 2026 · source · release history

docs

  • Backup with pymobiledevice3 After installing pymobiledevice3 and pairing your device, you can generate an iTunes-compatible backup using its backup2 commands. Enable backup encryption We recommend encrypted backups because they contain more data than unencrypted backups. seen Oct 2026 · source
  • Using Docker simplifies running MVT with its dependencies readily installed. Note that this requires a Linux host, as Docker for Windows and Mac The main and iOS Docker images include pymobiledevice3 for creating iOS backups . You do not need to install it separately on the host. seen Oct 2026 · source
  • Install pymobiledevice3 Before acquiring data from an iOS device, we recommend installing pymobiledevice3 . It provides command-line tools for generating iTunes-compatible backups and extracting crash logs. seen Oct 2026 · source
  • An incomplete backup still lists in its manifest the files it failed to acquire. Those records carry a missing: true field, and the module reports how many of them it found. seen Oct 2026 · source

example

  • Decrypt a large encrypted iOS backup faster by parallelising file decryption across multiple workers. mvt-ios decrypt-backup --jobs 8 -p <password> -d /tmp/decrypted /path/to/backup v2026.9.7 · Sep 2026 · source
SQLite recovery shipped Automatically attempts to recover locked or open SQLite databases during artifact analysis. 1 release · first seen Jan 2025

Shared capability: Disk and filesystem forensics

release

  • SQLite database recovery now attempted automatically when a DB is found locked or open. v2.6.0 · Jan 2025 · source · release history
Forensic timeline analysis 1 feature Investigation and response since 2026
Timezone-aware timestamping shipped Attaches timezone provenance information to file timestamps in the analysis output. 1 release · first seen Sep 2026

Shared capability: Forensic timeline analysis

release

  • Adds timezone provenance to file timestamps in analysis output. v2026.9.1 · Sep 2026 · source · release history
Other / not yet classified 18 features Features we have not matched to a capability yet. A suggested match is marked.
Android bugreport analysis shipped Analyses Android bugreport archives, including OEM wrapper zips, extracting system properties, dump states, and accessibility service data, and raising alerts on suspicious findings. 14 releases · 1 other source · first seen Jan 2025

release 14 total

  • Recovers properties lost when a section timing line was misidentified as a section boundary in bugreport parsing, restoring full SYSTEM PROPERTIES output on affected archives. v2026.9.28 · Sep 2026 · source · release history
  • Carries the accessibility service count from dump states, surfacing the count of installed accessibility services during a check-bugreport run. v2026.9.28 · Sep 2026 · source · release history
  • Extends check-bugreport to descend into OEM wrapper .zip archives when the outer archive lacks a dumpstate entry point, automatically finding and using the nested bugreport.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v2026.9.28 · Sep 2026 · source · release history
  • Extends check-bugreport to descend into OEM wrapper archives, enabling analysis of bug reports that wrap logs inside a vendor-specific outer archive. v2026.9.28 · Sep 2026 · source · release history
  • Surfaces accessibility service counts (installedServiceCount=N) per user in dumpsys accessibility analysis, raising a LOW alert when services are listed in the count but not named in the dump. v2026.9.28 · Sep 2026 · source · release history
  • Adds --timezone/-t option to mvt-android check-bugreport, accepting an IANA timezone name (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Europe/Paris), so bugreport file timestamps are interpreted in the device's wall-clock zone rather than the analysing machine's timezone; falls back to reading persist.sys.timezone from… v2026.9.14 · Sep 2026 · source · release history

example

  • Analyse a bugreport from a device known to be in a specific timezone when persist.sys.timezone is absent or unreliable in the archive. mvt-android check-bugreport --timezone 'America/New_York' -o ./results/ bugreport-2026-09-14.zip v2026.9.14 · Sep 2026 · source
iOS sysdiagnose checking verified suggested Prepares and analyses iOS sysdiagnose archives to detect anomalies using modular analysis steps. 4 releases · 6 other sources · first seen Jul 2026

Suggested capability: Disk and filesystem forensics. This is our guess, not confirmed.

Also counts toward: Command-line interface

release

  • Reports unreadable or truncated sysdiagnose archives (catching tarfile.ReadError, EOFError, zlib.error, and OSError) with a critical-level log message and a clean exit code 1 instead of a silent Aborted!. v2026.9.14 · Sep 2026 · source · release history
  • Adds SysdiagnoseInfo module to the check-sysdiagnose command v2026.9.7 · Sep 2026 · source · release history
  • Adds a SysdiagnoseInfo module to check-sysdiagnose, extending IOC scanning to sysdiagnose archives. v2026.9.7 · Sep 2026 · source · release history
  • Adds iOS sysdiagnose checking support. v2026.7.29 · Jul 2026 · source · release history

docs

  • check-sysdiagnose sysdiagnose_info.json SysdiagnoseInfo module. The module extracts details about the device and the sysdiagnose itself: the product type and model, iOS version and build, serial number, IMEI, MEID and UDID from the remotectl dump state and the mobile activation request, the Apple account name and… seen Sep 2026 · source
  • analyzes an iOS sysdiagnose archive. MVT's own SysdiagnoseInfo module extracts details about the device and the archive (see sysdiagnose_info.json ); the checks come from the modules of the installed declare support for the command. seen Sep 2026 · source
  • custom MVT modules. MVT does not include built-in sysdiagnose modules. The command runs the modules of the installed plugin packages which declare support for it. Install at least one such package first. to display the eligible modules without running them. mvt.plugin , see Writing a module . seen Aug 2026 · source
  • to declare the platform/command pairs a module supports. Empty means the module will not run and MVT logs a warning. This explicit declaration is required for every command. Supported pairs are: check-sysdiagnose seen Jul 2026 · source
  • Check an iOS Sysdiagnose mvt-ios check-sysdiagnose prepares an iOS sysdiagnose archive for analysis by custom MVT modules. MVT does not include built-in sysdiagnose modules. You must load at least one custom module that explicitly supports this command. docs update · Jul 2026 · source

command line

Shell completion verified Installs tab-completion for MVT commands in common shells, making it faster to navigate available options. 3 releases · 7 other sources · first seen Jul 2026

Also counts toward: Command-line interface

release

  • Adds mvt completion to generate shell completion scripts for Bash, Zsh, and Fish across mvt, mvt-ios, and mvt-android; pass the shell name (e.g. mvt completion bash) to emit the script directly, and --install to write it. v2026.9.1 · Sep 2026 · source · release history
  • Adds shell completion command for Bash, Zsh, and Fish via mvt-ios completion and mvt-android completion. v2026.7.29 · Jul 2026 · source · release history
  • Adds shell-completion subcommand to generate autocompletion scripts for the CLI v2026.7.29 · Jul 2026 · source · release history

docs

  • mvt completion generates one script which covers mvt , and . The following describes how to generate that script and add it to your shell configuration. docs update · Aug 2026 · source

command line

example

  • Generate and install shell completion for Bash so all three MVT commands are tab-completable in your daily workflow. mvt completion bash --install v2026.9.1 · Sep 2026 · source
  • Install shell completion for your shell so mvt-ios and mvt-android arguments tab-complete in your terminal. mvt-ios completion bash --install mvt-android completion zsh --install v2026.7.29 · Jul 2026 · source
  • Generate Bash completion script mvt completion bash
  • Show shell completion setup instructions mvt completion
Android forensic artifact checking shipped suggested Inspects AndroidQF backups and other Android artifacts for signs of compromise, tolerating malformed data. 8 releases · 1 other source · first seen Jan 2025

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

release 8 total

  • AndroidQF runs no longer abort when encountering an encrypted backup.ab; the encrypted backup is skipped and analysis continues. v2026.9.1 · Sep 2026 · source · release history
  • Alerts on unexpected trusted ADB keys in AndroidQF acquisitions: raises LOW-severity alerts for malformed keys, keys from a different host, trusted keys when no acquisition host key is present, and informational alerts when the acquisition host key was last connected more than one day before collection. v2026.9.1 · Sep 2026 · source · release history
  • Handles malformed AndroidQF backups gracefully instead of crashing. v2026.7.29 · Jul 2026 · source · release history
  • Adds Android intrusion log checks, parsing Intrusion Logging data available in Android Advanced Protection Mode to surface forensic indicators. v2026.5.12 · May 2026 · source · release history
  • Adds root_binaries module for androidqf to detect root-related binaries on Android devices. v2.7.0 · Dec 2025 · source · release history
  • Adds mounts module for androidqf to inspect mounted filesystems on Android devices. v2.7.0 · Dec 2025 · source · release history

example

  • Run an AndroidQF check with a custom detection module to extend MVT's analysis beyond built-in modules. mvt-android check-androidqf --load-module /path/to/my_custom_module.py <target> v2026.7.29 · Jul 2026 · source
Custom CLI command loading verified Adds user-defined top-level commands to the MVT CLI, enabling new operations beyond the standard check routines. 2 releases · 4 other sources · first seen Apr 2026

Also counts toward: Command-line interface, Plugin API support, Plugin system

release

  • Adds a plugin system: third-party packages can register forensic modules and top-level CLI commands via Python entry points; mvt plugins lists installed plugins and checks for updates. v2026.9.1 · Sep 2026 · source · release history
  • Replaces binary detected/not-detected alerting with a multi-level alert system, enabling heuristic detections and richer JSON output for downstream tooling. v2026.4.28 · Apr 2026 · source · release history

docs

  • Custom CLI Commands MVT can load additional top-level commands into mvt , mvt-ios and mvt-android . A command package chooses which of the three each of its commands is added to. docs update · Aug 2026 · source
  • Plugin Configuration Plugin packages that add custom CLI commands or modules often need to store their own settings, such as an API key, a server URL or the timestamp of the last synchronization. docs update · Aug 2026 · source
  • Custom CLI Commands MVT can load additional top-level commands into mvt-ios and mvt-android . Custom commands are different from custom forensic modules : commands add new CLI operations, while modules add analysis steps to existing check-* commands. docs update · Aug 2026 · source

command line

  • --load-command — Load a custom CLI command from a Python file or folder (can be invoked multiple times) v2026.9.1 · Sep 2026 · command-line history
Custom module loading verified Loads user-supplied Python modules at runtime so analysts can add custom analysis steps alongside the built-in ones. 4 releases · 1 other source · first seen Jul 2026

Also counts toward: Command-line interface, Plugin system, Python scripting support, Scripting language support

release

  • Modules with unavailable dependencies are now skipped instead of aborting the run. v2026.9.1 · Sep 2026 · source · release history
  • Allows custom modules to replace built-in MVT modules via the plugin system. v2026.9.1 · Sep 2026 · source · release history
  • Adds support for --module-path (configurable via MODULE_PATH env var) to load custom modules dynamically v2026.7.29 · Jul 2026 · source · release history
  • Supports loading custom Python analysis modules with --load-module PATH or the MVT_CUSTOM_MODULES environment variable. v2026.7.29 · Jul 2026 · source · release history

command line

Python runtime requirement shipped Requires Python 3.10 or newer to run. 1 release · 1 other source · first seen Oct 2026

release

  • Adds Python 3.15 support, extending the supported runtime range alongside Python 3.10–3.14.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v2026.10.26 · Oct 2026 · source · release history

docs

  • Before proceeding, please note that MVT requires Python 3.10 or newer to run. While it should be available on most operating systems, please make sure of that before proceeding. seen Oct 2026 · source
Dependency-aware module execution shipped Executes analysis modules in dependency order so that each module runs only after the modules it relies on have completed. 1 release · 1 other source · first seen Jul 2026

release

  • Adds dependency-aware module execution, allowing modules to declare prerequisites and run in stable topological order. v2026.7.29 · Jul 2026 · source · release history

docs

  • Selecting a single module also runs its transitive dependencies. A module can only depend on modules the command it runs in also has. docs update · Aug 2026 · source
Multi-level alert system shipped Replaces binary detection alerts with a multi-level heuristic system and richer JSON output for downstream tooling. 2 releases · first seen Apr 2026

Also counts toward: JSON data export

release

  • This release is described as a major v3 refactor; the README explicitly warns about v3 breaking changes — existing integrations that parse MVT JSON output or rely on the binary detected/not-detected alert structure will need to be updated for the new multi-level alert format. v2026.4.28 · Apr 2026 · source · release history
  • Replaces binary detected/not-detected alerting with a multi-level alert system, enabling heuristic detections and richer JSON output for downstream tooling. v2026.4.28 · Apr 2026 · source · release history
Debug logging configuration shipped Provides configurable CLI flags to enable and control USBmuxd debug logging verbosity during device connections. 1 release · 1 other source · first seen Apr 2024

release

  • Changes the usbmuxd debug option short flag from -d to -v. v2.5.1 · Apr 2024 · source · release history

example

  • Enable usbmuxd debug logging with the new short flag. mvt-ios check-finder --debug-mode -v v2.5.1 · Apr 2024 · source
Plugin management shipped Provides subcommands to check installed plugin versions, manage plugins, and discover available updates via PyPI. 1 other source · first seen Sep 2026

Also counts toward: Command-line interface, Plugin system

example

  • Check what plugins are installed and whether any have updates available, before running an analysis. mvt plugins v2026.9.1 · Sep 2026 · source
Parallel execution documented Executes analysis tasks in parallel using a configurable job count to speed up processing. 1 other source · first seen Aug 2026

docs

  • Installed module packages Python packages can register modules so they load automatically in every module-running command, without or . Register an entry point in the mvt.modules group in the package's pyproject.toml [project.entry-points. docs update · Aug 2026 · source
Delayed execution verified Delays the start of an analysis run by a configurable amount of time, allowing the user to prepare or schedule execution. 1 other source · first seen Jul 2026

command line

ADB keystore parsing shipped suggested Parses ADB keystores in XML format to capture additional credential and key artifacts. 1 release · first seen Dec 2025

Suggested capability: Disk and filesystem forensics. This is our guess, not confirmed.

release

  • Adds support for parsing ADB keystore in XML format, expanding credential and key artifact coverage. v2.6.1 · Dec 2025 · source · release history
Device model support shipped Expands supported device hardware models for accurate forensic context and compatibility. 1 release · first seen Dec 2025

release

iOS version support shipped Updates supported iOS versions to include the latest releases for forensic analysis. 1 release · first seen Dec 2025

release

  • Updates known iOS versions to include iOS 18.6.1 and 18.6.2. v2.7.0 · Dec 2025 · source · release history
Update check configuration shipped Provides user control over automatic update checks, allowing them to be disabled. 1 release · first seen Dec 2025

release

Docker build optimization shipped Reduces Docker image size through multistage builds and OS-specific image separation. 1 release · first seen Jan 2025

release

  • Docker image now built with multistage builds and separate OS-specific images, reducing image size. v2.6.0 · Jan 2025 · 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 Mobile Verification Toolkit, 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 Mobile Verification Toolkit 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 →

Releases

Show

24 entries

  1. October 20261
  2. September 20264
  3. August 20269
  4. July 20263
  5. May 20262
  6. April 20261
  7. December 20252
  8. January 20251
  9. April 20241
    Show

    24 entries

    Project health

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

    1. Contributors 16 +4 vs prior 12 months
    2. Maintainers 2 +1 joined · −2 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 64% of issues opened, last 12 months
    5. Median time to close 220 days first maintainer reply 5.4 hours
    6. Open backlog 25 of 390 issues ever filed
    1. Issues opened / month 1 · 1 communitymaintainers
    2. Open backlog 25
    3. Contributors / month 5
    4. Commits / month 20
    5. Stars 13,134
    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.

    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.

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