Public record
Software health reportschema 0.16.0 · metrics 2.10.0 · 2026-07-20 18:36 UTC

spatialaudio / python-sounddevice

:sound: Play and Record Sound with Python :snake:

PythonMIT★ 1,259 stars⑂ 162 forkssince Jun 2015View on GitHub ↗

spatialaudio/python-sounddevice holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Community & Adoption (74/100) and lowest on AI Readiness (30/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

spatialaudio.netOrganization
162 followers61 public repossince May 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIsounddevice0.5.5-34177 days agosoundaudioportaudioplayrecordplayrec

Metrics by category

Vitality

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

69Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
9/36Commit cadence13/52 weeks with commits
13.9/18Commit volume34 commits in the last year
7/10OpenSSF Scorecard: Maintained7 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year34
human_commit_share
days_since_last_push0
active_weeks_last_year13
How it's scored
27/27Ships releases34 releases published
27/36Release recencylatest release 177 days ago
12.6/27Release cadencea release every ~164.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count34
latest_release_tag0.5.5
releases_from_tagsno
days_since_latest_release177
mean_days_between_releases164.9
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?

74Good · 17% of overall
How it's scored
50.3/60Stars1,259 stars
18.4/25Forks162 forks
8.3/15Watchers32 watchers
Inputs used
forks162
stars1,259
watchers32
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
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?

68Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.8/22.5Commit distributiontop contributor authored 88% of commits
13.5/13.5Contributor breadth18 contributors
10/10OpenSSF Scorecard: Contributorsproject has 7 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled18
top_contributor_share0.876
How it's scored
23.2/42Issue resolution55% of issues closed
26.9/30PR acceptance167/186 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 4/15 approved changesets -- score normalized to 2
Inputs used
merged_prs167
open_issues198
closed_issues245
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.553
closed_unmerged_prs19
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
15.9/25Owner reach162 followers of spatialaudio
25/25Track record61 public repos, account ~12 yr old
Inputs used
followers162
owner_typeOrganization
is_verified
owner_loginspatialaudio
public_repos61
account_age_days4,459
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 pypi
35/35Publish recencylatest publish 177 days ago
20/20Version history34 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagessounddevice
ecosystemspypi
any_deprecatedno
min_days_since_publish177

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://python-sounddevice.readthedocs.io/
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsaudio, soundcard, portaudio, python
has_wikino
homepagehttps://python-sounddevice.readthedocs.io/
docs_sitehttps://python-sounddevice.readthedocs.io/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

56Moderate · 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-Tests27 out of 27 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
1.5/7.5Code-ReviewFound 4/15 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 7 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.5/2.5Licenselicense file detected
5.2/7.5Maintained7 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 7
5/5Packagingpackaging workflow detected
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
0/7.5Vulnerabilities10 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.5
Excluded from scoring (no data or not applicable): 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_packages2
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 pypi:sounddevice@0.5.5 runtime dependency closure — what installing the published package pulls in — 2 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.

30At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePython without a type-check config
52.1/55Manageable file sizes1/19 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes111,654
source_files_sampled19
oversized_source_files1
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

1,259GitHub stars
18contributors
34commits, last 12 months
0days since last push
34releases
1bus factor
198open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 4.5 / 10
4.5aggregate

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-07-20 18:35 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests27 out of 27 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 4/15 approved changesets -- score normalized to 2
10Contributorsproject has 7 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
7Maintained7 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 7
10Packagingpackaging workflow 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
0Vulnerabilities10 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPIcffipyproject.toml
All dependencies 34

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

RegistryPackageVersionRelation
PyPIcffi1.15.1direct
PyPIalabaster0.7.13indirect
PyPIbabel2.14.0indirect
PyPIcertifi2026.1.4indirect
PyPIcharset-normalizer3.4.4indirect
PyPIcolorama0.4.6indirect
PyPIdocutils0.17.1indirect
PyPIidna3.15indirect
PyPIimagesize1.4.1indirect
PyPIimportlib-metadata6.7.0indirect
PyPIinsipid-sphinx-theme0.3.2indirect
PyPIjinja23.1.6indirect
PyPImarkupsafe2.1.5indirect
PyPInumpy1.21.6indirect
PyPIpackaging24.0indirect
PyPIpycparser2.21indirect
PyPIpygments2.17.2indirect
PyPIpytz2025.2indirect
PyPIrequests2.15.1indirect
PyPIroman-numerals4.1.0indirect
PyPIsetuptools68.0.0indirect
PyPIsetuptools-scmindirect
PyPIsnowballstemmer3.0.1indirect
PyPIsphinx4.3.2indirect
PyPIsphinx-last-updated-by-git0.3.8indirect
PyPIsphinxcontrib-applehelp1.0.2indirect
PyPIsphinxcontrib-devhelp1.0.2indirect
PyPIsphinxcontrib-htmlhelp2.0.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp1.0.3indirect
PyPIsphinxcontrib-serializinghtml1.1.5indirect
PyPItomli2.4.0indirect
PyPIurllib32.7.0indirect
PyPIzipp3.19.1indirect
Dependency advisories 0

Installing pypi:sounddevice@0.5.5 pulls in 2 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.16.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.