Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 05:14 UTC

AFLplusplus / qemuafl

This fork of QEMU enables fuzzing userspace ELF binaries under AFL++.

C · C++Custom license★ 84 stars⑂ 55 forkssince Jul 2020forkView on GitHub ↗
KindDesktop applicationhow this is determined

AFLplusplus/qemuafl holds a health index of 53 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (89/100) and lowest on Security (31/100). It was last updated 42 days ago. 10 contributors account for most of its recent work.

53
overall / 100
Moderate

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.

53
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 52 is calibrated to 53 on the published index scale (record calibration 2026-08-02).

Ownership

Advanced Fuzzing League ++Organization · verified domain
437 followers35 public repossince Mar 2020

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

Metrics by category

Vitality

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

46Weak · 21% of overall
How it's scored
18/36Push recencylast push 42 days ago
10.4/36Commit cadence15/52 weeks with commits
14.5/18Commit volume40 commits in the last year
2/10OpenSSF Scorecard: Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year40
human_commit_share1
days_since_last_push42
active_weeks_last_year15
How it's scored
16.2/27Ships releases97 version tags (no GitHub releases)
0/36Release recencylatest release 2,276 days ago
27/27Release cadencea release every ~22.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count97
latest_release_tagv4.2.1
releases_from_tagsyes
days_since_latest_release2,276
mean_days_between_releases22.8
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?

34At Risk · 17% of overall
How it's scored
31.1/60Stars84 stars
14.4/25Forks55 forks
2.7/15Watchers4 watchers
Inputs used
forks55
stars84
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
16.9/22.5Licenselicense file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

89Excellent · 23% of overall
How it's scored
54/54Bus factor10 contributor(s) cover half of all commits
19.4/22.5Commit distributiontop contributor authored 14% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 26 contributing companies or organizations
Inputs used
bus_factor10
contributors_sampled100
top_contributor_share0.139
How it's scored
30.8/42Issue resolution73% of issues closed
27.9/30PR acceptance53/57 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 9/14 approved changesets -- score normalized to 6
Inputs used
merged_prs53
open_issues8
closed_issues22
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.733
closed_unmerged_prs4
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
19/25Owner reach437 followers of AFLplusplus
23.3/25Track record35 public repos, account ~6 yr old
Inputs used
followers437
owner_typeOrganization
is_verifiedyes
owner_loginAFLplusplus
public_repos35
account_age_days2,375

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config.flake8
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 10 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://aflplus.plus
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://aflplus.plus
docs_sitehttps://aflplus.plus
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

31At Risk · 16% of overall
How it's scored
0/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 10 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 9/14 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 26 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
5/5Fuzzingproject is fuzzed
2.2/2.5Licenselicense file detected
1.5/7.5Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate3.1
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.

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.

61Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
27.7/40Legible commit history52 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.52
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile, contrib/plugins/Makefile, pc-bios/Makefile, pc-bios/optionrom/Makefile, pc-bios/s390-ccw/Makefile, roms/Makefile, tests/migration/Makefile, tests/migration/aarch64/Makefile, tests/migration/i386/Makefile, tests/migration/s390x/Makefile, tests/multiboot/Makefile, tests/qemu-iotests/Makefile, tests/tcg/lm32/Makefile, tests/tcg/mips/user/ase/dsp/Makefile, tests/tcg/mips/user/isa/r5900/Makefile, tests/tcg/openrisc/Makefile, tests/uefi-test-tools/Makefile, ui/icons/Makefile
22/22Automated tests
11/11Lint / format config.flake8
11/11Static type checkingpython/mypy.ini, scripts/qapi/mypy.ini
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile, contrib/plugins/Makefile, pc-bios/Makefile, pc-bios/optionrom/Makefile, pc-bios/s390-ccw/Makefile, roms/Makefile, tests/migration/Makefile, tests/migration/aarch64/Makefile, tests/migration/i386/Makefile, tests/migration/s390x/Makefile, tests/multiboot/Makefile, tests/qemu-iotests/Makefile, tests/tcg/lm32/Makefile, tests/tcg/mips/user/ase/dsp/Makefile, tests/tcg/mips/user/isa/r5900/Makefile, tests/tcg/openrisc/Makefile, tests/uefi-test-tools/Makefile, ui/icons/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configspython/mypy.ini, scripts/qapi/mypy.ini
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeC (statically typed)
53/55Manageable file sizes189/5,304 source files over 60KB
Inputs used
primary_languageC
largest_source_bytes934,722
source_files_sampled5,304
oversized_source_files189

Key facts

84GitHub stars
100contributors
40commits, last 12 months
42days since last push
97releases
10bus factor
8open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Community profile unavailable
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 55 ⇿
0Stars
55Forks

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.

01020304050605522020-092023-072026-05

Each point covers 6 days.

OpenSSF Scorecard 3.1 / 10
3.1aggregate

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 05:13 UTC

0Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 10 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 9/14 approved changesets -- score normalized to 6
10Contributorsproject has 26 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
10Fuzzingproject is fuzzed
9Licenselicense file detected
2Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.