Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 00:21 UTC

noisetorch / NoiseTorch

Real-time microphone noise suppression on Linux.

Go · CCustom license★ 10,312 stars⑂ 254 forkssince Jul 2020View on GitHub ↗
KindDesktop applicationhow this is determined

noisetorch/NoiseTorch holds a health index of 29 out of 100, placing it in the At Risk band. It scores highest on Community & Adoption (69/100) and lowest on Vitality (25/100). It was last updated 591 days ago. 2 contributors account for most of its recent work.

29
overall / 100
At Risk

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.

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

Ownership

40 followers4 public repossince May 2022

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?

25At Risk · 21% of overall
How it's scored
0/36Push recencylast push 591 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share0.89
days_since_last_push591
active_weeks_last_year0
How it's scored
27/27Ships releases31 releases published
0/36Release recencylatest release 1,532 days ago
27/27Release cadencea release every ~43.7 days
8/10OpenSSF Scorecard: Signed-Releases3 out of the last 3 releases have a total of 3 signed artifacts.
Inputs used
releases_count31
latest_release_tagv0.12.2
releases_from_tagsno
days_since_latest_release1,532
mean_days_between_releases43.7

Community & Adoption

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

69Good · 17% of overall
How it's scored
60/60Stars10,312 stars
20/25Forks254 forks
10/15Watchers63 watchers
Inputs used
forks254
stars10,312
watchers63
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/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_readmeyes
has_licenseyes
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?

65Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
13/22.5Commit distributiontop contributor authored 42% of commits
13.5/13.5Contributor breadth21 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled21
top_contributor_share0.423
How it's scored
34.6/42Issue resolution82% of issues closed
20.2/30PR acceptance64/95 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs64
open_issues59
closed_issues274
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.823
closed_unmerged_prs31
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
0/20Verified domain
11.6/25Owner reach40 followers of noisetorch
13.6/25Track record4 public repos, account ~4 yr old
Inputs used
followers40
owner_typeOrganization
is_verifiedno
owner_loginnoisetorch
public_repos4
account_age_days1,560

Engineering Quality

Are baseline engineering and documentation practices in place?

42Weak · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 14 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics9 topics
10/10Wiki
Inputs used
topicsnoise-reduction, noise-suppression, voice, voice-activity-detection, voice-activated, pulseaudio, linux, hacktoberfest, hacktoberfest2023
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

44Weak · 16% of overall
How it's scored
0/7.5Binary-Artifactsbinaries present in source code
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Tests0 out of 14 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
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 5 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
3.5/5SASTSAST tool detected but not run on all commits
0/5Security-Policysecurity policy file not detected
6/7.5Signed-Releases3 out of the last 3 releases have a total of 3 signed artifacts.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities39 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.
How it's scored
7/35Direct dependencies free of known advisories1 affected: golang.org/x/crypto 0.14.0 (critical 10.0)
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
32/40No advisories left outstanding1 advisory-carrying package(s) unaddressed past 90 days; oldest published 983 days ago
Inputs used
sourceosv
advisories55
affected_packages2
assessed_packages15
unassessed_packages0
affected_by_severitycritical 1, high 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 15 resolved dependencies against OSV. 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.

52Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
32.4/40Legible commit history54 of 89 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.607
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile, c/ladspa/Makefile, vendor/github.com/BurntSushi/xgb/Makefile, vendor/github.com/BurntSushi/xgbutil/Makefile
0/22Automated tests
0/11Lint / format config
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance11 of the last 100 commits are automated dependency updates
1/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsno
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile, c/ladspa/Makefile, vendor/github.com/BurntSushi/xgb/Makefile, vendor/github.com/BurntSushi/xgbutil/Makefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsgo.mod, vendor/gioui.org/cpu/go.mod, vendor/gioui.org/shader/go.mod, vendor/github.com/BurntSushi/toml/go.mod, vendor/github.com/aarzilli/nucular/go.mod, vendor/github.com/blang/semver/v4/go.mod, vendor/github.com/go-gl/glfw/v3.3/glfw/go.mod, vendor/github.com/hashicorp/golang-lru/go.mod, vendor/github.com/noisetorch/pulseaudio/go.mod
dependency_bot_commit_share0.11
How it's scored
45/45Type-checkable codeGo (statically typed)
55/55Manageable file sizes0/15 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes27,593
source_files_sampled15
oversized_source_files0

Key facts

10,312GitHub stars
21contributors
0commits, last 12 months
591days since last push
31releases
2bus factor
59open issues
Gopackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 254 ⇿
0Stars
254Forks
26Releases

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.

050100150200250300254212020-072023-072026-08
Major 0Minor 4Patch 10

Each point covers 6 days.

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-08-28 00:20 UTC

0Binary-Artifactsbinaries present in source code
3Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 14 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
7SASTSAST tool detected but not run on all commits
0Security-Policysecurity policy file not detected
8Signed-Releases3 out of the last 3 releases have a total of 3 signed artifacts.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities39 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Gogithub.com/BurntSushi/tomlv1.3.2go.mod
Gogithub.com/BurntSushi/xgbutilv0.0.0-20190907113008-ad855c713046go.mod
Gogithub.com/aarzilli/nucularv0.0.0-20210408133902-d3dd7b05a80ago.mod
Gogithub.com/blang/semver/v4v4.0.0go.mod
Gogithub.com/noisetorch/pulseaudiov0.0.0-20220603053345-9303200c3861go.mod
Gogithub.com/syndtr/gocapabilityv0.0.0-20200815063812-42c35b437635go.mod
Gogolang.org/x/cryptov0.14.0go.mod
All dependencies 15

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

RegistryPackageVersionRelation
Gogithub.com/aarzilli/nucular0.0.0-20210408133902-d3dd7b05a80adirect
Gogithub.com/blang/semver/v44.0.0direct
Gogithub.com/burntsushi/toml1.3.2direct
Gogithub.com/burntsushi/xgbutil0.0.0-20190907113008-ad855c713046direct
Gogithub.com/noisetorch/pulseaudio0.0.0-20220603053345-9303200c3861direct
Gogithub.com/syndtr/gocapability0.0.0-20200815063812-42c35b437635direct
Gogolang.org/x/crypto0.14.0direct
Gogioui.org0.0.0-20220105104929-8d8aeef66befindirect
Gogithub.com/burntsushi/xgb0.0.0-20210121224620-deaf085860bcindirect
Gogithub.com/go-gl/glfw/v3.3/glfw0.0.0-20211213063430-748e38ca8aecindirect
Gogithub.com/golang/freetype0.0.0-20170609003504-e2365dfdc4a0indirect
Gogithub.com/hashicorp/golang-lru0.5.4indirect
Gogolang.org/x/exp0.0.0-20220104160115-025e73f80486indirect
Gogolang.org/x/image0.5.0indirect
Gogolang.org/x/mobile0.0.0-20220104184238-4a8be17bd2e3indirect
Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 15 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 1 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
golang.org/x/crypto0.14.0directcritical383.4.0
golang.org/x/image0.5.0indirecthigh170.45.0

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.