Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 23:10 UTC

squid-protocol / gitgalaxy

Deep repository intelligence for humans and ai. Air gapped, on premise, zero dependency SAST for 50 languages regardless of compilation status. Sarif and sbom outputs.

PythonCustom license★ 50 stars⑂ 8 forkssince Mar 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

squid-protocol/gitgalaxy holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (87/100) and lowest on Community & Adoption (51/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Joe EsquibelPersonal account
7 followers14 public repossince Jan 2026Lansing Community College, Professor of Biology

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 publishTags
PyPIgitgalaxy2.4.7-6415 days agostatic-analysissecuritydevsecopsvisualizationastzero-trustsbomlegacy-migration

Metrics by category

Vitality

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

87Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
14.5/36Commit cadence21/52 weeks with commits
18/18Commit volume2,016 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_year2,016
human_commit_share1
days_since_last_push0
active_weeks_last_year21

Release discipline

100Exceptional
How it's scored
27/27Ships releases15 releases published
36/36Release recencylatest release 15 days ago
27/27Release cadencea release every ~11.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count15
latest_release_tagv2.4.7
releases_from_tagsno
days_since_latest_release15
mean_days_between_releases11.1
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

51Moderate · 17% of overall
How it's scored
27.4/60Stars50 stars
7/25Forks8 forks
0/15Watchers0 watchers
Inputs used
forks8
stars50
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.3/22.5Commit distributiontop contributor authored 99% of commits
10.8/13.5Contributor breadth8 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled8
top_contributor_share0.988
How it's scored
37.3/42Issue resolution89% of issues closed
29.3/30PR acceptance1,525/1,561 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,525
open_issues64
closed_issues514
prs_merged_7d60
prs_decided_7d60
prs_merged_30d60
prs_decided_30d60
issue_closed_ratio0.889
closed_unmerged_prs36
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
6.5/25Owner reach7 followers of squid-protocol
9.8/25Track record14 public repos, account ~0 yr old
Inputs used
followers7
owner_typeUser
is_verified
owner_loginsquid-protocol
public_repos14
account_age_days221
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 pypi
35/35Publish recencylatest publish 15 days ago
20/20Version history64 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgitgalaxy
ecosystemspypi
any_deprecatedno
min_days_since_publish15

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows18 workflow(s)
24/24Tests present
16/16Linter config.flake8, pyproject.toml ([tool.ruff])
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://squid-protocol.github.io/gitgalaxy/
10/10Repository description
10/10Topics18 topics
0/10Wiki
Inputs used
topicsauditing, codebase-analysis, sbom, zero-trust, ai-security, appsec, cybersecurity, devsecops, incident-response, legacy-modernization, software-architecture, static-analysis, supply-chain-security, code-intelligence, graph-rag, knowledge-graph, sarif, sast
has_wikino
homepagehttps://squid-protocol.github.io/gitgalaxy/
docs_sitehttps://squid-protocol.github.io/gitgalaxy/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

74Good · 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 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.2/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
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
5/5SASTSAST tool is run on all commits
2/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.7
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages138
unassessed_packages2
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 138 resolved dependencies against OSV. 2 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

72Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history100 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_filesCLAUDE.md
agent_instruction_max_bytes23,371
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.flake8, pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environmentDockerfile
10/10Demonstrated agent practice18 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.18
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codePython without a type-check config
52.9/55Manageable file sizes10/260 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes927,186
source_files_sampled260
oversized_source_files10
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplescookbook
Inputs used
example_dirscookbook
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

50GitHub stars
8contributors
2,016commits, last 12 months
0days since last push
15releases
1bus factor
64open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi download statistics for 'gitgalaxy' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced

More detail

Star and fork history 0 ★ / 8 ⇿
0Stars
8Forks
7Releases

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.

02468822026-052026-062026-08
Major 0Minor 2Patch 5
OpenSSF Scorecard 6.7 / 10
6.7aggregate

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 23:08 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 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
10SASTSAST tool is run on all commits
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 140

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

RegistryPackageVersionRelation
PyPIasttokens3.0.2indirect
PyPIattrs26.1.0indirect
PyPIbabel2.18.0indirect
PyPIbackcall0.2.0indirect
PyPIbackrefs8.0indirect
PyPIbeautifulsoup44.15.0indirect
PyPIbleach6.4.0indirect
PyPIblinker1.9.0indirect
PyPIbuild1.4.3indirect
PyPIcertifi2026.7.22indirect
PyPIcffi2.0.0indirect
PyPIcharset-normalizer3.4.9indirect
PyPIclick8.4.2indirect
PyPIcolorama0.4.6indirect
PyPIcontourpy1.3.3indirect
PyPIcoverage7.14.0indirect
PyPIcryptography50.0.0indirect
PyPIcycler0.12.1indirect
PyPIdecorator5.2.1indirect
PyPIdefusedxml0.7.1indirect
PyPIdocopt0.6.2indirect
PyPIdocutils0.23indirect
PyPIexecuting2.2.1indirect
PyPIfastjsonschema2.22.1indirect
PyPIflask3.1.3indirect
PyPIfonttools4.63.0indirect
PyPIghp-import2.1.0indirect
PyPIid1.6.1indirect
PyPIidna3.18indirect
PyPIiniconfig2.3.0indirect
PyPIipython8.39.0indirect
PyPIitsdangerous2.2.0indirect
PyPIjaraco-classes3.4.0indirect
PyPIjaraco-context6.1.2indirect
PyPIjaraco-functools4.6.0indirect
PyPIjedi0.20.0indirect
PyPIjeepney0.9.0indirect
PyPIjinja23.1.6indirect
PyPIjoblib1.5.3indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPIjupyter-client8.9.1indirect
PyPIjupyter-core5.9.1indirect
PyPIjupyterlab-pygments0.3.0indirect
PyPIkeyring25.7.0indirect
PyPIkiwisolver1.5.0indirect
PyPIllvmlite0.48.0indirect
PyPImarkdown3.10.2indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.3indirect
PyPImatplotlib3.10.8indirect
PyPImatplotlib-inline0.2.2indirect
PyPImdurl0.1.2indirect
PyPImergedeep1.3.4indirect
PyPImistune3.3.4indirect
PyPImkdocs1.6.1indirect
PyPImkdocs-get-deps0.2.2indirect
PyPImkdocs-material9.7.7indirect
PyPImkdocs-material-extensions1.3.1indirect
PyPImore-itertools10.8.0indirect
PyPInarwhals2.18.1indirect
PyPInbclient0.11.0indirect
PyPInbconvert7.17.1indirect
PyPInbformat5.11.0indirect
PyPInetworkx3.6.1indirect
PyPInh30.3.6indirect
PyPInumba0.66.0indirect
PyPInumpy2.4.3indirect
PyPInvidia-nccl-cu122.30.4indirect
PyPIopencv-python5.0.0.93indirect
PyPIpackaging26.2indirect
PyPIpaginate0.5.7indirect
PyPIpandas3.0.1indirect
PyPIpandocfilters1.5.1indirect
PyPIparso0.8.7indirect
PyPIpathspec1.1.1indirect
PyPIpexpect4.9.0indirect
PyPIpickleshare0.7.5indirect
PyPIpillow12.3.0indirect
PyPIpipreqs0.5.0indirect
PyPIplatformdirs4.10.0indirect
PyPIplotly6.8.0indirect
PyPIpluggy1.6.0indirect
PyPIprompt-toolkit3.0.52indirect
PyPIptyprocess0.7.0indirect
PyPIpure-eval0.2.3indirect
PyPIpyan32.6.2indirect
PyPIpycparser3.0indirect
PyPIpydeps3.0.2indirect
PyPIpygments2.20.0indirect
PyPIpymdown-extensions11.0.1indirect
PyPIpynndescent0.6.0indirect
PyPIpypandoc1.17indirect
PyPIpyparsing3.3.2indirect
PyPIpyproject-hooks1.2.0indirect
PyPIpytest9.1.1indirect
PyPIpytest-cov7.1.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-dotenv1.2.2indirect
PyPIpyyaml6.0.3indirect
PyPIpyyaml-env-tag1.1indirect
PyPIpyzmq27.1.0indirect
PyPIreadme-renderer44.0indirect
PyPIreferencing0.37.0indirect
PyPIregex2026.7.19indirect
PyPIrequests2.34.2indirect
PyPIrequests-toolbelt1.0.0indirect
PyPIrfc39862.0.0indirect
PyPIrich15.0.0indirect
PyPIrpds-py0.30.0indirect
PyPIruff0.16.0indirect
PyPIscikit-learn1.8.0indirect
PyPIscipy1.17.1indirect
PyPIseaborn0.13.2indirect
PyPIsecretstorage3.5.0indirect
PyPIsetuptoolsindirect
PyPIsetuptools83.0.0indirect
PyPIsetuptools-scmindirect
PyPIsix1.17.0indirect
PyPIsoupsieve2.8.4indirect
PyPIstack-data0.6.3indirect
PyPIstdlib-list0.12.0indirect
PyPIstripe14.4.1indirect
PyPIthreadpoolctl3.6.0indirect
PyPItiktoken0.13.0indirect
PyPItinycss21.4.0indirect
PyPItornado6.5.7indirect
PyPItqdm4.69.0indirect
PyPItraitlets5.16.1indirect
PyPItwine6.2.0indirect
PyPItyping-extensions4.16.0indirect
PyPIumap-learn0.5.12indirect
PyPIurllib32.7.0indirect
PyPIwatchdog6.0.0indirect
PyPIwcwidth0.8.1indirect
PyPIwebencodings0.5.1indirect
PyPIwerkzeug3.1.8indirect
PyPIwheel0.47.0indirect
PyPIxgboost3.2.0indirect
PyPIyarg0.1.10indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 138 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 2 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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