Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-17 17:39 UTC

galtzo-floss / timecop-rspec

⌚️ Timecop::Rspec provides Timecop time-machines for RSpec that allow you to time-travel test examples, context/describes, and/or your entire test suite.

RubyMIT★ 4 stars⑂ 0 forkssince Aug 2025View on GitHub ↗
KindLibraryhow this is determined
#floss#rspec#rubygem#timecop

galtzo-floss/timecop-rspec holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (90/100) and lowest on AI Readiness (34/100). It was last updated 28 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Galtzo Open SourceOrganization
5 followers60 public repossince May 2025

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemstimecop-rspec1.0.3-4330 days ago

Metrics by category

Vitality

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

62Moderate · 21% of overall

Development activity

51Moderate
How it's scored
28.8/36Push recency — last push 28 days ago
4.8/36Commit cadence — 7/52 weeks with commits
17.8/18Commit volume — 94 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year94
human_commit_share—
days_since_last_push28
active_weeks_last_year7

Release discipline

78Good
How it's scored
27/27Ships releases — 2 releases published
16.2/36Release recency — latest release 333 days ago
27/27Release cadence — a release every ~0.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count2
latest_release_tagv1.0.1
releases_from_tagsno
days_since_latest_release333
mean_days_between_releases0.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?

49Weak · 17% of overall

Popularity & adoption

8Critical
How it's scored
7.7/60Stars — 4 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars4
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges—
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

63Moderate
How it's scored
50.7/80Total downloads — 76,017 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagestimecop-rspec
dependents—
ecosystemsrubygems
total_downloads76,017
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?

59Moderate · 23% of overall

Maintainer resilience (bus factor)

25At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.8/22.5Commit distribution — top contributor authored 92% of commits
4.1/13.5Contributor breadth — 3 contributors
10/10OpenSSF Scorecard: Contributors — project has 18 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.918

Issue & PR responsiveness

74Good
How it's scored
42/42Issue resolution — 100% of issues closed
22.5/30PR acceptance — 6/8 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/22 approved changesets -- score normalized to 0
Inputs used
merged_prs6
open_issues0
closed_issues1
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio1
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.

Ownership & stewardship

64Moderate
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
5.6/25Owner reach — 5 followers of galtzo-floss
15.3/25Track record — 60 public repos, account ~1 yr old
Inputs used
followers5
owner_typeOrganization
is_verified—
owner_logingaltzo-floss
public_repos60
account_age_days418
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

83Excellent
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
26/35Publish recency — latest publish 330 days ago
12/20Version history — 4 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagestimecop-rspec
ecosystemsrubygems
any_deprecatedno
min_days_since_publish330

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall

Engineering practices

84Excellent
How it's scored
24/24CI workflows — 16 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 4 out of 4 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

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://timecop-rspec.galtzo.com/
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsfloss, rspec, rubygem, timecop
has_wikiyes
homepagehttps://timecop-rspec.galtzo.com/
docs_sitehttps://timecop-rspec.galtzo.com/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

47Weak · 16% of overall

Security posture

47Weak
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 4 out of 4 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/22 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 18 contributing companies or organizations
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
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
4/5SAST — SAST tool detected but not run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 18 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.7
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.

34At Risk · 4% of overall

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no 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.

Verify loop (build / test / typecheck)

53Moderate
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
10/10Reproducible environment — devcontainer, lockfile
0/10Demonstrated agent practice — no data
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontaineryes
has_linter_configyes
typecheck_configs—
agent_commit_share—
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.

Code legibility for models

52Moderate
How it's scored
0/45Type-checkable code — Ruby without a type-check config
51.8/55Manageable file sizes — 1/17 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes93,868
source_files_sampled17
oversized_source_files1

Key facts

4GitHub stars
3contributors
94commits, last 12 months
28days since last push
2releases
1bus factor
0open issues
RubyGemspackage ecosystems

More detail

OpenSSF Scorecard 4.7 / 10
4.7aggregate

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 17:39 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests4 out of 4 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/22 approved changesets -- score normalized to 0
10Contributorsproject has 18 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
8SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities18 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
RubyGemsdebug>= 1.0.0Gemfile
RubyGemsgem_bench~> 2.0Gemfile
RubyGemspry~> 0.14Gemfile
RubyGemslogger—Gemfile
All dependencies 108

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

