Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-14 03:07 UTC

karust / openserp

Self-hosted SERP API for AI, SEO & automation. Browser-rendered Google, Bing, Yandex, Baidu, DuckDuckGo and Ecosia search with page extraction 🎉

GoMIT★ 1,262 stars⑂ 146 forkssince Jun 2023View on GitHub ↗

KindNetwork serviceCommand-line toolLibraryhow this is determined

#baidu #google #search #search-engine #serp #serpapi #yandex #bing #duckduckgo #openserp #opensource #web-scraping #ecosia #ai #llm #seo #api #cli

karust/openserp holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (90/100) and lowest on Security (40/100). It was last updated 22 days ago. A single contributor accounts for most of its recent work.

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.

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

Ownership

Rustem KamalovPersonal account

55 followers36 public repossince Sep 2018

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish
Go	github.com/karust/openserp	v0.8.12	-	13	22 days ago

Metrics by category

Vitality

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

80Excellent · 21% of overall

Development activity

74Good

How it's scored

28.8/36	Push recency — last push 22 days ago
17.3/36	Commit cadence — 25/52 weeks with commits
18/18	Commit volume — 114 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	114
human_commit_share	1
days_since_last_push	22
active_weeks_last_year	25

Release discipline

90Excellent

How it's scored

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

Inputs used

releases_count	14
latest_release_tag	v0.8.12
releases_from_tags	no
days_since_latest_release	22
mean_days_between_releases	37.5

Community & Adoption

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

75Good · 17% of overall

Popularity & adoption

74Good

How it's scored

50.3/60	Stars — 1,262 stars
18/25	Forks — 146 forks
5.6/15	Watchers — 11 watchers

Inputs used

forks	146
stars	1,262
watchers	11
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

77Good

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
18/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
6.3/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	5
has_contributing	yes
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	github.com, pkg.go.dev, shields.io
has_pull_request_template	yes

Sustainability & Governance

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

54Moderate · 23% of overall

Maintainer resilience (bus factor)

19Critical

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	5
top_contributor_share	0.853

Issue & PR responsiveness

54Moderate

How it's scored

21.8/42	Issue resolution — 52% of issues closed
24/30	PR acceptance — 8/10 decided PRs merged
8.7/13	Newcomer PR acceptance — 2/3 first-time contributors' PRs merged in 30d
0/15	OpenSSF Scorecard: Code-Review — Found 2/21 approved changesets -- score normalized to 0

Inputs used

merged_prs	8
open_issues	13
closed_issues	14
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	2
prs_decided_30d	3
issue_closed_ratio	0.519
closed_unmerged_prs	2
first_time_authors_30d	3
first_time_prs_merged_30d	2
first_time_prs_decided_30d	3

Ownership & stewardship

58Moderate

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
12.6/25	Owner reach — 55 followers of karust
23.4/25	Track record — 36 public repos, account ~7 yr old

Inputs used

followers	55
owner_type	User
is_verified	—
owner_login	karust
public_repos	36
account_age_days	2,884

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on go
35/35	Publish recency — latest publish 22 days ago
20/20	Version history — 13 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	github.com/karust/openserp
ecosystems	go
any_deprecated	no
min_days_since_publish	22

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall

Engineering practices

84Excellent

How it's scored

24/24	CI workflows — 4 workflow(s)
24/24	Tests present
16/16	Linter config — .golangci.yml
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
20/20	OpenSSF Scorecard: CI-Tests — 3 out of 3 merged PRs checked by a CI test -- score normalized to 10

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	yes
has_precommit_config	no

Documentation

100Exceptional

How it's scored

30/30	README
25/25	Documentation directory
15/15	Documentation / homepage site — https://openserp.org
10/10	Repository description
10/10	Topics — 18 topics
10/10	Wiki

Inputs used

topics	baidu, google, search, search-engine, serp, serpapi, yandex, bing, duckduckgo, openserp, opensource, web-scraping, ecosia, ai, llm, seo, api, cli
has_wiki	yes
homepage	https://openserp.org
docs_site	https://openserp.org
has_readme	yes
has_docs_dir	yes
has_description	yes

Security

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

40Weak · 16% of overall

Security posture

34At 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
2.5/2.5	CI-Tests — 3 out of 3 merged PRs checked by a CI test -- score normalized to 10
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 2/21 approved changesets -- score normalized to 0
0/2.5	Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
7.5/7.5	Maintained — 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
5/5	Packaging — packaging workflow detected
0.5/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
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 — detected GitHub workflow tokens with excessive permissions
0/7.5	Vulnerabilities — 27 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	18
scorecard_version	v5.5.0
checks_inconclusive	0
scorecard_aggregate	3.4

Dependency advisories

66Good

How it's scored

14.8/35	Direct dependencies free of known advisories — 2 affected: github.com/gofiber/fiber/v2 v2.52.13 (moderate 5.3), golang.org/x/net v0.50.0 (moderate 6.5)
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
34.4/40	No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 168 days ago

Inputs used

