Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 23:13 UTC

bannable / paseto

Ruby implementation of PASETO tokens

RubyMIT★ 23 stars⑂ 2 forkssince Nov 2022View on GitHub ↗

bannable/paseto holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (76/100) and lowest on Sustainability & Governance (41/100). It was last updated 48 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Joe TrubaPersonal account
14 followers25 public repossince Apr 2012

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
RubyGemsruby-paseto0.2.0-4514 days ago

Metrics by category

Vitality

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

44Weak · 21% of overall
How it's scored
18/36Push recency — last push 48 days ago
2.1/36Commit cadence — 3/52 weeks with commits
11.5/18Commit volume — 18 commits in the last year
7/10OpenSSF Scorecard: Maintained — 0 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year18
human_commit_share0.21
days_since_last_push48
active_weeks_last_year3
How it's scored
27/27Ships releases — 4 releases published
7.2/36Release recency — latest release 514 days ago
12.6/27Release cadence — a release every ~252.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count4
latest_release_tagv0.2.0
releases_from_tagsno
days_since_latest_release514
mean_days_between_releases252.8
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?

52Moderate · 17% of overall
How it's scored
21.8/60Stars — 23 stars
0/25Forks — 2 forks
0/15Watchers — 2 watchers
Inputs used
forks2
stars23
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
64.9/80Total downloads — 1,763,698 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesruby-paseto
dependents—
ecosystemsrubygems
total_downloads1,763,698
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?

41Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.2/22.5Commit distribution — top contributor authored 99% of commits
5.4/13.5Contributor breadth — 4 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.99
How it's scored
15/42Issue resolution — 36% of issues closed
16/30PR acceptance — 138/258 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 2/17 approved changesets -- score normalized to 1
Inputs used
merged_prs138
open_issues9
closed_issues5
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.357
closed_unmerged_prs120
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
8.5/25Owner reach — 14 followers of bannable
22.3/25Track record — 25 public repos, account ~14 yr old
Inputs used
followers14
owner_typeUser
is_verified—
owner_loginbannable
public_repos25
account_age_days5,257
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
14/35Publish recency — latest publish 514 days ago
12/20Version history — 4 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesruby-paseto
ecosystemsrubygems
any_deprecatedno
min_days_since_publish514

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests — 17 out of 27 merged PRs checked by a CI test -- score normalized to 6
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 site — https://github.com/bannable/paseto
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicsencryption, libsodium, paseto, ruby, security, signature, token
has_wikiyes
homepage—
docs_sitehttps://github.com/bannable/paseto
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

62Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
1.5/2.5CI-Tests — 17 out of 27 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 2/17 approved changesets -- score normalized to 1
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
5.2/7.5Maintained — 0 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 7
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
2.5/5SAST — SAST tool is not run on all commits -- score normalized to 5
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5Vulnerabilities — 15 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.9
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: oj 3.17.0 (high 7.5)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories15
affected_packages3
assessed_packages78
unassessed_packages4
affected_by_severityhigh 2, low 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 78 resolved dependencies against OSV. 4 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.

60Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://libsodium.gitbook.io/llms.txt)
40/40Legible commit history — 16 of 21 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://libsodium.gitbook.io/llms.txt
legible_history_share0.762
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 environment — lockfile
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 79 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.02
toolchain_manifests—
dependency_bot_commit_share0.79
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/101 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes18,478
source_files_sampled101
oversized_source_files0

Key facts

23GitHub stars
4contributors
18commits, last 12 months
48days since last push
4releases
1bus factor
9open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
1Releases

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.

111222212025-042025-062025-08
Major 0Minor 1Patch 0
OpenSSF Scorecard 5.9 / 10
5.9aggregate

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-11 23:13 UTC

