Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 04:22 UTC

lugassawan / rimba

Git worktree manager CLI — automate branch naming, dependency sharing, hooks, and parallel development workflows

GoMIT★ 3 stars⑂ 4 forkssince Feb 2026View on GitHub ↗
KindCommand-line toolhow this is determined

lugassawan/rimba holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on AI Readiness (87/100) and lowest on Community & Adoption (48/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

80
overall / 100
Excellent

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.

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

Ownership

Lugas SeptiawanPersonal account
3 followers50 public repossince Mar 2015

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
Gogithub.com/lugassawan/rimbav1.10.1-243 days ago

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
12.5/36Commit cadence18/52 weeks with commits
18/18Commit volume255 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year255
human_commit_share
days_since_last_push2
active_weeks_last_year18
How it's scored
27/27Ships releases24 releases published
36/36Release recencylatest release 2 days ago
27/27Release cadencea release every ~8.1 days
1/10OpenSSF Scorecard: Signed-Releases1 out of the last 5 releases have a total of 1 signed artifacts.
Inputs used
releases_count24
latest_release_tagv1.10.1
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases8.1

Community & Adoption

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

48Weak · 17% of overall
How it's scored
4.9/60Stars3 stars
4/25Forks4 forks
0/15Watchers0 watchers
Inputs used
forks4
stars3
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/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_templateyes

Sustainability & Governance

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

59Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.4/22.5Commit distributiontop contributor authored 89% of commits
6.8/13.5Contributor breadth5 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.894
How it's scored
41.7/42Issue resolution99% of issues closed
29.5/30PR acceptance254/258 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/28 approved changesets -- score normalized to 0
Inputs used
merged_prs254
open_issues1
closed_issues149
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.993
closed_unmerged_prs4
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.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
4.3/25Owner reach3 followers of lugassawan
24.4/25Track record50 public repos, account ~11 yr old
Inputs used
followers3
owner_typeUser
is_verified
owner_loginlugassawan
public_repos50
account_age_days4,151
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 go
35/35Publish recencylatest publish 3 days ago
20/20Version history24 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/lugassawan/rimba
ecosystemsgo
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
16/16Linter config.golangci.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 out of 30 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 sitehttps://lugassawan.github.io/rimba/
10/10Repository description
10/10Topics12 topics
0/10Wiki
Inputs used
topicsbranch-management, cli, developer-productivity, developer-tools, git, git-worktree, git-worktrees, go, golang, parallel-development, workflow-automation, worktree
has_wikino
homepagehttps://lugassawan.github.io/rimba/
docs_sitehttps://lugassawan.github.io/rimba/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

58Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests30 out of 30 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 1/28 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
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 30 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
2.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0.8/7.5Signed-Releases1 out of the last 5 releases have a total of 1 signed artifacts.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
5.2/7.5Vulnerabilities3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.8
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.

87Excellent · 4% of overall
How it's scored
45/45Agent instructions.cursor/rules/rimba.mdc, .github/copilot-instructions.md, AGENTS.md, GEMINI.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files.cursor/rules/rimba.mdc, .github/copilot-instructions.md, AGENTS.md, GEMINI.md
agent_instruction_max_bytes4,167
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
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 environmentlockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
5/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock, go.sum
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
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.
How it's scored
45/45Type-checkable codeGo (statically typed)
55/55Manageable file sizes0/368 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes45,889
source_files_sampled368
oversized_source_files0

Key facts

3GitHub stars
5contributors
255commits, last 12 months
2days since last push
24releases
1bus factor
1open issues
Go, RubyGemspackage ecosystems

More detail

OpenSSF Scorecard 5.8 / 10
5.8aggregate

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 04:22 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-Tests30 out of 30 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 1/28 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
1Signed-Releases1 out of the last 5 releases have a total of 1 signed artifacts.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
RubyGemsjekyll~> 4.4docs/Gemfile
RubyGemsjust-the-docs0.12.0docs/Gemfile
RubyGemsjekyll-sitemapdocs/Gemfile
RubyGemswebrick~> 1.8docs/Gemfile
Gogithub.com/google/shlexv0.0.0-20191202100458-e7afc7fbc510go.mod
Gogithub.com/mark3labs/mcp-gov0.55.1go.mod
Gogithub.com/pelletier/go-toml/v2v2.4.3go.mod
Gogithub.com/spf13/cobrav1.10.2go.mod
Gogithub.com/spf13/pflagv1.0.10go.mod
All dependencies 59

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

RegistryPackageVersionRelation
Gogithub.com/google/shlexv0.0.0-20191202100458-e7afc7fbc510direct
Gogithub.com/mark3labs/mcp-gov0.55.1direct
Gogithub.com/pelletier/go-toml/v2v2.4.3direct
Gogithub.com/spf13/cobrav1.10.2direct
Gogithub.com/spf13/pflagv1.0.10direct
RubyGemsjekyll4.4.1direct
RubyGemsjekyll-sitemap1.4.0direct
RubyGemsjust-the-docs0.12.0direct
RubyGemswebrick1.9.2direct
Gogithub.com/google/jsonschema-gov0.4.2indirect
Gogithub.com/google/uuidv1.6.0indirect
Gogithub.com/inconshreveable/mousetrapv1.1.0indirect
Gogithub.com/santhosh-tekuri/jsonschema/v6v6.0.2indirect
Gogithub.com/spf13/castv1.10.0indirect
Gogithub.com/yosida95/uritemplate/v3v3.0.2indirect
Gogolang.org/x/textv0.38.0indirect
RubyGemsaddressable2.9.0indirect
RubyGemsbase640.3.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemscolorator1.1.0indirect
RubyGemsconcurrent-ruby1.3.6indirect
RubyGemscsv3.3.5indirect
RubyGemsem-websocket0.5.3indirect
RubyGemseventmachine1.2.7indirect
RubyGemsffi1.17.4indirect
RubyGemsforwardable-extended2.6.0indirect
RubyGemsgoogle-protobuf4.35.1indirect
RubyGemshttp_parser.rb0.8.1indirect
RubyGemsi18n1.14.8indirect
RubyGemsjekyll-include-cache0.2.1indirect
RubyGemsjekyll-sass-converter3.1.0indirect
RubyGemsjekyll-seo-tag2.9.0indirect
RubyGemsjekyll-watch2.2.1indirect
RubyGemsjson2.19.9indirect
RubyGemskramdown2.5.2indirect
RubyGemskramdown-parser-gfm1.1.0indirect
RubyGemsliquid4.0.4indirect
RubyGemslisten3.10.0indirect
RubyGemslogger1.7.0indirect
RubyGemsmercenary0.4.0indirect
RubyGemspathutil0.16.2indirect
RubyGemspublic_suffix7.0.5indirect
RubyGemsrake13.4.2indirect
RubyGemsrb-fsevent0.11.2indirect
RubyGemsrb-inotify0.11.1indirect
RubyGemsrexml3.4.4indirect
RubyGemsrouge4.7.0indirect
RubyGemssafe_yaml1.0.5indirect
RubyGemssass-embedded1.101.0indirect
RubyGemssass-embedded1.101.0-aarch64-linux-androidindirect
RubyGemssass-embedded1.101.0-arm-linux-androideabiindirect
RubyGemssass-embedded1.101.0-arm-linux-gnueabihfindirect
RubyGemssass-embedded1.101.0-arm-linux-musleabihfindirect
RubyGemssass-embedded1.101.0-riscv64-linux-androidindirect
RubyGemssass-embedded1.101.0-riscv64-linux-gnuindirect
RubyGemssass-embedded1.101.0-riscv64-linux-muslindirect
RubyGemssass-embedded1.101.0-x86_64-linux-androidindirect
RubyGemsterminal-table3.0.2indirect
RubyGemsunicode-display_width2.6.0indirect
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.11.0 — full methodology · metrics wiki.

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