Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 06:26 UTC

robmorgan / timestretch-rs

Pure 🦀 Rust audio time-stretching library optimized for electronic dance music.

RustMIT★ 19 stars⑂ 2 forkssince Feb 2026View on GitHub ↗
KindDesktop applicationLibraryhow this is determined

robmorgan/timestretch-rs holds a health index of 75 out of 100, placing it in the Good band. It scores highest on AI Readiness (84/100) and lowest on Community & Adoption (39/100). It was last updated today. A single contributor accounts for most of its recent work.

75
overall / 100
Good

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.

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

Ownership

Rob MorganPersonal account
289 followers64 public repossince Jan 2010@brightfame

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.iotimestretch0.13.02,103152 days agoaudiodspedmphase-vocodertime-stretchingalgorithms

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
7.6/36Commit cadence11/52 weeks with commits
18/18Commit volume1,041 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,041
human_commit_share1
days_since_last_push0
active_weeks_last_year11

Release discipline

100Exceptional
How it's scored
27/27Ships releases15 releases published
36/36Release recencylatest release 2 days ago
27/27Release cadencea release every ~4.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count15
latest_release_tagv0.13.0
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases4.3
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?

39Weak · 17% of overall
How it's scored
20.4/60Stars19 stars
0/25Forks2 forks
0/15Watchers0 watchers
Inputs used
forks2
stars19
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
44.3/80Monthly downloads2,103 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagestimestretch
dependents
ecosystemscrates
total_downloads6,896
monthly_downloads2,103
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution100% of issues closed
29.6/30PR acceptance68/69 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/13 approved changesets -- score normalized to 0
Inputs used
merged_prs68
open_issues0
closed_issues1
prs_merged_7d8
prs_decided_7d8
prs_merged_30d47
prs_decided_30d47
issue_closed_ratio1
closed_unmerged_prs1
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
17.7/25Owner reach289 followers of robmorgan
25/25Track record64 public repos, account ~16 yr old
Inputs used
followers289
owner_typeUser
is_verified
owner_loginrobmorgan
public_repos64
account_age_days6,069
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on crates
35/35Publish recencylatest publish 2 days ago
20/20Version history15 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestimestretch
ecosystemscrates
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests10 out of 10 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://crates.io/crates/timestretch
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepagehttps://crates.io/crates/timestretch
docs_sitehttps://crates.io/crates/timestretch
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/13 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 4 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
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-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.3
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 advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages51
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:timestretch@0.13.0 runtime dependency closure — what installing the published package pulls in — 51 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.

84Excellent · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes1,653
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingRust (statically typed)
10/10Reproducible environmentlockfile
10/10Demonstrated agent practice65 of the last 100 commits agent-authored or agent-credited
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
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.65
toolchain_manifestsCargo.toml, desktop/Cargo.toml, tools/ab-tui/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
52.6/55Manageable file sizes5/115 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes118,168
source_files_sampled115
oversized_source_files5
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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

19GitHub stars
1contributors
1,041commits, last 12 months
0days since last push
15releases
1bus factor
0open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'timestretch-desktop' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
9Releases

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.

111222212026-062026-072026-08
Major 0Minor 7Patch 2
OpenSSF Scorecard 4.3 / 10
4.3aggregate

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-22 06:26 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests10 out of 10 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 0/13 approved changesets -- score normalized to 0
10Contributorsproject has 4 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 1 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 12
RegistryPackageVersion constraintManifest
crates.iorustfft6Cargo.toml
crates.ioserde1Cargo.toml
crates.ioserde_json1Cargo.toml
crates.ioarc-swap1.7Cargo.toml
crates.ioebur1280.1.10Cargo.toml
crates.iotimestretchdesktop/Cargo.toml
crates.ioeframe0.31desktop/Cargo.toml
crates.iocpal0.15desktop/Cargo.toml
crates.iosymphonia0.5desktop/Cargo.toml
crates.iorfd0.15desktop/Cargo.toml
crates.iolog0.4desktop/Cargo.toml
crates.ioenv_logger0.11desktop/Cargo.toml
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

Dependency advisories 0

Installing crates:timestretch@0.13.0 pulls in 51 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 statisticscrates.io.