Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 23:29 UTC

bmcszk / go-restclient

Go library for executing HTTP requests from .http files with JetBrains/VS Code compatibility. Same files for manual testing and automated E2E tests.

GoMIT★ 6 stars⑂ 0 forkssince May 2025View on GitHub ↗
KindLibraryApplicationhow this is determined

bmcszk/go-restclient holds a health index of 75 out of 100, placing it in the Good band. It scores highest on AI Readiness (94/100) and lowest on Community & Adoption (29/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

75
overall / 100
Good

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.

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

Ownership

Błażej McszkPersonal account
3 followers34 public repossince Mar 2012Blaze Software

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/bmcszk/go-restclientv1.0.0-1227 days ago

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
2.8/36Commit cadence — 4/52 weeks with commits
12.9/18Commit volume — 26 commits in the last year
10/10OpenSSF Scorecard: Maintained — 26 commit(s) and 16 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year26
human_commit_share0.959
days_since_last_push3
active_weeks_last_year4
How it's scored
27/27Ships releases — 12 releases published
36/36Release recency — latest release 26 days ago
19.8/27Release cadence — a release every ~53.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count12
latest_release_tagv1.0.0
releases_from_tagsno
days_since_latest_release26
mean_days_between_releases53.7
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?

29At Risk · 17% of overall
How it's scored
11.3/60Stars — 6 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars6
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, pkg.go.dev, shields.io
has_pull_request_templateno

Sustainability & Governance

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

54Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution — 100% of issues closed
20.7/30PR acceptance — 38/55 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/27 approved changesets -- score normalized to 0
Inputs used
merged_prs38
open_issues0
closed_issues26
prs_merged_7d0
prs_decided_7d1
prs_merged_30d19
prs_decided_30d23
issue_closed_ratio1
closed_unmerged_prs17
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 backing — personal (user) account
0/20Verified domain — not applicable to user accounts
4.3/25Owner reach — 3 followers of bmcszk
23.2/25Track record — 34 public repos, account ~14 yr old
Inputs used
followers3
owner_typeUser
is_verified—
owner_loginbmcszk
public_repos34
account_age_days5,334
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

83Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — .golangci.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 27 out of 29 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 15 topics
10/10Wiki
Inputs used
topicsapi-testing, e2e-testing, go, golang, http-client, http-requests, integration-testing, json, response-validation, rest, rest-client, testing, vscode-rest-client, xml, jetbrains-http-client
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

80Excellent · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.2/2.5CI-Tests — 27 out of 29 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
0/7.5Code-Review — Found 0/27 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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 — 26 commit(s) and 16 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
3.5/5SAST — SAST tool detected but not run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7.9
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
26.6/35Direct dependencies free of known advisories — 1 affected: golang.org/x/text v0.22.0 (unknown)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
37.2/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 98 days ago
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages9
unassessed_packages0
affected_by_severityunknown 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 9 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.

94Exceptional · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 44 of 47 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.936
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes1,118
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — .golangci.yml
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — lockfile
8.2/10Demonstrated agent practice — 2 of the last 49 commits agent-authored or agent-credited
8/8Automated maintenance — 2 of the last 49 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.041
toolchain_manifestsgo.mod
dependency_bot_commit_share0.041
How it's scored
45/45Type-checkable code — Go (statically typed)
55/55Manageable file sizes — 0/76 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes32,362
source_files_sampled76
oversized_source_files0

Key facts

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

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 7.9 / 10
7.9aggregate

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-10-20 23:29 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests27 out of 29 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/27 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained26 commit(s) and 16 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
7SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Gogithub.com/alecthomas/kongv1.16.1go.mod
Gogithub.com/google/uuidv1.6.0go.mod
Gogithub.com/hashicorp/go-multierrorv1.1.1go.mod
Gogithub.com/joho/godotenvv1.5.1go.mod
Gogithub.com/pmezard/go-difflibv1.0.0go.mod
Gogithub.com/stretchr/testifyv1.12.1go.mod
Gogolang.org/x/textv0.22.0go.mod
All dependencies 9

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

RegistryPackageVersionRelation
Gogithub.com/alecthomas/kongv1.16.1direct
Gogithub.com/google/uuidv1.6.0direct
Gogithub.com/hashicorp/go-multierrorv1.1.1direct
Gogithub.com/joho/godotenvv1.5.1direct
Gogithub.com/pmezard/go-difflibv1.0.0direct
Gogithub.com/stretchr/testifyv1.12.1direct
Gogolang.org/x/textv0.22.0direct
Gogithub.com/hashicorp/errwrapv1.1.0indirect
Gogo.yaml.in/yaml/v3v3.0.5indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
golang.org/x/textv0.22.0directunknown20.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.