10Binary-Artifactsno binaries found in the repo
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
6CI-Tests17 out of 27 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/17 approved changesets -- score normalized to 1
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
7Maintained0 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 7
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
5SASTSAST tool is not run on all commits -- score normalized to 5
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities15 existing vulnerabilities detected
Direct dependencies 14
RegistryPackageVersion constraintManifest
RubyGemsoj—Gemfile
RubyGemsparallel_tests—Gemfile
RubyGemsrake~> 13Gemfile
RubyGemsreek—Gemfile
RubyGemsrspec~> 3Gemfile
RubyGemsrspec_junit_formatter—Gemfile
RubyGemsrubocop~> 1.75Gemfile
RubyGemsrubocop-performance~> 1.25Gemfile
RubyGemsrubocop-rspec~> 3.5Gemfile
RubyGemsrubocop-sorbet~> 0.10Gemfile
RubyGemssimplecov~> 0Gemfile
RubyGemssimplecov_json_formatter—Gemfile
RubyGemssorbet~> 0Gemfile
RubyGemstimecop~> 0Gemfile
All dependencies 82

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

RegistryPackageVersionRelation
RubyGemsoj3.17.0direct
RubyGemsparallel_tests5.7.0direct
RubyGemsrake13.4.2direct
RubyGemsreek6.5.0direct
RubyGemsrspec3.13.2direct
RubyGemsrspec_junit_formatter0.6.0direct
RubyGemsrubocop1.86.1direct
RubyGemsrubocop-performance1.26.1direct
RubyGemsrubocop-rspec3.9.0direct
RubyGemsrubocop-sorbet0.12.0direct
RubyGemssimplecov0.22.0direct
RubyGemssimplecov_json_formatter0.1.4direct
RubyGemssorbet0.6.13160direct
RubyGemstimecop0.9.11direct
RubyGemsast2.4.3indirect
RubyGemsbenchmark0.5.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemscommander5.0.0indirect
RubyGemsconcurrent-ruby1.3.6indirect
RubyGemsdate3.5.1indirect
RubyGemsdebug1.11.1indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemsdocile1.4.0indirect
RubyGemsdry-configurable1.3.0indirect
RubyGemsdry-core1.2.0indirect
RubyGemsdry-inflector1.3.1indirect
RubyGemsdry-initializer3.2.0indirect
RubyGemsdry-logic1.6.0indirect
RubyGemsdry-schema1.16.0indirect
RubyGemsdry-types1.9.1indirect
RubyGemserb6.0.4indirect
RubyGemserubi1.13.1indirect
RubyGemshighline3.0.1indirect
RubyGemsio-console0.8.2indirect
RubyGemsirb1.17.0indirect
RubyGemsjson2.19.3indirect
RubyGemslanguage_server-protocol3.17.0.5indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsmulti_json—indirect
RubyGemsmulti_json1.20.1indirect
RubyGemsnetrc0.11.0indirect
RubyGemsopenssl—indirect
RubyGemsopenssl4.0.1indirect
RubyGemsostruct0.6.3indirect
RubyGemsparallel2.1.0indirect
RubyGemsparlour9.1.2indirect
RubyGemsparser3.3.11.1indirect
RubyGemspp0.6.3indirect
RubyGemsprettyprint0.2.0indirect
RubyGemsprism1.9.0indirect
RubyGemspsych5.3.1indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrbi0.3.10indirect
RubyGemsrbs4.0.2indirect
RubyGemsrdoc7.2.0indirect
RubyGemsregexp_parser2.12.0indirect
RubyGemsreline0.6.3indirect
RubyGemsrequire-hooks0.3.0indirect
RubyGemsrexml3.4.4indirect
RubyGemsrspec-core3.13.6indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.8indirect
RubyGemsrspec-support3.13.7indirect
RubyGemsrubocop-ast1.49.1indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsrubydex0.1.0.beta13indirect
RubyGemssimplecov-html0.12.3indirect
RubyGemssorbet-runtime—indirect
RubyGemssorbet-runtime0.6.13160indirect
RubyGemssorbet-static0.6.13160indirect
RubyGemssorbet-static-and-runtime0.6.13160indirect
RubyGemsspoom1.7.13indirect
RubyGemsstringio3.2.0indirect
RubyGemstapioca0.19.1indirect
RubyGemsthor1.5.0indirect
RubyGemstsort0.2.0indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemszeitwerk—indirect
RubyGemszeitwerk2.7.5indirect
Dependency advisories 3

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

PackageVersionRelationSeverityAdvisoriesFixed in
oj3.17.0directhigh113.17.3
concurrent-ruby1.3.6indirecthigh31.3.7
json2.19.3indirectlow12.19.9

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 — RubyGems.