Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 23:45 UTC

mvt-project / mvt

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

PythonCustom license★ 13,102 stars⑂ 1,298 forkssince Jul 2021View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

mvt-project/mvt holds a health index of 93 out of 100, placing it in the Exceptional band. It scores highest on Vitality (90/100) and lowest on AI Readiness (55/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

93
overall / 100
Exceptional

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

93
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 79 is calibrated to 93 on the published index scale (record calibration 2026-08-02).

Ownership

MVTOrganization
599 followers5 public repossince Jul 2021

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPImvt2026.9.7-7812 days agosecuritymobileforensicsmalware

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

90Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
24.2/36Commit cadence — 35/52 weeks with commits
18/18Commit volume — 197 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 23 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year197
human_commit_share0.98
days_since_last_push1
active_weeks_last_year35
How it's scored
27/27Ships releases — 25 releases published
36/36Release recency — latest release 5 days ago
19.8/27Release cadence — a release every ~90.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count25
latest_release_tagv2026.9.14
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases90.5
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

83Excellent · 17% of overall
How it's scored
60/60Stars — 13,102 stars
25/25Forks — 1,298 forks
13.6/15Watchers — 284 watchers
Inputs used
forks1,298
stars13,102
watchers284
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, readthedocs.org, shields.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

74Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.2/22.5Commit distribution — top contributor authored 46% of commits
13.5/13.5Contributor breadth — 59 contributors
10/10OpenSSF Scorecard: Contributors — project has 9 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled59
top_contributor_share0.458
How it's scored
39/42Issue resolution — 93% of issues closed
25.2/30PR acceptance — 393/468 decided PRs merged
8.7/13Newcomer PR acceptance — 4/6 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 3/14 approved changesets -- score normalized to 2
Inputs used
merged_prs393
open_issues28
closed_issues367
prs_merged_7d2
prs_decided_7d2
prs_merged_30d29
prs_decided_30d32
issue_closed_ratio0.929
closed_unmerged_prs75
first_time_authors_30d2
first_time_prs_merged_30d4
first_time_prs_decided_30d6
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
20/25Owner reach — 599 followers of mvt-project
16/25Track record — 5 public repos, account ~5 yr old
Inputs used
followers599
owner_typeOrganization
is_verifiedno
owner_loginmvt-project
public_repos5
account_age_days1,892

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 12 days ago
20/20Version history — 78 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesmvt
ecosystemspypi
any_deprecatedno
min_days_since_publish12

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://mvt.re
10/10Repository description
10/10Topics — 6 topics
0/10Wiki
Inputs used
topicsforensics, mobile, security, android, ios, forensics-tools
has_wikino
homepagehttps://mvt.re
docs_sitehttps://mvt.re
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

68Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 3/14 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 9 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 23 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
2/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages35
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:mvt@2026.9.7 runtime dependency closure — what installing the published package pulls in — 35 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

55Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
35.9/40Legible commit history — 66 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.673
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.02
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/246 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes33,096
source_files_sampled246
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — src/mvt/android/parsers/proto/tombstone.proto
0/20MCP server — not applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalno
api_schema_filessrc/mvt/android/parsers/proto/tombstone.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

13,102GitHub stars
59contributors
197commits, last 12 months
1days since last push
25releases
2bus factor
28open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi download statistics for 'mvt' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced

More detail

Star and fork history 0 ★ / 1,298 ⇿
0Stars
1,298Forks
24Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

2004006008001,0001,2001,4001,298472021-072024-022026-09
Major 0Minor 5Patch 19

Each point covers 5 days.

OpenSSF Scorecard 6.0 / 10
6.0aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-19 23:44 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 3/14 approved changesets -- score normalized to 2
10Contributorsproject has 9 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 23 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 20
RegistryPackageVersion constraintManifest
PyPIclick==8.4.2pyproject.toml
PyPIrich==15.0.0pyproject.toml
PyPItld==0.13.2pyproject.toml
PyPIrequests==2.34.2pyproject.toml
PyPIsimplejson==4.1.1pyproject.toml
PyPIpackaging==26.3pyproject.toml
PyPIappdirs==1.4.4pyproject.toml
PyPIiphone_backup_decrypt==0.10.0pyproject.toml
PyPIpycryptodome>=3.20.0pyproject.toml
PyPIadb-shell==0.4.4pyproject.toml
PyPIlibusb1==3.4.0pyproject.toml
PyPIcryptography==50.0.0pyproject.toml
PyPIPyYAML>=6.0.2pyproject.toml
PyPIpyahocorasick==2.3.1pyproject.toml
PyPIbetterproto2==0.10.0pyproject.toml
PyPIpydantic==2.13.4pyproject.toml
PyPIpydantic-settings==2.15.0pyproject.toml
PyPINSKeyedUnArchiver==1.5.2pyproject.toml
PyPIpython-dateutil==2.9.0.post0pyproject.toml
PyPItzdata==2026.3pyproject.toml
All dependencies 82

Full resolved dependency set from the GitHub dependency graph: 20 direct and 62 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
PyPIadb-shell0.4.4direct
PyPIappdirs1.4.4direct
PyPIbetterproto20.10.0direct
PyPIclick8.4.2direct
PyPIcryptography50.0.0direct
PyPIiphone-backup-decrypt0.10.0direct
PyPIlibusb13.4.0direct
PyPInskeyedunarchiver1.5.2direct
PyPIpackaging26.3direct
PyPIpyahocorasick2.3.1direct
PyPIpycryptodome3.23.0direct
PyPIpydantic2.13.4direct
PyPIpydantic-settings2.15.0direct
PyPIpython-dateutil2.9.0.post0direct
PyPIpyyaml6.0.3direct
PyPIrequests2.34.2direct
PyPIrich15.0.0direct
PyPIsimplejson4.1.1direct
PyPItld0.13.2direct
PyPItzdata2026.3direct
PyPIannotated-types0.8.0indirect
PyPIantlr4-python3-runtime4.13.2indirect
PyPIast-serialize0.8.0indirect
PyPIbabel2.18.0indirect
PyPIbackrefs8.0indirect
PyPIbetterproto2-compiler0.10.1indirect
PyPIcertifi2026.7.22indirect
PyPIcffi2.1.1indirect
PyPIcharset-normalizer3.4.9indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.15.4indirect
PyPIexceptiongroup1.3.1indirect
PyPIghp-import2.1.0indirect
PyPIidna3.18indirect
PyPIiniconfig2.3.0indirect
PyPIjinja23.1.6indirect
PyPIlibrt0.15.0indirect
PyPImarkdown3.10.3indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.3indirect
PyPImdurl0.1.2indirect
PyPImergedeep1.3.4indirect
PyPImkdocs1.6.1indirect
PyPImkdocs-autorefs1.4.4indirect
PyPImkdocs-get-deps0.2.2indirect
PyPImkdocs-material9.7.6indirect
PyPImkdocs-material9.7.7indirect
PyPImkdocs-material-extensions1.3.1indirect
PyPImkdocstrings1.0.4indirect
PyPImkdocstrings1.0.6indirect
PyPImypy2.3.0indirect
PyPImypy-extensions1.1.0indirect
PyPIpaginate0.5.7indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.11.2indirect
PyPIpluggy1.6.0indirect
PyPIpyasn10.6.4indirect
PyPIpycparser3.0indirect
PyPIpydantic-core2.46.4indirect
PyPIpygments2.20.0indirect
PyPIpymdown-extensions11.0.1indirect
PyPIpytest9.1.1indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-github-actions-annotate-failures0.4.2indirect
PyPIpytest-mock3.15.1indirect
PyPIpython-dotenv1.2.2indirect
PyPIpytz2026.3.post1indirect
PyPIpyyaml-env-tag1.1indirect
PyPIrsa4.9.1indirect
PyPIruff0.16.2indirect
PyPIsix1.17.0indirect
PyPIstix23.0.2indirect
PyPIstix2-patterns2.1.2indirect
PyPIstrenum0.4.15indirect
PyPItomli2.4.1indirect
PyPItypes-python-dateutil2.9.0.20260807indirect
PyPItypes-pyyaml6.0.12.20260724indirect
PyPItypes-requests2.33.0.20260712indirect
PyPItyping-extensions4.16.0indirect
PyPItyping-inspection0.4.3indirect
PyPIurllib32.7.0indirect
PyPIwatchdog6.0.0indirect
Dependency advisories 0

Installing pypi:mvt@2026.9.7 pulls in 35 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — PyPI.