Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 10:27 UTC

JoshGlazebrook / socks

Fully featured SOCKS proxy client supporting SOCKSv4, SOCKSv4a, and SOCKSv5. Includes Bind and Associate functionality.

TypeScriptMIT★ 328 stars⑂ 39 forkssince Dec 2013View on GitHub ↗

#socks-proxy #socks #socket #client #socks-protocol #socks-client #typescript #socks5 #socks4a #socks4

JoshGlazebrook/socks holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Engineering Quality (80/100) and lowest on Security (57/100). It was last updated 13 days ago. A single contributor accounts for most of its recent work.

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.

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

Ownership

Josh Glazebrook-LopezPersonal account

31 followers22 public repossince Jan 2013

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	Tags
npm	socks	2.8.10	217,166,720	56	13 days ago	socks proxy tor socks-4 socks-5 socks4 socks5

Metrics by category

Vitality

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

63Moderate · 21% of overall

Development activity

44Weak

How it's scored

28.8/36	Push recency — last push 13 days ago
2.1/36	Commit cadence — 3/52 weeks with commits
8.6/18	Commit volume — 8 commits in the last year
4/10	OpenSSF Scorecard: Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4

Inputs used

commits_last_year	8
human_commit_share	0.98
days_since_last_push	13
active_weeks_last_year	3

Release discipline

92Excellent

How it's scored

27/27	Ships releases — 35 releases published
36/36	Release recency — latest release 13 days ago
19.8/27	Release cadence — a release every ~103.7 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	35
latest_release_tag	2.8.10
releases_from_tags	no
days_since_latest_release	13
mean_days_between_releases	103.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?

66Good · 17% of overall

Popularity & adoption

58Moderate

How it's scored

40.8/60	Stars — 328 stars
13.2/25	Forks — 39 forks
4.3/15	Watchers — 7 watchers

Inputs used

forks	39
stars	328
watchers	7
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

50Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
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	2
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	coveralls.io, travis-ci.org
has_pull_request_template	no

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 217,166,720 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	socks
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	217,166,720
unverified_packages_excluded	—

Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

60Moderate · 23% of overall

Maintainer resilience (bus factor)

30At Risk

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	19
top_contributor_share	0.776

Issue & PR responsiveness

72Good

How it's scored

42/42	Issue resolution — 100% of issues closed
16.1/30	PR acceptance — 37/69 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15	OpenSSF Scorecard: Code-Review — Found 9/28 approved changesets -- score normalized to 3

Inputs used

merged_prs	37
open_issues	0
closed_issues	57
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	1
prs_decided_30d	1
issue_closed_ratio	1
closed_unmerged_prs	32
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): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

53Moderate

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
10.8/25	Owner reach — 31 followers of JoshGlazebrook
21.9/25	Track record — 22 public repos, account ~13 yr old

Inputs used

followers	31
owner_type	User
is_verified	—
owner_login	JoshGlazebrook
public_repos	22
account_age_days	4,993

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 npm
35/35	Publish recency — latest publish 13 days ago
20/20	Version history — 56 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	socks
ecosystems	npm
any_deprecated	no
min_days_since_publish	13

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall

Engineering practices

66Good

How it's scored

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

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://www.npmjs.com/package/socks
10/10	Repository description
10/10	Topics — 10 topics
10/10	Wiki

Inputs used

topics	socks-proxy, socks, socket, client, socks-protocol, socks-client, typescript, socks5, socks4a, socks4
has_wiki	yes
homepage	https://www.npmjs.com/package/socks
docs_site	https://www.npmjs.com/package/socks
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?

57Moderate · 16% of overall

Security posture

46Weak

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

Inputs used

source	openssf_scorecard
checks_evaluated	16
scorecard_version	v5.5.0
checks_inconclusive	2
scorecard_aggregate	4.6

Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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
25/25	Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	0
affected_packages	0
assessed_packages	2
unassessed_packages	0
affected_by_severity	none
direct_affected_packages	0

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:socks@2.8.10 runtime dependency closure — what installing the published package pulls in — 2 packages. 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.

64Moderate · 4% of overall

