Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 00:34 UTC

NiiightmareXD / windows-capture

Fastest Windows Screen Capture Library For Rust And Python 🔥

RustMIT★ 506 stars⑂ 81 forkssince Sep 2023View on GitHub ↗
KindLibraryDesktop applicationhow this is determined

NiiightmareXD/windows-capture holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (66/100) and lowest on Vitality (37/100). It was last updated 10 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

NiiightmareXDPersonal account
29 followers16 public repossince Sep 2021

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 publishTags
crates.iowindows-capture2.0.1324,4116240 days agocapturegraphicsscreenscreenshotwindowsguimultimediaapi-bindings
PyPIwindows-capture2.0.1-2540 days agoscreencapturescreenshotgraphicswindows

Metrics by category

Vitality

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

37Weak · 21% of overall
How it's scored
28.8/36Push recency — last push 10 days ago
7.6/36Commit cadence — 11/52 weeks with commits
14.2/18Commit volume — 37 commits in the last year
10/10OpenSSF Scorecard: Maintained — 7 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year37
human_commit_share1
days_since_last_push10
active_weeks_last_year11
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

66Good · 17% of overall
How it's scored
43.9/60Stars — 506 stars
15.9/25Forks — 81 forks
5.6/15Watchers — 11 watchers
Inputs used
forks81
stars506
watchers11
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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
73.5/80Monthly downloads — 324,411 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageswindows-capture
dependents—
ecosystemscrates
total_downloads1,368,992
monthly_downloads324,411
unverified_packages_excludedwindows-capture
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.1/22.5Commit distribution — top contributor authored 82% of commits
13.5/13.5Contributor breadth — 18 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled18
top_contributor_share0.817
How it's scored
35.1/42Issue resolution — 84% of issues closed
9.9/30PR acceptance — 36/109 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 3/27 approved changesets -- score normalized to 1
Inputs used
merged_prs36
open_issues15
closed_issues76
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.835
closed_unmerged_prs73
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
10.6/25Owner reach — 29 followers of NiiightmareXD
19/25Track record — 16 public repos, account ~5 yr old
Inputs used
followers29
owner_typeUser
is_verified—
owner_loginNiiightmareXD
public_repos16
account_age_days1,841
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on crates, pypi
35/35Publish recency — latest publish 40 days ago
20/20Version history — 62 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageswindows-capture, windows-capture
ecosystemscrates, pypi
any_deprecatedno
min_days_since_publish40

Engineering Quality

Are baseline engineering and documentation practices in place?

50Moderate · 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
0/20OpenSSF Scorecard: CI-Tests — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0
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/windows-capture
10/10Repository description
10/10Topics — 10 topics
0/10Wiki
Inputs used
topicsgame-capture, python, python-library, rust, screen-capture, screen-recorder, screenshot, screenshots, video-recording, rust-lang
has_wikino
homepage—
docs_sitehttps://docs.rs/windows-capture
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

59Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 3/27 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
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 — 7 commit(s) and 10 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
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.9
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
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages63
unassessed_packages5
affected_by_severityunknown 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 63 resolved dependencies against OSV. 5 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

54Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
14.9/40Legible commit history — 28 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.28
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Cargo.toml, windows-capture-python/Cargo.toml (toolchain convention, no task runner)
0/22Automated tests
11/11Lint / format config — rustfmt.toml
11/11Static type checking — Rust (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
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_testsno
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml, windows-capture-python/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Rust (statically typed)
55/55Manageable file sizes — 0/18 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes50,288
source_files_sampled18
oversized_source_files0
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

506GitHub stars
18contributors
37commits, last 12 months
10days since last push
0releases
1bus factor
15open issues
crates.io, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'windows-capture-python' from its registry
  • pypi download statistics for 'windows-capture' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced

More detail

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

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.

0204060807722023-112025-042026-09

Each point covers 3 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-18 00:34 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/27 approved changesets -- score normalized to 1
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained7 commit(s) and 10 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
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
crates.iowindows0.62.2Cargo.toml
crates.iowindows-future0.3.2Cargo.toml
crates.ioparking_lot0.12.5Cargo.toml
crates.iorayon1.12.0Cargo.toml
crates.iothiserror2.0.18Cargo.toml
crates.iopyo30.29.0windows-capture-python/Cargo.toml
crates.iothiserror2.0.18windows-capture-python/Cargo.toml
crates.iowindows0.62.2windows-capture-python/Cargo.toml
crates.iowindows-capture2.0.1windows-capture-python/Cargo.toml
PyPInumpy—windows-capture-python/pyproject.toml
PyPIopencv-python—windows-capture-python/pyproject.toml
All dependencies 68

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

RegistryPackageVersionRelation
crates.ioparking_lot0.12.5direct
crates.iopyo3—direct
crates.iopyo30.29.0direct
crates.iorayon1.12.0direct
crates.iothiserror—direct
crates.iothiserror2.0.18direct
crates.iowindows—direct
crates.iowindows0.62.2direct
crates.iowindows-capture—direct
crates.iowindows-future0.3.2direct
crates.ioanstream1.0.0indirect
crates.ioanstyle1.0.14indirect
crates.ioanstyle-parse1.0.0indirect
crates.ioanstyle-query1.1.5indirect
crates.ioanstyle-wincon3.0.11indirect
crates.iobitflags2.10.0indirect
crates.ioblock20.6.2indirect
crates.iocfg-if1.0.4indirect
crates.iocfg_aliases0.2.1indirect
crates.ioclap4.6.1indirect
crates.ioclap_builder4.6.0indirect
crates.ioclap_derive4.6.1indirect
crates.ioclap_lex1.1.0indirect
crates.iocolorchoice1.0.5indirect
crates.iocrossbeam-deque0.8.6indirect
crates.iocrossbeam-epoch0.9.18indirect
crates.iocrossbeam-utils0.8.21indirect
crates.ioctrlc3.5.2indirect
crates.iodispatch20.3.0indirect
crates.ioeither1.15.0indirect
crates.ioheck0.5.0indirect
crates.iois_terminal_polyfill1.70.2indirect
crates.iolibc0.2.186indirect
crates.iolock_api0.4.14indirect
crates.ionix0.31.2indirect
crates.ioobjc20.6.3indirect
crates.ioobjc2-encode4.1.0indirect
crates.ioonce_cell1.21.4indirect
crates.ioonce_cell_polyfill1.70.2indirect
crates.ioparking_lot_core0.9.12indirect
crates.ioportable-atomic1.13.1indirect
crates.ioproc-macro21.0.106indirect
crates.iopyo3-build-config0.29.0indirect
crates.iopyo3-ffi0.29.0indirect
crates.iopyo3-macros0.29.0indirect
crates.iopyo3-macros-backend0.29.0indirect
crates.ioquote1.0.46indirect
crates.iorayon-core1.13.0indirect
crates.ioredox_syscall0.5.17indirect
crates.ioscopeguard1.2.0indirect
crates.iosmallvec1.15.1indirect
crates.iostrsim0.11.1indirect
crates.iosyn2.0.118indirect
crates.iotarget-lexicon0.13.5indirect
crates.iothiserror-impl2.0.18indirect
crates.iounicode-ident1.0.24indirect
crates.ioutf8parse0.2.2indirect
crates.iowindows-collections0.3.2indirect
crates.iowindows-core0.62.2indirect
crates.iowindows-implement0.60.2indirect
crates.iowindows-interface0.59.3indirect
crates.iowindows-link0.2.1indirect
crates.iowindows-numerics0.3.1indirect
crates.iowindows-result0.4.1indirect
crates.iowindows-strings0.5.1indirect
crates.iowindows-sys0.61.2indirect
crates.iowindows-threading0.2.1indirect
PyPImaturin—indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 63 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct. 5 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
crossbeam-epoch0.9.18indirectunknown10.9.20

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, PyPI.