Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-17 04:58 UTC

WT-In / dbn-go

Golang bindings and tools for DataBento

GoApache-2.0★ 0 stars⑂ 0 forkssince May 2025forkView on GitHub ↗

WT-In/dbn-go holds a health index of 38 out of 100, placing it in the Weak band. It scores highest on AI Readiness (75/100) and lowest on Community & Adoption (12/100). It was last updated 136 days ago. A single contributor accounts for most of its recent work.

38
overall / 100
Weak

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.

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

Ownership

WT-InOrganization
0 followers1 public reposince May 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/WT-In/dbn-gov0.9.7-11136 days ago

Metrics by category

Vitality

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

59Moderate · 21% of overall
How it's scored
9.9/36Push recency — last push 136 days ago
10.4/36Commit cadence — 15/52 weeks with commits
18/18Commit volume — 100 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year100
human_commit_share1
days_since_last_push136
active_weeks_last_year15
How it's scored
27/27Ships releases — 11 releases published
27/36Release recency — latest release 136 days ago
27/27Release cadence — a release every ~11.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count11
latest_release_tagv0.9.7
releases_from_tagsno
days_since_latest_release136
mean_days_between_releases11.9
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?

12Critical · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

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

51Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.8/22.5Commit distribution — top contributor authored 83% of commits
8.1/13.5Contributor breadth — 6 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.83
How it's scored
0/42Issue resolution — no issues or no data
22.5/30PR acceptance — 6/8 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/26 approved changesets -- score normalized to 0
Inputs used
merged_prs6
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs2
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
0/25Owner reach — 0 followers of WT-In
5.3/25Track record — 1 public repos, account ~1 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginWT-In
public_repos1
account_age_days560

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

41Weak · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 4 out of 4 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

1Critical
How it's scored
0/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

34At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 4 out of 4 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/26 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflow — no 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
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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 — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 23 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate2.7
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: github.com/klauspost/compress v1.18.5 (high 7.5)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 112 days ago
Inputs used
sourceosv
advisories25
affected_packages5
assessed_packages20
unassessed_packages0
affected_by_severityhigh 1, moderate 1, unknown 3
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 20 resolved dependencies against OSV. 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.

75Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 78 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.78
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes4,149
How it's scored
12.6/18One-command bootstrap — go.mod (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — lockfile
4/10Demonstrated agent practice — 2 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
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.02
toolchain_manifestsgo.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Go (statically typed)
52.3/55Manageable file sizes — 2/41 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes63,326
source_files_sampled41
oversized_source_files2

Key facts

0GitHub stars
6contributors
100commits, last 12 months
136days since last push
11releases
1bus factor
0open issues
Gopackage ecosystems

Data collection warnings

  • Community profile unavailable

More detail

OpenSSF Scorecard 2.7 / 10
2.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-11-17 04:57 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests4 out of 4 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/26 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities23 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
Gogithub.com/klauspost/compressv1.18.5go.mod
Gogithub.com/onsi/ginkgo/v2v2.28.1go.mod
Gogithub.com/onsi/gomegav1.39.1go.mod
Gogithub.com/valyala/fastjsonv1.6.10go.mod
All dependencies 20

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

RegistryPackageVersionRelation
Gogithub.com/klauspost/compressv1.18.5direct
Gogithub.com/onsi/ginkgo/v2v2.28.1direct
Gogithub.com/onsi/gomegav1.39.1direct
Gogithub.com/valyala/fastjsonv1.6.10direct
Gogithub.com/davecgh/go-spewv1.1.2-0.20180830191138-d8f796af33ccindirect
Gogithub.com/go-logr/logrv1.4.3indirect
Gogithub.com/go-task/slim-sprig/v3v3.0.0indirect
Gogithub.com/google/go-cmpv0.7.0indirect
Gogithub.com/google/pprofv0.0.0-20260115054156-294ebfa9ad83indirect
Gogithub.com/masterminds/semver/v3v3.4.0indirect
Gogithub.com/pmezard/go-difflibv1.0.1-0.20181226105442-5d4384ee4fb2indirect
Gogithub.com/stretchr/testifyv1.11.1indirect
Gogo.yaml.in/yaml/v3v3.0.4indirect
Gogolang.org/x/modv0.33.0indirect
Gogolang.org/x/netv0.50.0indirect
Gogolang.org/x/syncv0.20.0indirect
Gogolang.org/x/sysv0.42.0indirect
Gogolang.org/x/textv0.34.0indirect
Gogolang.org/x/toolsv0.42.0indirect
Gogoogle.golang.org/protobufv1.36.11indirect
Dependency advisories 5

This repository publishes no package the index resolves, so its own dependency graph was assessed — 20 packages, which also include development and test pins that never ship: 5 carry known advisories, of which 1 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
github.com/klauspost/compressv1.18.5directhigh31.20.2
golang.org/x/netv0.50.0indirectmoderate171.27.2
golang.org/x/modv0.33.0indirectunknown21.27.0-rc.3
golang.org/x/sysv0.42.0indirectunknown10.44.0
golang.org/x/textv0.34.0indirectunknown20.41.0

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