source	osv
advisories	41
affected_packages	6
assessed_packages	70
unassessed_packages	2
affected_by_severity	critical 1, moderate 2, unknown 3
direct_affected_packages	2

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

65Good · 4% of overall

Agent context & guidance

30At Risk

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.56
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

73Good

How it's scored

18/18	One-command bootstrap — Makefile
22/22	Automated tests
11/11	Lint / format config — .golangci.yml
11/11	Static type checking — Go (statically typed)
10/10	Reproducible environment — Dockerfile, lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
0/8	Automated maintenance — no automated dependency updates observed
1/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1

Inputs used

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

Code legibility for models

100Exceptional

How it's scored

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

Inputs used

primary_language	Go
largest_source_bytes	101,533
source_files_sampled	179
oversized_source_files	1

Machine-readable interfaces

80Excellent

How it's scored

40/40	API schema (OpenAPI/GraphQL/proto) — docs/openapi.yaml
0/20	MCP server
40/40	Runnable examples — examples

Inputs used

example_dirs	examples
has_mcp_signal	no
api_schema_files	docs/openapi.yaml
interfaces_expected_of	network-service

Key facts

1,262GitHub stars

5contributors

114commits, last 12 months

22days since last push

14releases

1bus factor

13open issues

Gopackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 146 ⇿

0Stars

146Forks

14Releases

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.

Major 0Minor 1Patch 11

Each point covers 3 days.

OpenSSF Scorecard 3.4 / 10

3.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-08-14 03:07 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
10	CI-Tests	3 out of 3 merged PRs checked by a CI test -- score normalized to 10
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 2/21 approved changesets -- score normalized to 0
0	Contributors	project has 0 contributing companies or organizations -- score normalized to 0
10	Dangerous-Workflow	no dangerous workflow patterns detected
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
10	Maintained	30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
10	Packaging	packaging workflow detected
1	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 1
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.
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
0	Vulnerabilities	27 existing vulnerabilities detected

Direct dependencies 18

Registry	Package	Version constraint	Manifest
Go	github.com/2captcha/2captcha-go	`v1.1.10`	go.mod
Go	github.com/JohannesKaufmann/html-to-markdown/v2	`v2.4.0`	go.mod
Go	github.com/PuerkitoBio/goquery	`v1.10.3`	go.mod
Go	github.com/armon/go-socks5	`v0.0.0-20160902184237-e75332964ef5`	go.mod
Go	github.com/bogdanfinn/fhttp	`v0.6.8`	go.mod
Go	github.com/bogdanfinn/tls-client	`v1.15.1`	go.mod
Go	github.com/go-rod/rod	`v0.116.2`	go.mod
Go	github.com/gofiber/fiber/v2	`v2.52.13`	go.mod
Go	github.com/google/uuid	`v1.6.0`	go.mod
Go	github.com/markusmobius/go-trafilatura	`v1.12.2`	go.mod
Go	github.com/sirupsen/logrus	`v1.9.4`	go.mod
Go	github.com/spf13/cobra	`v1.9.1`	go.mod
Go	github.com/spf13/pflag	`v1.0.10`	go.mod
Go	github.com/spf13/viper	`v1.20.1`	go.mod
Go	github.com/ysmood/gson	`v0.7.3`	go.mod
Go	golang.org/x/net	`v0.50.0`	go.mod
Go	golang.org/x/time	`v0.14.0`	go.mod
Go	gopkg.in/yaml.v3	`v3.0.1`	go.mod

All dependencies 72

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

