Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 00:50 UTC

sigma67 / ytmusicapi

Unofficial API for YouTube Music

PythonMIT★ 2,934 stars⑂ 330 forkssince Feb 2020View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

sigma67/ytmusicapi holds a health index of 94 out of 100, placing it in the Exceptional band. It scores highest on Engineering Quality (94/100) and lowest on Security (70/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

94
overall / 100
Exceptional

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.

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

Ownership

sigma67Personal account
138 followers49 public repossince Dec 2015

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 publish
PyPIytmusicapi1.12.2313,113944 days ago

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
15.2/36Commit cadence22/52 weeks with commits
17.7/18Commit volume92 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 25 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year92
human_commit_share0.91
days_since_last_push2
active_weeks_last_year22
How it's scored
27/27Ships releases96 releases published
36/36Release recencylatest release 4 days ago
19.8/27Release cadencea release every ~52 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count96
latest_release_tag1.12.2
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases52
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?

81Excellent · 17% of overall
How it's scored
56.2/60Stars2,934 stars
21/25Forks330 forks
7/15Watchers19 watchers
Inputs used
forks330
stars2,934
watchers19
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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
73.3/80Monthly downloads313,113 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesytmusicapi
dependents
ecosystemspypi
total_downloads
monthly_downloads313,113
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?

74Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.4/22.5Commit distributiontop contributor authored 49% of commits
13.5/13.5Contributor breadth86 contributors
10/10OpenSSF Scorecard: Contributorsproject has 9 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled86
top_contributor_share0.493
How it's scored
39.5/42Issue resolution94% of issues closed
23.9/30PR acceptance243/305 decided PRs merged
13/13Newcomer PR acceptance6/6 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 12/25 approved changesets -- score normalized to 4
Inputs used
merged_prs243
open_issues34
closed_issues546
prs_merged_7d7
prs_decided_7d7
prs_merged_30d19
prs_decided_30d19
issue_closed_ratio0.941
closed_unmerged_prs62
first_time_authors_30d5
first_time_prs_merged_30d6
first_time_prs_decided_30d6
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
15.4/25Owner reach138 followers of sigma67
24.4/25Track record49 public repos, account ~10 yr old
Inputs used
followers138
owner_typeUser
is_verified
owner_loginsigma67
public_repos49
account_age_days3,889
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 4 days ago
20/20Version history94 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesytmusicapi
ecosystemspypi
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

94Exceptional · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests25 out of 30 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://ytmusicapi.readthedocs.io
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsyoutube, youtube-music, youtube-api, ytmusicapi, youtube-music-api
has_wikiyes
homepagehttps://ytmusicapi.readthedocs.io
docs_sitehttps://ytmusicapi.readthedocs.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

70Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2/2.5CI-Tests25 out of 30 merged PRs checked by a CI test -- score normalized to 8
0.5/2.5CII-Best-Practicesbadge detected: InProgress
3/7.5Code-ReviewFound 12/25 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 9 contributing companies or organizations
0/10Dangerous-Workflowdangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 25 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
3/5SASTSAST tool is not run on all commits -- score normalized to 6
4.5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
3.8/7.5Vulnerabilities5 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.2
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_packages5
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:ytmusicapi@1.12.2 runtime dependency closure — what installing the published package pulls in — 5 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.

72Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history80 of 91 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.879
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapdocs/Makefile
22/22Automated tests
11/11Lint / format config
11/11Static type checkingytmusicapi/py.typed
10/10Reproducible environmentlockfile
10/10Demonstrated agent practice14 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance9 of the last 100 commits are automated dependency updates
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilespdm.lock
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configsytmusicapi/py.typed
agent_commit_share0.14
toolchain_manifests
dependency_bot_commit_share0.09
How it's scored
27/45Type-checkable codePython with type-check config (ytmusicapi/py.typed)
55/55Manageable file sizes0/77 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes48,235
source_files_sampled77
oversized_source_files0

Key facts

2,934GitHub stars
86contributors
92commits, last 12 months
2days since last push
96releases
2bus factor
34open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 330 ⇿
0Stars
330Forks
90Releases

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.

012525037532852020-042023-062026-08
Major 1Minor 32Patch 56

Each point covers 6 days.

OpenSSF Scorecard 6.2 / 10
6.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-13 00:50 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
8CI-Tests25 out of 30 merged PRs checked by a CI test -- score normalized to 8
2CII-Best-Practicesbadge detected: InProgress
4Code-ReviewFound 12/25 approved changesets -- score normalized to 4
10Contributorsproject has 9 contributing companies or organizations
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 25 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
6SASTSAST tool is not run on all commits -- score normalized to 6
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
5Vulnerabilities5 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPIrequests>= 2.22pyproject.toml
All dependencies 3

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

RegistryPackageVersionRelation
PyPIsphinxindirect
PyPIsphinx-autodoc-typehintsindirect
PyPIsphinx-rtd-themeindirect
Dependency advisories 0

Installing pypi:ytmusicapi@1.12.2 pulls in 5 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.31.0 — full methodology · metrics wiki.

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