Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 11:44 UTC

hornbill / goHornbillRequestImport

Hornbill Service Manager Request Import Utility

GoCustom license★ 0 stars⑂ 1 forksince Nov 2018View on GitHub ↗

hornbill/goHornbillRequestImport holds a health index of 31 out of 100, placing it in the At Risk band. It scores highest on AI Readiness (51/100) and lowest on Engineering Quality (21/100). It was last updated 54 days ago. A single contributor accounts for most of its recent work.

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.

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)

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

Ownership

HornbillOrganization

12 followers54 public repossince Nov 2015

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?

47Weak · 21% of overall

Development activity

27At Risk

How it's scored

18/36	Push recency — last push 54 days ago
1.4/36	Commit cadence — 2/52 weeks with commits
5.4/18	Commit volume — 3 commits in the last year
2/10	OpenSSF Scorecard: Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2

Inputs used

commits_last_year	3
human_commit_share	0.894
days_since_last_push	54
active_weeks_last_year	2

Release discipline

76Good

How it's scored

27/27	Ships releases — 25 releases published
36/36	Release recency — latest release 56 days ago
12.6/27	Release cadence — a release every ~204.9 days
0/10	OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.

Inputs used

releases_count	25
latest_release_tag	v1.13.0
releases_from_tags	no
days_since_latest_release	56
mean_days_between_releases	204.9

Community & Adoption

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

21At Risk · 17% of overall

Popularity & adoption

1Critical

How it's scored

0/60	Stars — 0 stars
0/25	Forks — 1 forks
0/15	Watchers — 2 watchers

Inputs used

forks	1
stars	0
watchers	2
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

44Weak

How it's scored

22.5/22.5	README
16.9/22.5	License — license file present, not a recognized license
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	0
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	no

Sustainability & Governance

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

47Weak · 23% of overall

Maintainer resilience (bus factor)

16Critical

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
2.4/22.5	Commit distribution — top contributor authored 90% of commits
4.1/13.5	Contributor breadth — 3 contributors
0/10	OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0

Inputs used

bus_factor	1
contributors_sampled	3
top_contributor_share	0.895

Issue & PR responsiveness

67Good

How it's scored

0/42	Issue resolution — no issues or no data
30/30	PR acceptance — 6/6 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — Found 0/19 approved changesets -- score normalized to 0

Inputs used

merged_prs	6
open_issues	0
closed_issues	0
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	—
closed_unmerged_prs	0
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

63Moderate

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
8/25	Owner reach — 12 followers of hornbill
24.7/25	Track record — 54 public repos, account ~10 yr old

Inputs used

followers	12
owner_type	Organization
is_verified	no
owner_login	hornbill
public_repos	54
account_age_days	3,969

Engineering Quality

Are baseline engineering and documentation practices in place?

21At Risk · 19% of overall

Engineering practices

1Critical

How it's scored

0/24	CI workflows
0/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
0/20	OpenSSF Scorecard: CI-Tests — 0 out of 6 merged PRs checked by a CI test -- score normalized to 0

Inputs used

has_ci	no
has_tests	no
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

50Moderate

How it's scored

30/30	README
0/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

topics	—
has_wiki	yes
homepage	—
docs_site	—
has_readme	yes
has_docs_dir	no
has_description	yes

Security

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

39Weak · 16% of overall

Security posture

24At Risk

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — branch protection not enabled on development/release branches
0/2.5	CI-Tests — 0 out of 6 merged PRs checked by a CI test -- score normalized to 0
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 0/19 approved changesets -- score normalized to 0
0/2.5	Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10	Dangerous-Workflow — no data
7.5/7.5	Dependency-Update-Tool — update tool detected
0/5	Fuzzing — project is not fuzzed
2.2/2.5	License — license file detected
1.5/7.5	Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5	Token-Permissions — no data
0/7.5	Vulnerabilities — 35 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	14
scorecard_version	v5.5.0
checks_inconclusive	4
scorecard_aggregate	2.4

Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	54
affected_packages	3
assessed_packages	23
unassessed_packages	0
affected_by_severity	critical 1, moderate 1, unknown 1
direct_affected_packages	0

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 23 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.

51Moderate · 4% of overall

Agent context & guidance

32At Risk

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
31.7/40	Legible commit history — 25 of 42 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.595
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

46Weak

How it's scored

12.6/18	One-command bootstrap — go.mod (toolchain convention, no task runner)
0/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — Go (statically typed)
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 47
8/8	Automated maintenance — 5 of the last 47 commits are automated dependency updates
0/10	OpenSSF Scorecard: Pinned-Dependencies — no data

Inputs used

has_nix	no
has_tests	no
lockfiles	go.sum
has_dockerfile	no
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	—
agent_commit_share	0
toolchain_manifests	go.mod
dependency_bot_commit_share	0.106

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — Go (statically typed)
55/55	Manageable file sizes — 0/14 source files over 60KB