Agent context & guidance

17Critical

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.316
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

71Good

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
11/11	Lint / format config — eslint.config.mjs
11/11	Static type checking — tsconfig.json
10/10	Reproducible environment — lockfile
6/10	Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
8/8	Automated maintenance — 2 of the last 100 commits are automated dependency updates
3/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3

Inputs used

has_nix	no
has_tests	yes
lockfiles	package-lock.json
has_dockerfile	no
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	yes
typecheck_configs	tsconfig.json
agent_commit_share	0.03
toolchain_manifests	—
dependency_bot_commit_share	0.02

Code legibility for models

100Exceptional

How it's scored

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

Inputs used

primary_language	TypeScript
largest_source_bytes	32,139
source_files_sampled	15
oversized_source_files	0

Machine-readable interfaces

100Exceptional

How it's scored

0/40	API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20	MCP server — not applicable to this kind of software
40/40	Runnable examples — examples

Inputs used

example_dirs	examples
has_mcp_signal	no
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

328GitHub stars

19contributors

8commits, last 12 months

13days since last push

35releases

1bus factor

0open issues

npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 39 ⇿

0Stars

39Forks

25Releases

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 4Patch 21

Each point covers 10 days.

OpenSSF Scorecard 4.6 / 10

4.6aggregate

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-16 10:27 UTC

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

Direct dependencies 2

Registry	Package	Version constraint	Manifest
npm	ip-address	`^10.1.1`	package.json
npm	smart-buffer	`^4.2.0`	package.json

All dependencies 129

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

