Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 12:06 UTC

izzyreal / vmpc-juce

JUCE implementation of VMPC2000XL

C · C++GPL-3.0★ 256 stars⑂ 19 forkssince Jan 2018View on GitHub ↗
KindMobile applicationhow this is determined

izzyreal/vmpc-juce holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on Vitality (91/100) and lowest on Engineering Quality (42/100). It was last updated today. A single contributor accounts for most of its recent work.

60
overall / 100
Moderate

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.

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

Ownership

Izmar VerhagePersonal account
103 followers100 public repossince Feb 2013

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Metrics by category

Vitality

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

91Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
27.7/36Commit cadence — 40/52 weeks with commits
18/18Commit volume — 435 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year435
human_commit_share1
days_since_last_push0
active_weeks_last_year40
How it's scored
27/27Ships releases — 34 releases published
36/36Release recency — latest release 28 days ago
27/27Release cadence — a release every ~11.3 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count34
latest_release_tagv0.9.17
releases_from_tagsno
days_since_latest_release28
mean_days_between_releases11.3

Community & Adoption

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

53Moderate · 17% of overall
How it's scored
39/60Stars — 256 stars
10.5/25Forks — 19 forks
6.5/15Watchers — 16 watchers
Inputs used
forks19
stars256
watchers16
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
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?

48Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
4.1/13.5Contributor breadth — 3 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.999
How it's scored
36.8/42Issue resolution — 88% of issues closed
28.1/30PR acceptance — 15/16 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs15
open_issues18
closed_issues126
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.875
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 backing — personal (user) account
0/20Verified domain — not applicable to user accounts
14.5/25Owner reach — 103 followers of izzyreal
25/25Track record — 100 public repos, account ~13 yr old
Inputs used
followers103
owner_typeUser
is_verified—
owner_loginizzyreal
public_repos100
account_age_days4,952
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

42Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 9 topics
10/10Wiki
Inputs used
topicsaudio, drum, juce, machine, mpc, sampler, sequencer, virtual, mpc2000xl
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?