Registry	Package	Version	Relation
Go	github.com/2captcha/2captcha-go	`v1.1.10`	direct
Go	github.com/armon/go-socks5	`v0.0.0-20160902184237-e75332964ef5`	direct
Go	github.com/bogdanfinn/fhttp	`v0.6.8`	direct
Go	github.com/bogdanfinn/tls-client	`v1.15.1`	direct
Go	github.com/go-rod/rod	`v0.116.2`	direct
Go	github.com/gofiber/fiber/v2	`v2.52.13`	direct
Go	github.com/google/uuid	`v1.6.0`	direct
Go	github.com/johanneskaufmann/html-to-markdown/v2	`v2.4.0`	direct
Go	github.com/markusmobius/go-trafilatura	`v1.12.2`	direct
Go	github.com/puerkitobio/goquery	`v1.10.3`	direct
Go	github.com/sirupsen/logrus	`v1.9.4`	direct
Go	github.com/spf13/cobra	`v1.9.1`	direct
Go	github.com/spf13/pflag	`v1.0.10`	direct
Go	github.com/spf13/viper	`v1.20.1`	direct
Go	github.com/ysmood/gson	`v0.7.3`	direct
Go	golang.org/x/net	`v0.50.0`	direct
Go	golang.org/x/time	`v0.14.0`	direct
Go	gopkg.in/yaml.v3	`v3.0.1`	direct
Go	github.com/andybalholm/brotli	`v1.2.0`	indirect
Go	github.com/andybalholm/cascadia	`v1.3.3`	indirect
Go	github.com/araddon/dateparse	`v0.0.0-20210429162001-6b43995a97de`	indirect
Go	github.com/bdandy/go-errors	`v1.2.2`	indirect
Go	github.com/bdandy/go-socks4	`v1.2.3`	indirect
Go	github.com/bogdanfinn/quic-go-utls	`v1.0.9-utls`	indirect
Go	github.com/bogdanfinn/utls	`v1.7.7-barnius`	indirect
Go	github.com/bogdanfinn/websocket	`v1.5.5-barnius`	indirect
Go	github.com/elliotchance/pie/v2	`v2.9.0`	indirect
Go	github.com/forpelevin/gomoji	`v1.2.0`	indirect
Go	github.com/fsnotify/fsnotify	`v1.9.0`	indirect
Go	github.com/go-shiori/dom	`v0.0.0-20230515143342-73569d674e1c`	indirect
Go	github.com/go-shiori/go-readability	`v0.0.0-20241012063810-92284fa8a71f`	indirect
Go	github.com/go-viper/mapstructure/v2	`v2.4.0`	indirect
Go	github.com/gogs/chardet	`v0.0.0-20211120154057-b7413eaefb8f`	indirect
Go	github.com/hablullah/go-hijri	`v1.0.2`	indirect
Go	github.com/hablullah/go-juliandays	`v1.0.0`	indirect
Go	github.com/inconshreveable/mousetrap	`v1.1.0`	indirect
Go	github.com/jalaali/go-jalaali	`v0.0.0-20210801064154-80525e88d958`	indirect
Go	github.com/johanneskaufmann/dom	`v0.2.0`	indirect
Go	github.com/klauspost/compress	`v1.18.2`	indirect
Go	github.com/markusmobius/go-dateparser	`v1.2.3`	indirect
Go	github.com/markusmobius/go-domdistiller	`v0.0.0-20240926050704-25b8d046ffb4`	indirect
Go	github.com/markusmobius/go-htmldate	`v1.9.1`	indirect
Go	github.com/mattn/go-colorable	`v0.1.14`	indirect
Go	github.com/mattn/go-isatty	`v0.0.20`	indirect
Go	github.com/mattn/go-runewidth	`v0.0.16`	indirect
Go	github.com/pelletier/go-toml/v2	`v2.2.4`	indirect
Go	github.com/quic-go/qpack	`v0.6.0`	indirect
Go	github.com/radhifadlillah/whatlanggo	`v0.0.0-20240916001553-aac1f0f737fc`	indirect
Go	github.com/rivo/uniseg	`v0.4.7`	indirect
Go	github.com/rs/zerolog	`v1.33.0`	indirect
Go	github.com/sagikazarmark/locafero	`v0.10.0`	indirect
Go	github.com/sourcegraph/conc	`v0.3.1-0.20240121214520-5f936abd7ae8`	indirect
Go	github.com/spf13/afero	`v1.14.0`	indirect
Go	github.com/spf13/cast	`v1.9.2`	indirect
Go	github.com/subosito/gotenv	`v1.6.0`	indirect
Go	github.com/tam7t/hpkp	`v0.0.0-20160821193359-2b70b4024ed5`	indirect
Go	github.com/tetratelabs/wazero	`v1.8.1`	indirect
Go	github.com/valyala/bytebufferpool	`v1.0.0`	indirect
Go	github.com/valyala/fasthttp	`v1.65.0`	indirect
Go	github.com/wasilibs/go-re2	`v1.7.0`	indirect
Go	github.com/wasilibs/wazero-helpers	`v0.0.0-20240620070341-3dff1577cd52`	indirect
Go	github.com/yosssi/gohtml	`v0.0.0-20201013000340-ee4748c638f4`	indirect
Go	github.com/ysmood/fetchup	`v0.3.0`	indirect
Go	github.com/ysmood/goob	`v0.4.0`	indirect
Go	github.com/ysmood/got	`v0.41.0`	indirect
Go	github.com/ysmood/leakless	`v0.9.0`	indirect
Go	golang.org/x/crypto	`v0.48.0`	indirect
Go	golang.org/x/exp	`v0.0.0-20241009180824-f66d83c29e7c`	indirect
Go	golang.org/x/sys	`v0.41.0`	indirect
Go	golang.org/x/text	`v0.34.0`	indirect
npm	@openserp/sdk	`^0.2.0`	indirect
PyPI	openserp	`—`	indirect

Dependency advisories 6

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

Package	Version	Relation	Severity	Advisories	Fixed in
golang.org/x/crypto	`v0.48.0`	indirect	critical	27	`0.52.0`
github.com/gofiber/fiber/v2	`v2.52.13`	direct	moderate	1	`3.3.0`
golang.org/x/net	`v0.50.0`	direct	moderate	10	`1.27.0-rc.3`
github.com/klauspost/compress	`v1.18.2`	indirect	unknown	1	`1.18.7`
golang.org/x/sys	`v0.41.0`	indirect	unknown	1	`0.44.0`
golang.org/x/text	`v0.34.0`	indirect	unknown	1	`0.39.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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — Go.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records