Registry	Package	Version	Relation
npm	ip-address	`10.7.0`	direct
npm	smart-buffer	`4.2.0`	direct
npm	@cspotcode/source-map-support	`0.8.1`	indirect
npm	@eslint-community/eslint-utils	`4.10.1`	indirect
npm	@eslint-community/regexpp	`4.12.2`	indirect
npm	@eslint/config-array	`0.23.5`	indirect
npm	@eslint/config-helpers	`0.7.0`	indirect
npm	@eslint/core	`1.2.1`	indirect
npm	@eslint/js	`10.0.1`	indirect
npm	@eslint/object-schema	`3.0.5`	indirect
npm	@eslint/plugin-kit	`0.7.2`	indirect
npm	@humanfs/core	`0.19.2`	indirect
npm	@humanfs/node	`0.16.8`	indirect
npm	@humanfs/types	`0.15.0`	indirect
npm	@humanwhocodes/module-importer	`1.0.1`	indirect
npm	@humanwhocodes/retry	`0.4.3`	indirect
npm	@jridgewell/resolve-uri	`3.1.2`	indirect
npm	@jridgewell/sourcemap-codec	`1.6.0`	indirect
npm	@jridgewell/trace-mapping	`0.3.9`	indirect
npm	@tsconfig/node10	`1.0.13`	indirect
npm	@tsconfig/node12	`1.0.11`	indirect
npm	@tsconfig/node14	`1.0.3`	indirect
npm	@tsconfig/node16	`1.0.4`	indirect
npm	@types/esrecurse	`4.3.1`	indirect
npm	@types/estree	`1.0.9`	indirect
npm	@types/json-schema	`7.0.15`	indirect
npm	@types/mocha	`10.0.10`	indirect
npm	@types/node	`26.4.1`	indirect
npm	@typescript-eslint/eslint-plugin	`8.69.0`	indirect
npm	@typescript-eslint/parser	`8.69.0`	indirect
npm	@typescript-eslint/project-service	`8.69.0`	indirect
npm	@typescript-eslint/scope-manager	`8.69.0`	indirect
npm	@typescript-eslint/tsconfig-utils	`8.69.0`	indirect
npm	@typescript-eslint/type-utils	`8.69.0`	indirect
npm	@typescript-eslint/types	`8.69.0`	indirect
npm	@typescript-eslint/typescript-estree	`8.69.0`	indirect
npm	@typescript-eslint/utils	`8.69.0`	indirect
npm	@typescript-eslint/visitor-keys	`8.69.0`	indirect
npm	acorn	`8.18.0`	indirect
npm	acorn-jsx	`5.3.2`	indirect
npm	acorn-walk	`8.3.5`	indirect
npm	ajv	`6.15.0`	indirect
npm	arg	`4.1.3`	indirect
npm	argparse	`2.0.1`	indirect
npm	balanced-match	`4.0.4`	indirect
npm	brace-expansion	`5.0.9`	indirect
npm	browser-stdout	`1.3.1`	indirect
npm	chokidar	`5.0.0`	indirect
npm	create-require	`1.1.1`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	debug	`4.4.3`	indirect
npm	deep-is	`0.1.4`	indirect
npm	diff	`4.0.4`	indirect
npm	diff	`9.0.0`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	eslint	`10.9.1`	indirect
npm	eslint-scope	`9.1.2`	indirect
npm	eslint-visitor-keys	`3.4.3`	indirect
npm	eslint-visitor-keys	`5.0.1`	indirect
npm	espree	`11.2.0`	indirect
npm	esquery	`1.7.0`	indirect
npm	esrecurse	`4.3.0`	indirect
npm	estraverse	`5.3.0`	indirect
npm	esutils	`2.0.3`	indirect
npm	fast-deep-equal	`3.1.3`	indirect
npm	fast-json-stable-stringify	`2.1.0`	indirect
npm	fast-levenshtein	`2.0.6`	indirect
npm	fdir	`6.5.0`	indirect
npm	file-entry-cache	`8.0.0`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat-cache	`4.0.1`	indirect
npm	flatted	`3.4.4`	indirect
npm	glob	`13.0.6`	indirect
npm	glob-parent	`6.0.2`	indirect
npm	has-flag	`4.0.0`	indirect
npm	ignore	`5.3.2`	indirect
npm	ignore	`7.0.8`	indirect
npm	imurmurhash	`0.1.4`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-path-inside	`3.0.3`	indirect
npm	is-unicode-supported	`0.1.0`	indirect
npm	isexe	`2.0.0`	indirect
npm	js-yaml	`5.4.1`	indirect
npm	json-buffer	`3.0.1`	indirect
npm	json-schema-traverse	`0.4.1`	indirect
npm	json-stable-stringify-without-jsonify	`1.0.1`	indirect
npm	keyv	`4.5.4`	indirect
npm	levn	`0.4.1`	indirect
npm	locate-path	`6.0.0`	indirect
npm	lru-cache	`11.5.2`	indirect
npm	make-error	`1.3.6`	indirect
npm	minimatch	`10.2.6`	indirect
npm	minipass	`7.1.3`	indirect
npm	mocha	`12.0.0`	indirect
npm	ms	`2.1.3`	indirect
npm	natural-compare	`1.4.0`	indirect
npm	optionator	`0.9.4`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-key	`3.1.1`	indirect
npm	path-scurry	`2.0.2`	indirect
npm	picocolors	`1.1.1`	indirect
npm	picomatch	`4.0.7`	indirect
npm	prelude-ls	`1.2.1`	indirect
npm	prettier	`3.9.6`	indirect
npm	punycode	`2.3.1`	indirect
npm	readdirp	`5.1.1`	indirect
npm	semver	`7.8.5`	indirect
npm	serialize-javascript	`7.1.1`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	strip-json-comments	`5.0.3`	indirect
npm	supports-color	`8.1.1`	indirect
npm	tinyglobby	`0.2.17`	indirect
npm	ts-api-utils	`2.5.0`	indirect
npm	ts-node	`10.9.2`	indirect
npm	type-check	`0.4.0`	indirect
npm	typescript	`5.9.3`	indirect
npm	typescript-eslint	`8.69.0`	indirect
npm	undici-types	`8.3.0`	indirect
npm	uri-js	`4.4.1`	indirect
npm	v8-compile-cache-lib	`3.0.1`	indirect
npm	which	`2.0.2`	indirect
npm	word-wrap	`1.2.5`	indirect
npm	workerpool	`10.0.3`	indirect
npm	yn	`3.1.1`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 0

Installing npm:socks@2.8.10 pulls in 2 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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 — npm.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records