Inputs used

primary_language	Go
largest_source_bytes	41,757
source_files_sampled	14
oversized_source_files	0

Key facts

0GitHub stars

3contributors

3commits, last 12 months

54days since last push

25releases

1bus factor

0open issues

Gopackage ecosystems

More detail

OpenSSF Scorecard 2.4 / 10

2.4aggregate

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-19 11:43 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
0	CI-Tests	0 out of 6 merged PRs checked by a CI test -- score normalized to 0
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 0/19 approved changesets -- score normalized to 0
0	Contributors	project has 0 contributing companies or organizations -- score normalized to 0
n/a	Dangerous-Workflow	no workflows found
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
9	License	license file detected
2	Maintained	3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
n/a	Packaging	packaging workflow not detected
n/a	Pinned-Dependencies	no dependencies found
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
0	Signed-Releases	Project has not signed or included provenance with any releases.
n/a	Token-Permissions	No tokens found
0	Vulnerabilities	35 existing vulnerabilities detected

Direct dependencies 11

Registry	Package	Version constraint	Manifest
Go	github.com/alexbrainman/odbc	`v0.0.0-20211220213544-9c9a2e61c5e2`	go.mod
Go	github.com/denisenkom/go-mssqldb	`v0.12.3`	go.mod
Go	github.com/fatih/color	`v1.14.1`	go.mod
Go	github.com/go-sql-driver/mysql	`v1.7.0`	go.mod
Go	github.com/hornbill/goApiLib	`v0.0.0-20210702135347-bcef2b442dbc`	go.mod
Go	github.com/hornbill/goHornbillHelpers	`v0.0.0-20190110171921-6d8d037ec1e8`	go.mod
Go	github.com/hornbill/mysql320	`v0.0.0-20230221110602-449b6f4f55b2`	go.mod
Go	github.com/hornbill/pb	`v0.0.0-20151205101406-5d91ad42e9c1`	go.mod
Go	github.com/hornbill/sqlx	`v0.0.0-20160105113732-0c4aca8610c8`	go.mod
Go	github.com/jmoiron/sqlx	`v1.3.5`	go.mod
Go	github.com/tcnksm/go-latest	`v0.0.0-20170313132115-e3007ae9052e`	go.mod

All dependencies 23

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

Registry	Package	Version	Relation
Go	github.com/alexbrainman/odbc	`v0.0.0-20211220213544-9c9a2e61c5e2`	direct
Go	github.com/denisenkom/go-mssqldb	`v0.12.3`	direct
Go	github.com/fatih/color	`v1.14.1`	direct
Go	github.com/go-sql-driver/mysql	`v1.7.0`	direct
Go	github.com/hornbill/goapilib	`v0.0.0-20210702135347-bcef2b442dbc`	direct
Go	github.com/hornbill/gohornbillhelpers	`v0.0.0-20190110171921-6d8d037ec1e8`	direct
Go	github.com/hornbill/mysql320	`v0.0.0-20230221110602-449b6f4f55b2`	direct
Go	github.com/hornbill/pb	`v0.0.0-20151205101406-5d91ad42e9c1`	direct
Go	github.com/hornbill/sqlx	`v0.0.0-20160105113732-0c4aca8610c8`	direct
Go	github.com/jmoiron/sqlx	`v1.3.5`	direct
Go	github.com/tcnksm/go-latest	`v0.0.0-20170313132115-e3007ae9052e`	direct
Go	github.com/golang-sql/civil	`v0.0.0-20190719163853-cb61b32ac6fe`	indirect
Go	github.com/golang-sql/sqlexp	`v0.1.0`	indirect
Go	github.com/google/go-github	`v17.0.0+incompatible`	indirect
Go	github.com/google/go-querystring	`v1.1.0`	indirect
Go	github.com/hashicorp/go-version	`v1.6.0`	indirect
Go	github.com/hornbill/color	`v0.0.0-20160224221155-4f7bcef27eec`	indirect
Go	github.com/mattn/go-colorable	`v0.1.13`	indirect
Go	github.com/mattn/go-isatty	`v0.0.17`	indirect
Go	github.com/olekukonko/ts	`v0.0.0-20171002115256-78ecb04241c0`	indirect
Go	golang.org/x/crypto	`v0.31.0`	indirect
Go	golang.org/x/net	`v0.23.0`	indirect
Go	golang.org/x/sys	`v0.28.0`	indirect

Dependency advisories 3

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

Package	Version	Relation	Severity	Advisories	Fixed in
golang.org/x/crypto	`v0.31.0`	indirect	critical	37	`0.56.0`
golang.org/x/net	`v0.23.0`	indirect	moderate	16	`1.27.0-rc.3`
golang.org/x/sys	`v0.28.0`	indirect	unknown	1	`0.44.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.

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.

Software health index

Score profile

Ownership

Metrics by category

Key facts

More detail

Feedback

Related records