A library for soundscape synthesis and augmentation
justinsalamon/scaper holds a health index of 26 out of 100, placing it in the At Risk band. It scores highest on Community & Adoption (56/100) and lowest on Vitality (25/100). It was last updated 1552 days ago. A single contributor accounts for most of its recent work.
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.
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 46 is calibrated to 44 on the published index scale (record calibration 2026-08-02).
This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| PyPI | scaper | 1.6.5 | - | 37 | 1928 days ago | audiosoundsoundscapeenvironmentaldspmixing |
Is the project alive — is code being written and are releases shipping?
Silence alone is never the finding — a small, finished library may need no commits for years. This alert requires both: no human commit for a long time, and obligations the project is visibly not discharging. Automated commits do not count as maintenance.
How abandonment is assessed| 0/36 | Push recency — last push 1,552 days ago |
| 0/36 | Commit cadence — 0/52 weeks with commits |
| 0/18 | Commit volume — 0 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| commits_last_year | 0 |
| human_commit_share | 1 |
| days_since_last_push | 1,552 |
| active_weeks_last_year | 0 |
| 27/27 | Ships releases — 38 releases published |
| 0/36 | Release recency — latest release 1,928 days ago |
| 27/27 | Release cadence — a release every ~24.1 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
| releases_count | 38 |
| latest_release_tag | v1.6.5 |
| releases_from_tags | no |
| days_since_latest_release | 1,928 |
| mean_days_between_releases | 24.1 |
Does the project have users, downloads, attention, and a welcoming setup for contributors?
| 42.6/60 | Stars — 426 stars |
| 15.3/25 | Forks — 70 forks |
| 4.3/15 | Watchers — 7 watchers |
| forks | 70 |
| stars | 426 |
| watchers | 7 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (BSD-3-Clause) |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
| has_readme | yes |
| has_license | yes |
| readme_badges | 6 |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | coveralls.io, readthedocs.org, shields.io, travis-ci.org |
| has_pull_request_template | no |
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 3.1/22.5 | Commit distribution — top contributor authored 86% of commits |
| 5.4/13.5 | Contributor breadth — 4 contributors |
| 6/10 | OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6 |
| bus_factor | 1 |
| contributors_sampled | 4 |
| top_contributor_share | 0.864 |
| 18.9/42 | Issue resolution — 45% of issues closed |
| 27.4/30 | PR acceptance — 42/46 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 13.5/15 | OpenSSF Scorecard: Code-Review — Found 16/17 approved changesets -- score normalized to 9 |
| merged_prs | 42 |
| open_issues | 59 |
| closed_issues | 48 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 0 |
| prs_decided_30d | 0 |
| issue_closed_ratio | 0.449 |
| closed_unmerged_prs | 4 |
| first_time_authors_30d | 0 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 0 |
| 10/30 | Ownership backing — personal (user) account |
| 0/20 | Verified domain — not applicable to user accounts |
| 17.9/25 | Owner reach — 305 followers of justinsalamon |
| 23.2/25 | Track record — 34 public repos, account ~13 yr old |
| followers | 305 |
| owner_type | User |
| is_verified | — |
| owner_login | justinsalamon |
| public_repos | 34 |
| account_age_days | 4,984 |
| 25/25 | Published & resolvable — 1 package(s) on pypi |
| 4/35 | Publish recency — latest publish 1,928 days ago |
| 20/20 | Version history — 37 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
| packages | scaper |
| ecosystems | pypi |
| any_deprecated | no |
| min_days_since_publish | 1,928 |
Are baseline engineering and documentation practices in place?
| 0/24 | CI workflows |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — 0 out of 17 merged PRs checked by a CI test -- score normalized to 0 |
| has_ci | no |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | no |
| has_precommit_config | no |
| 30/30 | README |
| 25/25 | Documentation directory |
| 0/15 | Documentation / homepage site |
| 10/10 | Repository description |
| 10/10 | Topics — 9 topics |
| 10/10 | Wiki |
| topics | soundscape, synthesis, audio, soundscape-synthesis, sox, machine-listening, data-augmentation, audio-processing, machine-learning |
| has_wiki | yes |
| homepage | — |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | yes |
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 0/2.5 | CI-Tests — 0 out of 17 merged PRs checked by a CI test -- score normalized to 0 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 6.8/7.5 | Code-Review — Found 16/17 approved changesets -- score normalized to 9 |
| 1.5/2.5 | Contributors — project has 2 contributing companies or organizations -- score normalized to 6 |
| 0/10 | Dangerous-Workflow — no data |
| 0/7.5 | Dependency-Update-Tool — no update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 0/7.5 | Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — no data |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — no data |
| 7.5/7.5 | Vulnerabilities — 0 existing vulnerabilities detected |
| source | openssf_scorecard |
| checks_evaluated | 12 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 6 |
| scorecard_aggregate | 4.1 |
| 35/35 | Direct dependencies free of known advisories — no direct dependency carries a known advisory |
| 25/25 | Indirect dependencies free of known advisories — no indirect dependency carries a known advisory |
| 0/40 | No advisories left outstanding — no advisory carries a publication date |
| source | osv |
| advisories | 0 |
| affected_packages | 0 |
| assessed_packages | 21 |
| unassessed_packages | 0 |
| affected_by_severity | none |
| direct_affected_packages | 0 |
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.
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 19.2/40 | Legible commit history — 36 of 100 human commits state their intent (structured subject or explanatory body) |
| has_llms_txt | no |
| legible_history_share | 0.36 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
| 18/18 | One-command bootstrap — docs/Makefile |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 0/11 | Static type checking |
| 0/10 | Reproducible environment |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 0/8 | Automated maintenance — no automated dependency updates observed |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — no data |
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | no |
| typed_language | no |
| bootstrap_files | docs/Makefile |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | — |
| agent_commit_share | 0 |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0 |
| 0/45 | Type-checkable code — Python without a type-check config |
| 47.7/55 | Manageable file sizes — 2/15 source files over 60KB |
| primary_language | Python |
| largest_source_bytes | 106,280 |
| source_files_sampled | 15 |
| oversized_source_files | 2 |
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.
Each point covers 9 days.
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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| n/a | Branch-Protection | internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md |
| 0 | CI-Tests | 0 out of 17 merged PRs checked by a CI test -- score normalized to 0 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 9 | Code-Review | Found 16/17 approved changesets -- score normalized to 9 |
| 6 | Contributors | project has 2 contributing companies or organizations -- score normalized to 6 |
| n/a | Dangerous-Workflow | no workflows found |
| 0 | Dependency-Update-Tool | no update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 0 | Maintained | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| n/a | Packaging | packaging workflow not detected |
| n/a | Pinned-Dependencies | no dependencies found |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 0 | Security-Policy | security policy file not detected |
| n/a | Signed-Releases | no releases found |
| n/a | Token-Permissions | No tokens found |
| 10 | Vulnerabilities | 0 existing vulnerabilities detected |
Full resolved dependency set from the GitHub dependency graph: 0 direct and 9 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| PyPI | jams | — | indirect |
| PyPI | numpy | — | indirect |
| PyPI | numpydoc | — | indirect |
| PyPI | pyloudnorm | — | indirect |
| PyPI | soundfile | — | indirect |
| PyPI | sox | 1.4.0 | indirect |
| PyPI | soxbindings | — | indirect |
| PyPI | sphinx-issues | — | indirect |
| PyPI | sphinx-rtd-theme | — | indirect |
Installing pypi:scaper@1.6.5 pulls in 21 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.
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.5.0, schema v0.30.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — PyPI.