RegistryPackageVersionRelation
RubyGemsdebug1.11.0direct
RubyGemsgem_bench2.0.5direct
RubyGemslogger1.7.0direct
RubyGemspry0.15.2direct
RubyGemsansi1.5.0indirect
RubyGemsappraisal2—indirect
RubyGemsappraisal23.0.0indirect
RubyGemsast2.4.3indirect
RubyGemsbackports3.25.1indirect
RubyGemsbenchmark0.4.1indirect
RubyGemsbigdecimal3.2.2indirect
RubyGemsbundler-audit0.9.2indirect
RubyGemscoderay1.1.3indirect
RubyGemsconcurrent-ruby1.3.5indirect
RubyGemsdate3.4.1indirect
RubyGemsdelegate—indirect
RubyGemsdelegate0.4.0indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemsdiffy3.4.4indirect
RubyGemsdocile1.4.1indirect
RubyGemsdry-configurable1.3.0indirect
RubyGemsdry-core1.1.0indirect
RubyGemsdry-inflector1.2.0indirect
RubyGemsdry-initializer3.2.0indirect
RubyGemsdry-logic1.6.0indirect
RubyGemsdry-schema1.14.1indirect
RubyGemsdry-types1.8.3indirect
RubyGemserb—indirect
RubyGemserb5.0.2indirect
RubyGemsgitmoji-regex—indirect
RubyGemsgitmoji-regex1.0.3indirect
RubyGemsio-console0.8.1indirect
RubyGemsirb1.15.2indirect
RubyGemsjson2.13.2indirect
RubyGemskettle-soup-cover1.0.10indirect
RubyGemskramdown2.5.1indirect
RubyGemskramdown-parser-gfm1.1.0indirect
RubyGemslanguage_server-protocol3.17.0.5indirect
RubyGemslint_roller1.1.0indirect
RubyGemsmethod_source1.1.0indirect
RubyGemsnokogiri1.18.9indirect
RubyGemsostruct0.6.3indirect
RubyGemsparallel1.27.0indirect
RubyGemsparser3.3.9.0indirect
RubyGemspp0.6.2indirect
RubyGemsprettyprint0.2.0indirect
RubyGemsprism1.4.0indirect
RubyGemspsych5.2.6indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrake—indirect
RubyGemsrake13.3.0indirect
RubyGemsrdoc6.14.2indirect
RubyGemsreek6.5.0indirect
RubyGemsregexp_parser2.11.2indirect
RubyGemsreline0.6.2indirect
RubyGemsrexml3.4.1indirect
RubyGemsrspec—indirect
RubyGemsrspec3.13.1indirect
RubyGemsrspec-block_is_expected—indirect
RubyGemsrspec-block_is_expected1.0.6indirect
RubyGemsrspec-core3.13.5indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.5indirect
RubyGemsrspec-stubbed_env—indirect
RubyGemsrspec-stubbed_env1.0.4indirect
RubyGemsrspec-support3.13.5indirect
RubyGemsrspec_junit_formatter—indirect
RubyGemsrspec_junit_formatter0.6.0indirect
RubyGemsrubocop1.75.8indirect
RubyGemsrubocop-ast1.46.0indirect
RubyGemsrubocop-gradual0.3.6indirect
RubyGemsrubocop-lts0.1.1indirect
RubyGemsrubocop-md1.2.4indirect
RubyGemsrubocop-packaging0.6.0indirect
RubyGemsrubocop-performance1.25.0indirect
RubyGemsrubocop-rake0.7.1indirect
RubyGemsrubocop-rspec3.6.0indirect
RubyGemsrubocop-ruby1_81.0.7indirect
RubyGemsrubocop-shopify2.17.1indirect
RubyGemsrubocop-thread_safety0.7.3indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemssilent_stream—indirect
RubyGemssilent_stream1.0.11indirect
RubyGemssimplecov0.22.0indirect
RubyGemssimplecov-cobertura3.0.0indirect
RubyGemssimplecov-console0.9.4indirect
RubyGemssimplecov-html0.13.2indirect
RubyGemssimplecov-lcov0.8.0indirect
RubyGemssimplecov-rcov0.3.7indirect
RubyGemssimplecov_json_formatter0.1.4indirect
RubyGemsstandard1.50.0indirect
RubyGemsstandard-custom1.0.2indirect
RubyGemsstandard-performance1.8.0indirect
RubyGemsstandard-rubocop-lts1.0.10indirect
RubyGemsstone_checksums—indirect
RubyGemsstone_checksums1.0.0indirect
RubyGemsstringio3.1.7indirect
RubyGemsterminal-table4.0.0indirect
RubyGemsthor1.4.0indirect
RubyGemstimecop—indirect
RubyGemstimecop0.9.10indirect
RubyGemsunicode-display_width3.1.5indirect
RubyGemsunicode-emoji4.0.4indirect
RubyGemsversion_gem1.1.8indirect
RubyGemsyard0.9.37indirect
RubyGemsyard-relative_markdown_links0.5.0indirect
RubyGemszeitwerk2.7.3indirect
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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with galtzo-floss/timecop-rspec. Read them side by side →

83galtzo-floss/turbo_tests2🚀 Run RSpec tests on multiple cores. Like parallel_tests but with incremental summarized output. Originally extracted from the Discourse and Rubygems source code.Excellent78galtzo-floss/rspec-pending_for⏳️Mark specs pending or skipped for specific Ruby engine (e.g. MRI or JRuby) / version combinations | rangesGood78kettle-dev/kettle-test🍲 Setup a complete multi-core parallelized RSpec test harness, temporal manipulation, silent output testing, block expectations, etc.Good62infrablocks/rspec-terraformRSpec support for testing Terraform configurations.Moderate96rubocop/rubocop-rspecCode style checking for RSpec files.Exceptional90julianguyen/ifmeFree, open source mental health communication web app to share experiences with loved onesExcellent

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

How one result sits in the wider record: aggregate statistics — RubyGems.