Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 01:30 UTC

zverok / yard-junk

Get rid of the junk in your YARD docs

RubyMIT★ 71 stars⑂ 4 forkssince Aug 2017View on GitHub ↗

zverok/yard-junk holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on Engineering Quality (64/100) and lowest on Vitality (33/100). It was last updated 123 days ago. A single contributor accounts for most of its recent work.

48
overall / 100
Weak

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.

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

Ownership

Victor Shepelev Personal account
550 followers100 public repossince Sep 2009Netsoft

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
RubyGemsyard-junk0.1.0-11123 days ago

Metrics by category

Vitality

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

33At Risk · 21% of overall
How it's scored
9.9/36Push recencylast push 123 days ago
0.7/36Commit cadence1/52 weeks with commits
2.7/18Commit volume1 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year1
human_commit_share
days_since_last_push123
active_weeks_last_year1
How it's scored
16.2/27Ships releases11 version tags (no GitHub releases)
27/36Release recencylatest release 123 days ago
12.6/27Release cadencea release every ~346.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count11
latest_release_tagv0.1.0
releases_from_tagsyes
days_since_latest_release123
mean_days_between_releases346.1
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?

51Moderate · 17% of overall
How it's scored
29.9/60Stars71 stars
4/25Forks4 forks
0/15Watchers2 watchers
Inputs used
forks4
stars71
watchers2
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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
63.2/80Total downloads1,207,534 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesyard-junk
dependents
ecosystemsrubygems
total_downloads1,207,534
monthly_downloads
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.3/22.5Commit distributiontop contributor authored 81% of commits
5.4/13.5Contributor breadth4 contributors
10/10OpenSSF Scorecard: Contributorsproject has 10 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.807
How it's scored
21/42Issue resolution50% of issues closed
27.7/30PR acceptance24/26 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 4/26 approved changesets -- score normalized to 1
Inputs used
merged_prs24
open_issues10
closed_issues10
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.5
closed_unmerged_prs2
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
19.7/25Owner reach550 followers of zverok
25/25Track record100 public repos, account ~16 yr old
Inputs used
followers550
owner_typeUser
is_verified
owner_loginzverok
public_repos100
account_age_days6,142
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 rubygems
35/35Publish recencylatest publish 123 days ago
20/20Version history11 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesyard-junk
ecosystemsrubygems
any_deprecatedno
min_days_since_publish123

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests1 out of 10 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsruby, yard, docs, ci
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?

36Weak · 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
0.2/2.5CI-Tests1 out of 10 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 4/26 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 10 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
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
2.2/7.5Vulnerabilities7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

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.

44Weak · 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
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/26 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes7,582
source_files_sampled26
oversized_source_files0
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

71GitHub stars
4contributors
1commits, last 12 months
123days since last push
11releases
1bus factor
10open issues
RubyGemspackage ecosystems

More detail

OpenSSF Scorecard 3.6 / 10
3.6aggregate

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-17 01:30 UTC

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

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

RegistryPackageVersionRelation
RubyGemsaddressable2.8.9indirect
RubyGemsast2.4.3indirect
RubyGemsbenchmarkindirect
RubyGemsbenchmark0.4.1indirect
RubyGemsbigdecimal4.0.1indirect
RubyGemsdiff-lcs1.5.1indirect
RubyGemsdocile1.4.1indirect
RubyGemsfakefsindirect
RubyGemsfakefs2.5.0indirect
RubyGemsio-console0.7.2indirect
RubyGemsirb1.14.0indirect
RubyGemsjar-dependencies0.4.1indirect
RubyGemsjson2.19.1indirect
RubyGemsjson-schema6.2.0indirect
RubyGemskramdownindirect
RubyGemskramdown2.4.0indirect
RubyGemslanguage_server-protocol3.17.0.5indirect
RubyGemslint_roller1.1.0indirect
RubyGemsmcp0.8.0indirect
RubyGemsmoarspecindirect
RubyGemsmoarspec0.1.2indirect
RubyGemsostructindirect
RubyGemsostruct0.6.0indirect
RubyGemsparallel1.27.0indirect
RubyGemsparser3.3.10.2indirect
RubyGemsprism1.9.0indirect
RubyGemspsych5.1.2indirect
RubyGemspublic_suffix7.0.5indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbowindirect
RubyGemsrainbow3.1.1indirect
RubyGemsrakeindirect
RubyGemsrake13.2.1indirect
RubyGemsrdoc6.7.0indirect
RubyGemsregexp_parser2.11.3indirect
RubyGemsreline0.5.10indirect
RubyGemsrexml3.3.7indirect
RubyGemsrspecindirect
RubyGemsrspec3.13.0indirect
RubyGemsrspec-core3.13.1indirect
RubyGemsrspec-expectations3.13.2indirect
RubyGemsrspec-itsindirect
RubyGemsrspec-its1.3.0indirect
RubyGemsrspec-mocks3.13.1indirect
RubyGemsrspec-support3.13.1indirect
RubyGemsrubocopindirect
RubyGemsrubocop1.85.1indirect
RubyGemsrubocop-ast1.49.1indirect
RubyGemsrubocop-rakeindirect
RubyGemsrubocop-rake0.7.1indirect
RubyGemsrubocop-rspecindirect
RubyGemsrubocop-rspec3.9.0indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsrubygems-tasksindirect
RubyGemsrubygems-tasks0.2.6indirect
RubyGemssimplecovindirect
RubyGemssimplecov0.22.0indirect
RubyGemssimplecov-html0.12.3indirect
RubyGemssimplecov_json_formatter0.1.4indirect
RubyGemsstringio3.1.1indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemsyardindirect
RubyGemsyard0.9.37indirect
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.11.0 — full methodology · metrics wiki.

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