Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-18 07:02 UTC

devlibx / gox-messaging

GoNo license detected★ 0 stars⑂ 3 forkssince Apr 2021View on GitHub ↗

devlibx/gox-messaging holds a health index of 39 out of 100, placing it in the Weak band. It scores highest on Vitality (62/100) and lowest on Community & Adoption (13/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

devlibxPersonal account
2 followers51 public repossince Apr 2021

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/devlibx/gox-messagingv0.0.102-102305 days ago

Metrics by category

Vitality

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

62Moderate · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
1.4/36Commit cadence2/52 weeks with commits
6.3/18Commit volume4 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year4
human_commit_share1
days_since_last_push4
active_weeks_last_year2
How it's scored
16.2/27Ships releases100 version tags (no GitHub releases)
36/36Release recencylatest release 4 days ago
27/27Release cadencea release every ~7.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv2.0.59
releases_from_tagsyes
days_since_latest_release4
mean_days_between_releases7.4
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?

13Critical · 17% of overall
How it's scored
0/60Stars0 stars
2.5/25Forks3 forks
0/15Watchers2 watchers
Inputs used
forks3
stars0
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
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?

55Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.9/22.5Commit distributiontop contributor authored 92% of commits
4.1/13.5Contributor breadth3 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.917
How it's scored
42/42Issue resolution100% of issues closed
23.3/30PR acceptance7/9 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 2/28 approved changesets -- score normalized to 0
Inputs used
merged_prs7
open_issues0
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio1
closed_unmerged_prs2
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
3.4/25Owner reach2 followers of devlibx
23.2/25Track record51 public repos, account ~5 yr old
Inputs used
followers2
owner_typeUser
is_verified
owner_logindevlibx
public_repos51
account_age_days1,958
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on go
26/35Publish recencylatest publish 305 days ago
20/20Version history102 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/devlibx/gox-messaging
ecosystemsgo
any_deprecatedno
min_days_since_publish305

Engineering Quality

Are baseline engineering and documentation practices in place?

45Weak · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 2 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

29At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 2 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 2/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
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities60 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate2.1
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
13/35Direct dependencies free of known advisories2 affected: golang.org/x/net 0.8.0 (high 7.5), github.com/aws/aws-sdk-go 1.38.39 (unknown)
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
31.7/40No advisories left outstanding2 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,648 days ago
Inputs used
sourceosv
advisories25
affected_packages2
assessed_packages14
unassessed_packages0
affected_by_severityhigh 1, unknown 1
direct_affected_packages2
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 14 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.

54Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
1.6/40Legible commit history3 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.03
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapgo.mod (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsgo.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeGo (statically typed)
55/55Manageable file sizes0/28 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes14,543
source_files_sampled28
oversized_source_files0
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 examplesexample
Inputs used
example_dirsexample
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

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

More detail

Star and fork history 0 ★ / 3 ⇿
0Stars
3Forks
80Releases

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.

12233312023-012024-102026-07
Major 1Minor 0Patch 79

Each point covers 4 days.

OpenSSF Scorecard 2.1 / 10
2.1aggregate

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-18 07:02 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 2 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/28 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
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
0Vulnerabilities60 existing vulnerabilities detected
Direct dependencies 14
RegistryPackageVersion constraintManifest
Gogithub.com/aws/aws-sdk-gov1.38.39go.mod
Gogithub.com/confluentinc/confluent-kafka-go/v2v2.1.0go.mod
Gogithub.com/devlibx/gox-awsv0.0.17go.mod
Gogithub.com/devlibx/gox-basev0.0.111go.mod
Gogithub.com/devlibx/gox-metricsv0.0.16go.mod
Gogithub.com/golang/mockv1.6.0go.mod
Gogithub.com/google/uuidv1.3.0go.mod
Gogithub.com/pkg/errorsv0.9.1go.mod
Gogithub.com/stretchr/testifyv1.8.2go.mod
Gogithub.com/yalp/jsonpathv0.0.0-20180802001716-5cc68e5049a0go.mod
Gogo.uber.org/goleakv1.1.12go.mod
Gogo.uber.org/ratelimitv0.2.0go.mod
Gogo.uber.org/zapv1.17.0go.mod
Gogolang.org/x/netv0.8.0go.mod
All dependencies 14

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

RegistryPackageVersionRelation
Gogithub.com/aws/aws-sdk-go1.38.39direct
Gogithub.com/confluentinc/confluent-kafka-go/v22.1.0direct
Gogithub.com/devlibx/gox-aws0.0.17direct
Gogithub.com/devlibx/gox-base0.0.111direct
Gogithub.com/devlibx/gox-metrics0.0.16direct
Gogithub.com/golang/mock1.6.0direct
Gogithub.com/google/uuid1.3.0direct
Gogithub.com/pkg/errors0.9.1direct
Gogithub.com/stretchr/testify1.8.2direct
Gogithub.com/yalp/jsonpath0.0.0-20180802001716-5cc68e5049a0direct
Gogo.uber.org/goleak1.1.12direct
Gogo.uber.org/ratelimit0.2.0direct
Gogo.uber.org/zap1.17.0direct
Gogolang.org/x/net0.8.0direct
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
golang.org/x/net0.8.0directhigh2312.0.2
github.com/aws/aws-sdk-go1.38.39directunknown2

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.31.0 — full methodology · metrics wiki.

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