Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 01:05 UTC

riftdata / rift

Instant, copy-on-write database branches for Postgres. Self-hosted. Every PR gets its own database.

GoApache-2.0★ 1 star⑂ 0 forkssince Jan 2026View on GitHub ↗
KindCommand-line toolNetwork serviceTerminal interfaceLibraryhow this is determined

riftdata/rift holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on AI Readiness (82/100) and lowest on Community & Adoption (31/100). It was last updated 121 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

Rift DataOrganization
0 followers3 public repossince Jan 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Gogithub.com/riftdata/riftv0.1.51-20200 days ago
npm@rift-data/cli0.0.42286201 days agogitgithubbranchdatabasedbpostgrespg

Metrics by category

Vitality

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

42Weak · 21% of overall
How it's scored
9.9/36Push recencylast push 121 days ago
0.7/36Commit cadence1/52 weeks with commits
13.6/18Commit volume32 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_year32
human_commit_share1
days_since_last_push121
active_weeks_last_year1
How it's scored
27/27Ships releases12 releases published
16.2/36Release recencylatest release 200 days ago
27/27Release cadencea release every ~0.1 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count12
latest_release_tagv0.1.51
releases_from_tagsno
days_since_latest_release200
mean_days_between_releases0.1

Community & Adoption

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

31At Risk · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
0/15Watchers1 watchers
Inputs used
forks0
stars1
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
19.5/80Monthly downloads28 downloads/month across go, npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesgithub.com/riftdata/rift, @rift-data/cli
dependents
ecosystemsgo, npm
total_downloads
monthly_downloads28
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?

40Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolutionno issues or no data
15/30PR acceptance1/2 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs1
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
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): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
0/25Owner reach0 followers of riftdata
5.5/25Track record3 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verified
owner_loginriftdata
public_repos3
account_age_days202
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable2 package(s) on go, npm
26/35Publish recencylatest publish 200 days ago
20/20Version history20 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/riftdata/rift, @rift-data/cli
ecosystemsgo, npm
any_deprecatedno
min_days_since_publish200

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter config.golangci.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests1 out of 1 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://riftdata.io
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_sitehttps://riftdata.io
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

47Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
4.5/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests1 out of 1 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/30 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update 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
5/5Packagingpackaging workflow detected
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-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
3.8/7.5Vulnerabilities5 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate3.4

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages5
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:@rift-data/cli@0.0.42 runtime dependency closure — what installing the published package pulls in — 5 packages. 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.

82Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history26 of 32 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.812
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes7,482
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config.golangci.yml
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 32
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifestsgo.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeGo (statically typed)
55/55Manageable file sizes0/38 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes26,692
source_files_sampled38
oversized_source_files0

Key facts

1GitHub stars
1contributors
32commits, last 12 months
121days since last push
12releases
1bus factor
0open issues
Go, npmpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 3.4 / 10
3.4aggregate

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-22 01:04 UTC

10Binary-Artifactsno binaries found in the repo
6Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests1 out of 1 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/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update 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
10Packagingpackaging workflow 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
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
5Vulnerabilities5 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
Gogithub.com/charmbracelet/bubblesv0.21.1-0.20250623103423-23b8fd6302d7go.mod
Gogithub.com/charmbracelet/bubbleteav1.3.10go.mod
Gogithub.com/charmbracelet/huhv0.8.0go.mod
Gogithub.com/charmbracelet/lipglossv1.1.0go.mod
Gogithub.com/charmbracelet/logv0.4.2go.mod
Gogithub.com/jackc/pgx/v5v5.8.0go.mod
Gogithub.com/pganalyze/pg_query_go/v6v6.2.2go.mod
Gogithub.com/spf13/cobrav1.10.2go.mod
Gogithub.com/spf13/viperv1.21.0go.mod
Gogopkg.in/yaml.v3v3.0.1go.mod
All dependencies 58

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

