Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 11:42 UTC

open-goal / jak-project

Reviving the language that brought us the Jak & Daxter Series

Common Lisp · C++ISC★ 3,506 stars⑂ 233 forkssince Aug 2020View on GitHub ↗
KindMobile applicationLibraryhow this is determined

open-goal/jak-project holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (93/100) and lowest on Security (53/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

OpenGOALOrganization · verified domain
487 followers11 public repossince Feb 2022

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?

90Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
25.6/36Commit cadence — 37/52 weeks with commits
18/18Commit volume — 229 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year229
human_commit_share0.99
days_since_last_push2
active_weeks_last_year37
How it's scored
27/27Ships releases — 88 releases published
36/36Release recency — latest release 18 days ago
27/27Release cadence — a release every ~36.9 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count88
latest_release_tagv0.3.6
releases_from_tagsno
days_since_latest_release18
mean_days_between_releases36.9

Community & Adoption

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

69Good · 17% of overall
How it's scored
57.5/60Stars — 3,506 stars
19.7/25Forks — 233 forks
9.2/15Watchers — 46 watchers
Inputs used
forks233
stars3,506
watchers46
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (ISC)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesapp.codacy.com, github.com, shields.io
has_pull_request_templateno

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
25.2/54Bus factor — 2 contributor(s) cover half of all commits
14.7/22.5Commit distribution — top contributor authored 35% of commits
13.5/13.5Contributor breadth — 71 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled71
top_contributor_share0.346
How it's scored
37.7/42Issue resolution — 90% of issues closed
28.3/30PR acceptance — 2,522/2,671 decided PRs merged
9/13Newcomer PR acceptance — 9/13 first-time contributors' PRs merged in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 21/30 approved changesets -- score normalized to 7
Inputs used
merged_prs2,522
open_issues166
closed_issues1,459
prs_merged_7d4
prs_decided_7d4
prs_merged_30d26
prs_decided_30d35
issue_closed_ratio0.898
closed_unmerged_prs149
first_time_authors_30d6
first_time_prs_merged_30d9
first_time_prs_decided_30d13
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
19.3/25Owner reach — 487 followers of open-goal
17/25Track record — 11 public repos, account ~4 yr old
Inputs used
followers487
owner_typeOrganization
is_verifiedyes
owner_loginopen-goal
public_repos11
account_age_days1,677

Engineering Quality

Are baseline engineering and documentation practices in place?

93Exceptional · 19% of overall
How it's scored
24/24CI workflows — 13 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.js, tox.ini
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 29 out of 30 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://opengoal.dev
10/10Repository description
10/10Topics — 6 topics
10/10Wiki
Inputs used
topicslisp, scheme, jak, jak-and-daxter, ps2, reverse-engineering
has_wikiyes
homepagehttps://opengoal.dev
docs_sitehttps://opengoal.dev
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

53Moderate · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — no data
2.2/2.5CI-Tests — 29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-Review — Found 21/30 approved changesets -- score normalized to 7
2.5/2.5Contributors — project has 6 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 10 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
0/7.5Vulnerabilities — 86 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. 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.

76Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, third-party/SDL/AGENTS.md, third-party/SDL/CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 99 of 99 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, third-party/SDL/AGENTS.md, third-party/SDL/CLAUDE.md
agent_instruction_max_bytes2,730
How it's scored
18/18One-command bootstrap — Taskfile.yml, third-party/SDL/build-scripts/pkg-support/mingw/Makefile, third-party/capstone/Makefile, third-party/capstone/bindings/java/Makefile, third-party/capstone/bindings/ocaml/Makefile, third-party/capstone/contrib/m68k_instruction_tbl_gen/Makefile, third-party/capstone/cstool/Makefile, third-party/capstone/packages/freebsd/ports/devel/capstone/Makefile, third-party/capstone/suite/fuzz/Makefile, third-party/cubeb/Makefile, third-party/cubeb/cubeb/Makefile, third-party/discord-rpc/thirdparty/rapidjson-1.1.0/doc/diagram/makefile, third-party/tree-sitter/tree-sitter/Makefile, third-party/tree-sitter/tree-sitter/cli/src/generate/templates/makefile, third-party/zydis/Makefile
22/22Automated tests
11/11Lint / format config — .eslintrc.js, tox.ini
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, Gemfile.lock
has_dockerfileyes
typed_languageno
bootstrap_filesTaskfile.yml, third-party/SDL/build-scripts/pkg-support/mingw/Makefile, third-party/capstone/Makefile, third-party/capstone/bindings/java/Makefile, third-party/capstone/bindings/ocaml/Makefile, third-party/capstone/contrib/m68k_instruction_tbl_gen/Makefile, third-party/capstone/cstool/Makefile, third-party/capstone/packages/freebsd/ports/devel/capstone/Makefile, third-party/capstone/suite/fuzz/Makefile, third-party/cubeb/Makefile, third-party/cubeb/cubeb/Makefile, third-party/discord-rpc/thirdparty/rapidjson-1.1.0/doc/diagram/makefile, third-party/tree-sitter/tree-sitter/Makefile, third-party/tree-sitter/tree-sitter/cli/src/generate/templates/makefile, third-party/zydis/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifeststhird-party/SDL/android-project/app/build.gradle, third-party/SDL/android-project/build.gradle, third-party/fmt/support/build.gradle, third-party/tree-sitter/tree-sitter/Cargo.toml, third-party/tree-sitter/tree-sitter/cli/Cargo.toml, third-party/tree-sitter/tree-sitter/cli/config/Cargo.toml, third-party/tree-sitter/tree-sitter/cli/loader/Cargo.toml, third-party/tree-sitter/tree-sitter/cli/src/generate/templates/cargo.toml, third-party/tree-sitter/tree-sitter/cli/src/generate/templates/go.mod, third-party/tree-sitter/tree-sitter/cli/src/tests/proc_macro/Cargo.toml, third-party/tree-sitter/tree-sitter/highlight/Cargo.toml, third-party/tree-sitter/tree-sitter/lib/Cargo.toml, third-party/tree-sitter/tree-sitter/tags/Cargo.toml, third-party/tree-sitter/tree-sitter/xtask/Cargo.toml
dependency_bot_commit_share0.01
How it's scored
0/45Type-checkable code — Common Lisp without a type-check config
52.4/55Manageable file sizes — 336/6,989 source files over 60KB
Inputs used
primary_languageCommon Lisp
largest_source_bytes8,745,220
source_files_sampled6,989
oversized_source_files336
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, samples
Inputs used
example_dirsexamples, samples
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

3,506GitHub stars
71contributors
229commits, last 12 months
2days since last push
88releases
2bus factor
166open issues
—package ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-21: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 3506 stars today.
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 3,463 ★ / 233 ⇿
3,463Stars
233Forks
88Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-07-21. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

01,2502,5003,7503,463225462020-082023-082026-08
Major 0Minor 3Patch 85

Each point covers 6 days.

OpenSSF Scorecard 5.3 / 10
5.3aggregate

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-12 11:42 UTC

9Binary-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
9CI-Tests29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 21/30 approved changesets -- score normalized to 7
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 10 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
0Vulnerabilities86 existing vulnerabilities detected
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.