Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-16 13:35 UTC

cataclysmbn / Cataclysm-BN

Cataclysm: Bright Nights: A fork/variant of Cataclysm:DDA by CleverRaven with a mod registry at https://mods.cataclysmbn.org/

C++Custom license★ 1,307 stars⑂ 515 forkssince Sep 2014View on GitHub ↗
KindMobile applicationDesktop applicationhow this is determined

cataclysmbn/Cataclysm-BN holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Engineering Quality (100/100) and lowest on Security (28/100). It was last updated today. 7 contributors account for most of its recent work.

34
overall / 100
At Risk

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.

34
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 77 is calibrated to 91 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 50% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

46 followers8 public repossince Sep 2017

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

Metrics by category

Vitality

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

96Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recency — last push 0 days ago
36/36Commit cadence — 52/52 weeks with commits
18/18Commit volume — 2,514 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year2,514
human_commit_share1
days_since_last_push0
active_weeks_last_year52
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~1 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tag2026-11-16
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases1

Community & Adoption

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

75Good · 17% of overall
How it's scored
50.5/60Stars — 1,307 stars
22.6/25Forks — 515 forks
8.7/15Watchers — 38 watchers
Inputs used
forks515
stars1,307
watchers38
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes

Sustainability & Governance

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

77Good · 23% of overall
How it's scored
51.3/54Bus factor — 7 contributor(s) cover half of all commits
20.3/22.5Commit distribution — top contributor authored 10% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 9 contributing companies or organizations
Inputs used
bus_factor7
contributors_sampled99
top_contributor_share0.099
How it's scored
27.9/42Issue resolution — 66% of issues closed
27.9/30PR acceptance — 7,184/7,723 decided PRs merged
4.3/13Newcomer PR acceptance — 1/3 first-time contributors' PRs merged in 30d
12/15OpenSSF Scorecard: Code-Review — Found 13/15 approved changesets -- score normalized to 8
Inputs used
merged_prs7,184
open_issues950
closed_issues1,875
prs_merged_7d51
prs_decided_7d57
prs_merged_30d54
prs_decided_30d60
issue_closed_ratio0.664
closed_unmerged_prs539
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d3
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
12/25Owner reach — 46 followers of cataclysmbn
18.9/25Track record — 8 public repos, account ~9 yr old
Inputs used
followers46
owner_typeOrganization
is_verifiedno
owner_logincataclysmbn
public_repos8
account_age_days3,345

Engineering Quality

Are baseline engineering and documentation practices in place?

100Exceptional · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows — 16 workflow(s)
24/24Tests present
16/16Linter config
9.6/9.6Pre-commit hooks
6.4/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_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://docs.cataclysmbn.org
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicsgame, c-plus-plus, zombies, roguelike, cataclysm, sci-fi, survival
has_wikiyes
homepagehttps://docs.cataclysmbn.org
docs_sitehttps://docs.cataclysmbn.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

28At Risk · 16% of overall
How it's scored
6/7.5Binary-Artifacts — binaries present in source code
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
6/7.5Code-Review — Found 13/15 approved changesets -- score normalized to 8
2.5/2.5Contributors — project has 9 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.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.6
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier50
security_posture_after_multiplier28
security_posture_before_jurisdiction56
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 50% multiplier and gives Security posture an At risk ceiling of 34.

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.

84Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes5,780
How it's scored
18/18One-command bootstrap — justfile
22/22Automated tests
11/11Lint / format config
11/11Static type checking — C++ (statically typed)
0/10Reproducible environment
10/10Demonstrated agent practice — 30 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
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_filesjustfile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.3
toolchain_manifestsandroid/app/build.gradle.kts, android/build.gradle.kts
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — C++ (statically typed)
51.4/55Manageable file sizes — 90/1,390 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes973,137
source_files_sampled1,390
oversized_source_files90
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples, recipes
Inputs used
example_dirsexamples, recipes
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

1,307GitHub stars
99contributors
2,514commits, last 12 months
0days since last push
100releases
7bus factor
950open issues
Mavenpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 515 ⇿
0Stars
515Forks
97Releases

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.

0100200300400500600501212017-102022-042026-11
Major 0Minor 1Patch 0

Each point covers 9 days.

OpenSSF Scorecard 5.6 / 10
5.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-11-16 13:34 UTC

8Binary-Artifactsbinaries present in source code
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
8Code-ReviewFound 13/15 approved changesets -- score normalized to 8
10Contributorsproject has 9 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 0

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

RegistryPackageVersionRelation
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies to assess

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.