Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 00:03 UTC

miracle-wm-org / miracle-wm

A hackable Wayland window manager 🌠

C++GPL-3.0★ 802 stars⑂ 31 forkssince Feb 2023View on GitHub ↗

miracle-wm-org/miracle-wm holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (98/100) and lowest on Security (50/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

83
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.

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

Ownership

miracle-wmOrganization
18 followers8 public repossince Aug 2024

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
crates.iomiracle-plugin0.1.0561485 days ago

Metrics by category

Vitality

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

98Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
32.5/36Commit cadence — 47/52 weeks with commits
18/18Commit volume — 306 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year306
human_commit_share1
days_since_last_push4
active_weeks_last_year47

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 29 releases published
36/36Release recency — latest release 78 days ago
27/27Release cadence — a release every ~33.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count29
latest_release_tagv0.10.1
releases_from_tagsno
days_since_latest_release78
mean_days_between_releases33.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?

56Moderate · 17% of overall
How it's scored
47.1/60Stars — 802 stars
12.3/25Forks — 31 forks
4.7/15Watchers — 8 watchers
Inputs used
forks31
stars802
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
23.4/80Monthly downloads — 56 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesmiracle-plugin
dependents—
ecosystemscrates
total_downloads407
monthly_downloads56
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?

62Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.9/22.5Commit distribution — top contributor authored 96% of commits
13.5/13.5Contributor breadth — 17 contributors
10/10OpenSSF Scorecard: Contributors — project has 25 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled17
top_contributor_share0.961
How it's scored
37.2/42Issue resolution — 89% of issues closed
28.5/30PR acceptance — 574/604 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/30 approved changesets -- score normalized to 0
Inputs used
merged_prs574
open_issues40
closed_issues311
prs_merged_7d1
prs_decided_7d2
prs_merged_30d13
prs_decided_30d15
issue_closed_ratio0.886
closed_unmerged_prs30
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
9.2/25Owner reach — 18 followers of miracle-wm-org
11.1/25Track record — 8 public repos, account ~2 yr old
Inputs used
followers18
owner_typeOrganization
is_verifiedno
owner_loginmiracle-wm-org
public_repos8
account_age_days764

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://miracle-wm.org
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicslinux, wayland, tiling-window-manager, mir, tiling, window-manager, hackable
has_wikiyes
homepagehttps://miracle-wm.org
docs_sitehttps://miracle-wm.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

50Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 22 out of 22 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
0/7.5Code-Review — Found 1/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 25 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 4 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
0/7.5Vulnerabilities — 19 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.8
Excluded from scoring (no data or not applicable): Packaging, 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_packages25
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 crates:miracle-plugin@0.1.0 runtime dependency closure — what installing the published package pulls in — 25 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.

58Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 98 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.98
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — miracle-plugin-rs/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — C++ (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsmiracle-plugin-rs/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — C++ (statically typed)
54/55Manageable file sizes — 5/271 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes217,563
source_files_sampled271
oversized_source_files5

Key facts

802GitHub stars
17contributors
306commits, last 12 months
4days since last push
29releases
1bus factor
40open issues
crates.io, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 31 ⇿
0Stars
31Forks
28Releases

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.

01325383122024-022025-052026-09
Major 0Minor 9Patch 19

Each point covers 3 days.

OpenSSF Scorecard 3.8 / 10
3.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-15 00:02 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests22 out of 22 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/30 approved changesets -- score normalized to 0
10Contributorsproject has 25 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 4 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
0Vulnerabilities19 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
crates.iobitflags2miracle-plugin-rs/Cargo.toml
crates.ioglam0.29miracle-plugin-rs/Cargo.toml
crates.ioserde1miracle-plugin-rs/Cargo.toml
crates.ioserde_json1miracle-plugin-rs/Cargo.toml
All dependencies 40

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

RegistryPackageVersionRelation
crates.iobitflags2.10.0direct
crates.ioglam0.29.3direct
crates.ioserde1.0.228direct
crates.ioserde_json1.0.149direct
crates.ioaho-corasick1.1.4indirect
crates.iobindgen0.71.1indirect
crates.iocexpr0.6.0indirect
crates.iocfg-if1.0.4indirect
crates.ioclang-sys1.8.1indirect
crates.ioeither1.15.0indirect
crates.ioglob0.3.3indirect
crates.ioitertools0.13.0indirect
crates.ioitoa1.0.17indirect
crates.iolibc0.2.180indirect
crates.iolibloading0.8.9indirect
crates.iolog0.4.29indirect
crates.iomemchr2.7.6indirect
crates.iominimal-lexical0.2.1indirect
crates.ionom7.1.3indirect
crates.ioprettyplease0.2.37indirect
crates.ioproc-macro21.0.105indirect
crates.ioquote1.0.43indirect
crates.ioregex1.12.2indirect
crates.ioregex-automata0.4.13indirect
crates.ioregex-syntax0.8.8indirect
crates.iorustc-hash2.1.1indirect
crates.ioserde_core1.0.228indirect
crates.ioserde_derive1.0.228indirect
crates.ioshlex1.3.0indirect
crates.iosyn2.0.114indirect
crates.iounicode-ident1.0.22indirect
crates.iowindows-link0.2.1indirect
crates.iozmij1.0.21indirect
PyPIi3ipc2.2.1indirect
PyPImike—indirect
PyPImkdocs—indirect
PyPImkdocs-material—indirect
PyPIpillow—indirect
PyPIpytest8.3.2indirect
PyPIpytest-asyncio—indirect
Dependency advisories 0

Installing crates:miracle-plugin@0.1.0 pulls in 25 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 — crates.io.