Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-26 04:24 UTC

yegor256 / telepost

Simple Telegram posting Ruby gem

RubyMIT★ 15 stars⑂ 0 forkssince Dec 2018View on GitHub ↗

yegor256/telepost holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Vitality (92/100) and lowest on Community & Adoption (40/100). It was last updated today. A single contributor accounts for most of its recent work.

78
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.

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

Ownership

Yegor BugayenkoPersonal account
5,342 followers215 public repossince Dec 2010@zerocracy

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
RubyGemstelepost0.10.0-180 days ago

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
28.4/36Commit cadence41/52 weeks with commits
18/18Commit volume132 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year132
human_commit_share0.31
days_since_last_push0
active_weeks_last_year41
How it's scored
27/27Ships releases18 releases published
36/36Release recencylatest release 0 days ago
19.8/27Release cadencea release every ~86.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count18
latest_release_tag0.10.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases86.2
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?

40Weak · 17% of overall
How it's scored
18.6/60Stars15 stars
0/25Forks0 forks
0/15Watchers2 watchers
Inputs used
forks0
stars15
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_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesapi.codeclimate.com, badge.fury.io, github.com, shields.io
has_pull_request_templateno
How it's scored
46/80Total downloads26,600 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagestelepost
dependents
ecosystemsrubygems
total_downloads26,600
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?

65Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.7/22.5Commit distributiontop contributor authored 84% of commits
4.1/13.5Contributor breadth3 contributors
10/10OpenSSF Scorecard: Contributorsproject has 10 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.837
How it's scored
37.8/42Issue resolution90% of issues closed
25.7/30PR acceptance149/174 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/3 approved changesets -- score normalized to 0
Inputs used
merged_prs149
open_issues2
closed_issues18
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.9
closed_unmerged_prs25
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
25/25Owner reach5,342 followers of yegor256
25/25Track record215 public repos, account ~15 yr old
Inputs used
followers5,342
owner_typeUser
is_verified
owner_loginyegor256
public_repos215
account_age_days5,731
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 0 days ago
20/20Version history18 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestelepost
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows10 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests21 out of 21 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://rubygems.org/gems/telepost
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicstelegram, telegram-bot, telegram-api, ruby, ruby-gem
has_wikino
homepagehttps://rubygems.org/gems/telepost
docs_sitehttps://rubygems.org/gems/telepost
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

61Moderate · 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-Tests21 out of 21 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
0/7.5Code-ReviewFound 0/3 approved changesets -- score normalized to 0
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
7.5/7.5Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): Packaging, 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
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages54
unassessed_packages1
affected_by_severitynone
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 54 resolved dependencies against OSV. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
22.4/40Legible commit history13 of 31 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.419
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
10/10Reproducible environmentlockfile
10/10Demonstrated agent practice8 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance69 of the last 100 commits are automated dependency updates
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_share0.08
toolchain_manifests
dependency_bot_commit_share0.69
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/3 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes5,883
source_files_sampled3
oversized_source_files0

Key facts

15GitHub stars
3contributors
132commits, last 12 months
0days since last push
18releases
1bus factor
2open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-26 04:24 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests21 out of 21 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/3 approved changesets -- score normalized to 0
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
10Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
RubyGemsminitest~>6.0Gemfile
RubyGemsminitest-reporters~>1.7Gemfile
RubyGemsrake~>13.2Gemfile
RubyGemsrubocop~>1.71Gemfile
RubyGemsrubocop-elegant>=0.0.20Gemfile
RubyGemsrubocop-minitest~>0.38Gemfile
RubyGemsrubocop-performance~>1.25Gemfile
RubyGemsrubocop-rake~>0.7Gemfile
RubyGemssimplecov~>0.22Gemfile
RubyGemssimplecov-cobertura~>3.0Gemfile
RubyGemswebmock~>3.23Gemfile
RubyGemsyard~>0.9Gemfile
All dependencies 55

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

RegistryPackageVersionRelation
RubyGemsminitest6.0.6direct
RubyGemsminitest-reporters1.8.0direct
RubyGemsrake13.4.2direct
RubyGemsrubocop1.90.0direct
RubyGemsrubocop-elegant0.5.1direct
RubyGemsrubocop-minitest0.40.0direct
RubyGemsrubocop-performance1.27.0direct
RubyGemsrubocop-rake0.7.1direct
RubyGemssimplecov0.22.0direct
RubyGemssimplecov-cobertura3.1.0direct
RubyGemswebmock3.26.3direct
RubyGemsyard0.9.45direct
RubyGemsaddressable2.9.0indirect
RubyGemsansi1.6.0indirect
RubyGemsast2.4.3indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsbuilder3.3.0indirect
RubyGemsconcurrent-ruby1.3.7indirect
RubyGemscrack1.0.1indirect
RubyGemsdocile1.4.1indirect
RubyGemsdrb2.2.3indirect
RubyGemsdry-core1.2.0indirect
RubyGemsdry-inflector1.3.1indirect
RubyGemsdry-logic1.6.0indirect
RubyGemsdry-struct1.8.1indirect
RubyGemsdry-types1.9.1indirect
RubyGemsfaraday2.14.3indirect
RubyGemsfaraday-multipart1.2.0indirect
RubyGemsfaraday-net_http3.4.4indirect
RubyGemshashdiff1.2.1indirect
RubyGemsice_nine0.11.2indirect
RubyGemsjson2.21.2indirect
RubyGemslanguage_server-protocol3.17.0.6indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsmultipart-post2.4.1indirect
RubyGemsnet-http0.9.1indirect
RubyGemsparallel2.1.0indirect
RubyGemsparser3.3.12.0indirect
RubyGemsprism1.9.0indirect
RubyGemspublic_suffix7.0.5indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsregexp_parser2.12.0indirect
RubyGemsrexml3.4.4indirect
RubyGemsrubocop-ast1.50.0indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemssimplecov-html0.13.2indirect
RubyGemssimplecov_json_formatter0.1.4indirect
RubyGemstelegram-bot-rubyindirect
RubyGemstelegram-bot-ruby1.0.0indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemsuri1.1.1indirect
RubyGemszeitwerk2.8.2indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 54 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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.34.0 — full methodology · metrics wiki.

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