Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 01:27 UTC

vladbat00 / bevy_egui

This crate provides an Egui integration for the Bevy game engine. 🇺🇦 Please support the Ukrainian army: https://savelife.in.ua/en/

RustMIT★ 1,413 stars⑂ 336 forkssince Jan 2021View on GitHub ↗
KindLibraryDesktop applicationhow this is determined

vladbat00/bevy_egui holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (80/100) and lowest on AI Readiness (53/100). It was last updated 10 days ago. A single contributor accounts for most of its recent work.

80
overall / 100
Excellent

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.

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

Ownership

Vladyslav BatyrenkoPersonal account
183 followers98 public repossince Dec 2012

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
crates.iobevy_egui0.42.0135,6097625 days ago

Metrics by category

Vitality

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

80Excellent · 21% of overall
How it's scored
28.8/36Push recency — last push 10 days ago
11.8/36Commit cadence — 17/52 weeks with commits
16.3/18Commit volume — 64 commits in the last year
10/10OpenSSF Scorecard: Maintained — 16 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year64
human_commit_share0.96
days_since_last_push10
active_weeks_last_year17

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 52 releases published
36/36Release recency — latest release 25 days ago
27/27Release cadence — a release every ~34.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count52
latest_release_tagv0.42.0
releases_from_tagsno
days_since_latest_release25
mean_days_between_releases34.1
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?

70Good · 17% of overall
How it's scored
51.1/60Stars — 1,413 stars
21/25Forks — 336 forks
5.8/15Watchers — 12 watchers
Inputs used
forks336
stars1,413
watchers12
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
68.4/80Monthly downloads — 135,609 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesbevy_egui
dependents—
ecosystemscrates
total_downloads2,514,968
monthly_downloads135,609
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

67Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.1/22.5Commit distribution — top contributor authored 64% of commits
13.5/13.5Contributor breadth — 83 contributors
10/10OpenSSF Scorecard: Contributors — project has 19 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled83
top_contributor_share0.64
How it's scored
35.3/42Issue resolution — 84% of issues closed
19.9/30PR acceptance — 184/278 decided PRs merged
13/13Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 10/28 approved changesets -- score normalized to 3
Inputs used
merged_prs184
open_issues34
closed_issues180
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.841
closed_unmerged_prs94
first_time_authors_30d2
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
16.3/25Owner reach — 183 followers of vladbat00
25/25Track record — 98 public repos, account ~13 yr old
Inputs used
followers183
owner_typeUser
is_verified—
owner_loginvladbat00
public_repos98
account_age_days5,030
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on crates
35/35Publish recency — latest publish 25 days ago
20/20Version history — 76 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesbevy_egui
ecosystemscrates
any_deprecatedno
min_days_since_publish25

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
16/16Linter config — .rustfmt.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 13 out of 15 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/bevy_egui
10/10Repository description
10/10Topics — 3 topics
10/10Wiki
Inputs used
topicsbevy, egui, bevy-engine
has_wikiyes
homepage—
docs_sitehttps://docs.rs/bevy_egui
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

58Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2/2.5CI-Tests — 13 out of 15 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 10/28 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 19 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.5/2.5License — license file detected
7.5/7.5Maintained — 16 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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
0/5Security-Policy — security policy file not 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_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. 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.

53Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
21.1/40Legible commit history — 38 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.396
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Cargo.toml (toolchain convention, no task runner)
0/22Automated tests
11/11Lint / format config — .rustfmt.toml
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 4 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml
dependency_bot_commit_share0.04
How it's scored
45/45Type-checkable code — Rust (statically typed)
50/55Manageable file sizes — 2/22 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes76,113
source_files_sampled22
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

1,413GitHub stars
83contributors
64commits, last 12 months
10days since last push
52releases
1bus factor
34open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 336 ⇿
0Stars
336Forks
51Releases

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.

012525037530992021-012023-102026-08
Major 0Minor 30Patch 18

Each point covers 6 days.

OpenSSF Scorecard 5.8 / 10
5.8aggregate

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-11 01:27 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
8CI-Tests13 out of 15 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 10/28 approved changesets -- score normalized to 3
10Contributorsproject has 19 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained16 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
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
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 31
RegistryPackageVersion constraintManifest
crates.ioegui0.36Cargo.toml
crates.iobevy_a11y0.19Cargo.toml
crates.iobevy_app0.19Cargo.toml
crates.iobevy_camera0.19Cargo.toml
crates.iobevy_derive0.19Cargo.toml
crates.iobevy_ecs0.19Cargo.toml
crates.iobevy_input0.19Cargo.toml
crates.iobevy_log0.19Cargo.toml
crates.iobevy_math0.19Cargo.toml
crates.iobevy_platform0.19Cargo.toml
crates.iobevy_reflect0.19Cargo.toml
crates.iobevy_time0.19Cargo.toml
crates.iobevy_window0.19Cargo.toml
crates.iobevy_winit0.19Cargo.toml
crates.iobevy_utils0.19Cargo.toml
crates.iowinit0.30Cargo.toml
crates.iowebbrowser1.0.1Cargo.toml
crates.iobytemuck1Cargo.toml
crates.iobevy_asset0.19Cargo.toml
crates.iobevy_core_pipeline0.19Cargo.toml
crates.iobevy_image0.19Cargo.toml
crates.iobevy_mesh0.19Cargo.toml
crates.iobevy_render0.19Cargo.toml
crates.iobevy_color0.19Cargo.toml
crates.iobevy_shader0.19Cargo.toml
crates.iobevy_transform0.19Cargo.toml
crates.ioencase0.12Cargo.toml
crates.ioitertools0.15Cargo.toml
crates.iowgpu-types29.0.3Cargo.toml
crates.iobevy_ui_render0.19Cargo.toml
crates.iobevy_picking0.19Cargo.toml
All dependencies 44

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

RegistryPackageVersionRelation
crates.iobevy_a11y—direct
crates.iobevy_app—direct
crates.iobevy_asset—direct
crates.iobevy_camera—direct
crates.iobevy_color—direct
crates.iobevy_core_pipeline—direct
crates.iobevy_derive—direct
crates.iobevy_ecs—direct
crates.iobevy_image—direct
crates.iobevy_input—direct
crates.iobevy_log—direct
crates.iobevy_math—direct
crates.iobevy_mesh—direct
crates.iobevy_picking—direct
crates.iobevy_platform—direct
crates.iobevy_reflect—direct
crates.iobevy_render—direct
crates.iobevy_shader—direct
crates.iobevy_time—direct
crates.iobevy_transform—direct
crates.iobevy_ui_render—direct
crates.iobevy_utils—direct
crates.iobevy_window—direct
crates.iobevy_winit—direct
crates.iobytemuck—direct
crates.ioegui—direct
crates.ioencase—direct
crates.ioitertools—direct
crates.iowebbrowser—direct
crates.iowgpu-types—direct
crates.iowinit—direct
crates.ioarboard—indirect
crates.iobevy—indirect
crates.iocrossbeam-channel—indirect
crates.iogetrandom—indirect
crates.ioimage—indirect
crates.iojs-sys—indirect
crates.iorfd—indirect
crates.iosmithay-clipboard—indirect
crates.iothread_local—indirect
crates.ioversion-sync—indirect
crates.iowasm-bindgen—indirect
crates.iowasm-bindgen-futures—indirect
crates.ioweb-sys—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 — crates.io.