RegistryPackageVersionRelation
Gogithub.com/charmbracelet/bubblesv0.21.1-0.20250623103423-23b8fd6302d7direct
Gogithub.com/charmbracelet/bubbleteav1.3.10direct
Gogithub.com/charmbracelet/huhv0.8.0direct
Gogithub.com/charmbracelet/lipglossv1.1.0direct
Gogithub.com/charmbracelet/logv0.4.2direct
Gogithub.com/jackc/pgx/v5v5.8.0direct
Gogithub.com/pganalyze/pg_query_go/v6v6.2.2direct
Gogithub.com/spf13/cobrav1.10.2direct
Gogithub.com/spf13/viperv1.21.0direct
Gogopkg.in/yaml.v3v3.0.1direct
Gogithub.com/atotto/clipboardv0.1.4indirect
Gogithub.com/aymanbagabas/go-osc52/v2v2.0.1indirect
Gogithub.com/catppuccin/gov0.3.0indirect
Gogithub.com/charmbracelet/colorprofilev0.4.1indirect
Gogithub.com/charmbracelet/harmonicav0.2.0indirect
Gogithub.com/charmbracelet/x/ansiv0.11.4indirect
Gogithub.com/charmbracelet/x/cellbufv0.0.14indirect
Gogithub.com/charmbracelet/x/exp/stringsv0.0.0-20240722160745-212f7b056ed0indirect
Gogithub.com/charmbracelet/x/termv0.2.2indirect
Gogithub.com/clipperhouse/displaywidthv0.8.0indirect
Gogithub.com/clipperhouse/stringishv0.1.1indirect
Gogithub.com/clipperhouse/uax29/v2v2.4.0indirect
Gogithub.com/dustin/go-humanizev1.0.1indirect
Gogithub.com/erikgeiser/coninputv0.0.0-20211004153227-1c3628e74d0findirect
Gogithub.com/fsnotify/fsnotifyv1.9.0indirect
Gogithub.com/go-logfmt/logfmtv0.6.0indirect
Gogithub.com/go-viper/mapstructure/v2v2.5.0indirect
Gogithub.com/inconshreveable/mousetrapv1.1.0indirect
Gogithub.com/jackc/pgpassfilev1.0.0indirect
Gogithub.com/jackc/pgservicefilev0.0.0-20240606120523-5a60cdf6a761indirect
Gogithub.com/jackc/puddle/v2v2.2.2indirect
Gogithub.com/lucasb-eyer/go-colorfulv1.3.0indirect
Gogithub.com/mattn/go-isattyv0.0.20indirect
Gogithub.com/mattn/go-localereaderv0.0.1indirect
Gogithub.com/mattn/go-runewidthv0.0.19indirect
Gogithub.com/mitchellh/hashstructure/v2v2.0.2indirect
Gogithub.com/muesli/ansiv0.0.0-20230316100256-276c6243b2f6indirect
Gogithub.com/muesli/cancelreaderv0.2.2indirect
Gogithub.com/muesli/termenvv0.16.0indirect
Gogithub.com/pelletier/go-toml/v2v2.2.4indirect
Gogithub.com/rivo/unisegv0.4.7indirect
Gogithub.com/sagikazarmark/locaferov0.12.0indirect
Gogithub.com/spf13/aferov1.15.0indirect
Gogithub.com/spf13/castv1.10.0indirect
Gogithub.com/spf13/pflagv1.0.10indirect
Gogithub.com/subosito/gotenvv1.6.0indirect
Gogithub.com/xo/terminfov0.0.0-20220910002029-abceb7e1c41eindirect
Gogo.yaml.in/yaml/v3v3.0.4indirect
Gogolang.org/x/expv0.0.0-20231006140011-7918f672742dindirect
Gogolang.org/x/syncv0.19.0indirect
Gogolang.org/x/sysv0.40.0indirect
Gogolang.org/x/textv0.33.0indirect
Gogoogle.golang.org/protobufv1.36.11indirect
npm@rift-data/cli-darwin-arm640.0.1indirect
npm@rift-data/cli-darwin-x640.0.1indirect
npm@rift-data/cli-linux-arm640.0.1indirect
npm@rift-data/cli-linux-x640.0.1indirect
npm@rift-data/cli-win32-x640.0.1indirect
Dependency advisories 0

Installing npm:@rift-data/cli@0.0.42 pulls in 5 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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 statisticsGo, npm.