Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 19:30 UTC

getstackit / stackit

Stackit is a Go-based CLI tool for managing stacked changes in Git repositories. It helps developers work with dependent branches (a "stack") by tracking branch relationships, automating rebases across the stack, and submitting connected pull requests.

GoMIT★ 32 stars⑂ 1 forksince Dec 2025View on GitHub ↗
KindCommand-line toolhow this is determined

getstackit/stackit holds a health index of 71 out of 100, placing it in the Good band. It scores highest on AI Readiness (92/100) and lowest on Security (26/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

getstackitOrganization
2 followers7 public repossince Dec 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/getstackit/stackitv0.27.1-771 day ago

Metrics by category

Vitality

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

91Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
27/36Commit cadence — 39/52 weeks with commits
18/18Commit volume — 2,724 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year2,724
human_commit_share1
days_since_last_push0
active_weeks_last_year39
How it's scored
27/27Ships releases — 77 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~8.3 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count77
latest_release_tagv0.27.1
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases8.3

Community & Adoption

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

45Weak · 17% of overall
How it's scored
24.2/60Stars — 32 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars32
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

54Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.5/22.5Commit distribution — top contributor authored 93% of commits
4.1/13.5Contributor breadth — 3 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.934
How it's scored
37.4/42Issue resolution — 89% of issues closed
27.8/30PR acceptance — 1,535/1,657 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/15 approved changesets -- score normalized to 0
Inputs used
merged_prs1,535
open_issues8
closed_issues65
prs_merged_7d15
prs_decided_7d16
prs_merged_30d57
prs_decided_30d60
issue_closed_ratio0.89
closed_unmerged_prs122
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
30/30Ownership backing — organization-owned
0/20Verified domain
3.4/25Owner reach — 2 followers of getstackit
8/25Track record — 7 public repos, account ~0 yr old
Inputs used
followers2
owner_typeOrganization
is_verifiedno
owner_logingetstackit
public_repos7
account_age_days259

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 1 days ago
20/20Version history — 77 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/getstackit/stackit
ecosystemsgo
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — .golangci.yml, eslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 15 out of 15 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://getstackit.github.io/stackit/
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicsclaude, git, stacking
has_wikino
homepagehttps://getstackit.github.io/stackit/
docs_sitehttps://getstackit.github.io/stackit/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

26At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 15 out of 15 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/15 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 40 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate2.6
Excluded from scoring (no data or not applicable): Branch-Protection. 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.

92Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md, apps/web/AGENTS.md, apps/web/CLAUDE.md, doc/src/integrations/claude.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://getstackit.github.io/stackit/llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://getstackit.github.io/stackit/llms.txt
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md, apps/web/AGENTS.md, apps/web/CLAUDE.md, doc/src/integrations/claude.md
agent_instruction_max_bytes9,139
How it's scored
18/18One-command bootstrap — mise.toml
22/22Automated tests
11/11Lint / format config — .golangci.yml, eslint.config.mjs
11/11Static type checking — apps/web/tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 17 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum, pnpm-lock.yaml, uv.lock
has_dockerfileyes
typed_languageyes
bootstrap_filesmise.toml
has_devcontainerno
has_linter_configyes
typecheck_configsapps/web/tsconfig.json
agent_commit_share0.17
toolchain_manifestsgo.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Go (statically typed)
54.9/55Manageable file sizes — 1/953 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes70,798
source_files_sampled953
oversized_source_files1

Key facts

32GitHub stars
3contributors
2,724commits, last 12 months
0days since last push
77releases
1bus factor
8open issues
Go, npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 2.6 / 10
2.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-09-13 19:29 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
10CI-Tests15 out of 15 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/15 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
0Dangerous-Workflowdangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
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
0Vulnerabilities40 existing vulnerabilities detected
Direct dependencies 21
RegistryPackageVersion constraintManifest
Gocharm.land/bubbles/v2v2.2.1go.mod
Gocharm.land/bubbletea/v2v2.0.9go.mod
Gocharm.land/glamour/v2v2.0.1go.mod
Gocharm.land/lipgloss/v2v2.0.6go.mod
Gogithub.com/anmitsu/go-shlexv0.0.0-20200514113438-38f4b401e2bego.mod
Gogithub.com/bradleyfalzon/ghinstallation/v2v2.19.0go.mod
Gogithub.com/fsnotify/fsnotifyv1.10.1go.mod
Gogithub.com/golang-migrate/migrate/v4v4.19.1go.mod
Gogithub.com/google/go-github/v91v91.0.0go.mod
Gogithub.com/jackc/pgx/v5v5.10.0go.mod
Gogithub.com/mattn/go-isattyv0.0.24go.mod
Gogithub.com/sabhiram/go-gitignorev0.0.0-20210923224102-525f6e181f06go.mod
Gogithub.com/sahilm/fuzzyv0.1.3go.mod
Gogithub.com/spf13/cobrav1.10.2go.mod
Gogithub.com/stretchr/testifyv1.12.1go.mod
Gogithub.com/testcontainers/testcontainers-go/modules/postgresv0.44.0go.mod
Gogolang.org/x/oauth2v0.36.0go.mod
Gogolang.org/x/syncv0.22.0go.mod
Gogithub.com/charmbracelet/x/ansiv0.11.8go.mod
Gogopkg.in/natefinch/lumberjack.v2v2.2.1go.mod
Gogopkg.in/yaml.v3v3.0.1go.mod
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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