48Weak · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — no data
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
2/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — no data
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.5
Excluded from scoring (no data or not applicable): Branch-Protection, CI-Tests, Dangerous-Workflow, Packaging, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages97
unassessed_packages0
affected_by_severitymoderate 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 97 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
12.8/40Legible commit history — 24 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.24
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — android/app/build.gradle, android/build.gradle (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — C (statically typed)
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
4/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsandroid/app/build.gradle, android/build.gradle
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — C (statically typed)
54/55Manageable file sizes — 3/166 source files over 60KB
Inputs used
primary_languageC
largest_source_bytes5,562,353
source_files_sampled166
oversized_source_files3

Key facts

256GitHub stars
3contributors
435commits, last 12 months
0days since last push
34releases
1bus factor
18open issues
Mavenpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 19 ⇿
0Stars
19Forks
34Releases

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.

0481216201942020-112023-102026-08
Major 0Minor 1Patch 15

Each point covers 6 days.

OpenSSF Scorecard 3.5 / 10
3.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-09-19 12:06 UTC

9Binary-Artifactsbinaries present in source code
n/aBranch-Protectioninternal 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
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
n/aToken-PermissionsNo tokens found
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 97

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

RegistryPackageVersionRelation
RubyGemsabbrev0.1.2indirect
RubyGemsaddressable2.9.0indirect
RubyGemsartifactory3.0.17indirect
RubyGemsatomos0.1.3indirect
RubyGemsaws-eventstream1.4.0indirect
RubyGemsaws-partitions1.1282.0indirect
RubyGemsaws-sdk-core3.254.1indirect
RubyGemsaws-sdk-kms1.130.0indirect
RubyGemsaws-sdk-s31.229.0indirect
RubyGemsaws-sigv41.12.1indirect
RubyGemsbabosa1.0.4indirect
RubyGemsbase640.3.0indirect
RubyGemsbenchmark0.5.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsCFPropertyList3.0.8indirect
RubyGemsclaide1.1.0indirect
RubyGemscolored1.2indirect
RubyGemscolored23.1.2indirect
RubyGemscommander4.6.0indirect
RubyGemscsv3.3.6indirect
RubyGemsdeclarative0.0.20indirect
RubyGemsdigest-crc0.7.0indirect
RubyGemsdomain_name0.6.20240107indirect
RubyGemsdotenv2.8.1indirect
RubyGemsemoji_regex3.2.3indirect
RubyGemsexcon0.112.0indirect
RubyGemsfaraday1.10.6indirect
RubyGemsfaraday-cookie_jar0.0.8indirect
RubyGemsfaraday-em_http1.0.0indirect
RubyGemsfaraday-em_synchrony1.0.1indirect
RubyGemsfaraday-excon1.1.0indirect
RubyGemsfaraday-httpclient1.0.1indirect
RubyGemsfaraday-multipart1.2.0indirect
RubyGemsfaraday-net_http1.0.2indirect
RubyGemsfaraday-net_http_persistent1.2.0indirect
RubyGemsfaraday-patron1.0.0indirect
RubyGemsfaraday-rack1.0.0indirect
RubyGemsfaraday-retry1.0.4indirect
RubyGemsfaraday_middleware1.2.1indirect
RubyGemsfastimage2.4.1indirect
RubyGemsfastlane2.235.0indirect
RubyGemsfastlane-sirp1.1.0indirect
RubyGemsgh_inspector1.1.3indirect
RubyGemsgoogle-apis-androidpublisher_v30.107.0indirect
RubyGemsgoogle-apis-core0.18.0indirect
RubyGemsgoogle-apis-iamcredentials_v10.28.0indirect
RubyGemsgoogle-apis-playcustomapp_v10.18.0indirect
RubyGemsgoogle-apis-storage_v10.66.0indirect
RubyGemsgoogle-cloud-core1.9.0indirect
RubyGemsgoogle-cloud-env2.2.2indirect
RubyGemsgoogle-cloud-errors1.7.0indirect
RubyGemsgoogle-cloud-storage1.62.0indirect
RubyGemsgoogle-logging-utils0.2.0indirect
RubyGemsgoogleauth1.17.4indirect
RubyGemshighline2.0.3indirect
RubyGemshttp-cookie1.0.8indirect
RubyGemshttpclient2.9.0indirect
RubyGemsjmespath1.6.2indirect
RubyGemsjson2.21.2indirect
RubyGemsjwt3.2.0indirect
RubyGemslogger1.7.0indirect
RubyGemsmini_magick4.13.2indirect
RubyGemsmini_mime1.1.5indirect
RubyGemsmulti_json1.19.1indirect
RubyGemsmultipart-post2.4.1indirect
RubyGemsmutex_m0.3.0indirect
RubyGemsnanaimo0.4.0indirect
RubyGemsnaturally2.3.0indirect
RubyGemsnkf0.3.0indirect
RubyGemsoptparse0.8.1indirect
RubyGemsos1.1.4indirect
RubyGemsostruct0.6.3indirect
RubyGemsplist3.7.2indirect
RubyGemspstore0.2.1indirect
RubyGemspublic_suffix7.0.5indirect
RubyGemsrake13.4.2indirect
RubyGemsrepresentable3.2.0indirect
RubyGemsretriable3.8.0indirect
RubyGemsrexml3.4.4indirect
RubyGemsrouge3.28.0indirect
RubyGemsruby2_keywords0.0.5indirect
RubyGemsrubyzip2.4.1indirect
RubyGemssecurity0.1.5indirect
RubyGemssignet0.22.0indirect
RubyGemssimctl1.6.10indirect
RubyGemsterminal-notifier2.0.0indirect
RubyGemsterminal-table3.0.2indirect
RubyGemstrailblazer-option0.1.2indirect
RubyGemstty-cursor0.7.1indirect
RubyGemstty-screen0.8.2indirect
RubyGemstty-spinner0.9.3indirect
RubyGemsuber0.1.0indirect
RubyGemsunicode-display_width2.6.0indirect
RubyGemsword_wrap1.0.0indirect
RubyGemsxcodeproj1.28.1indirect
RubyGemsxcpretty0.4.1indirect
RubyGemsxcpretty-travis-formatter1.0.1indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
excon0.112.0indirectmoderate11.5.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.