Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 02:58 UTC

arcships / light-ocr

Fast, offline OCR for Node.js & C++. PP-OCRv6 with Core ML / WebGPU hardware acceleration — recognize text in images with confidence scores & coordinates. npm: @arcships/light-ocr

C++ · JavaScriptApache-2.0★ 503 stars⑂ 42 forkssince Jul 2026View on GitHub ↗

KindNetwork servicehow this is determined

arcships/light-ocr holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Community & Adoption (72/100) and lowest on Sustainability & Governance (55/100). It was last updated 40 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 64 is calibrated to 73 on the published index scale (record calibration 2026-08-02).

Ownership

arcshipsOrganization

20 followers11 public repossince Apr 2026

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish
npm	@arcships/light-ocr-document	0.1.0	126	4	49 days ago
npm	@arcships/light-ocr-medium	0.1.0	357	6	53 days ago
npm	@arcships/light-ocr-tiny	0.1.0	352	6	53 days ago
npm	@arcships/light-ocr	0.5.7	8,720	13	40 days ago
npm	@arcships/light-ocr-model-ppocrv6-medium	0.1.0	411	1	53 days ago

Metrics by category

Vitality

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

63Moderate · 21% of overall

Development activity

39Weak

How it's scored

18/36	Push recency — last push 40 days ago
2.8/36	Commit cadence — 4/52 weeks with commits
18/18	Commit volume — 145 commits in the last year
0/10	OpenSSF Scorecard: Maintained — project was created within the last 90 days. Please review its contents carefully

Inputs used

commits_last_year	145
human_commit_share	1
days_since_last_push	40
active_weeks_last_year	4

Release discipline

100Exceptional

How it's scored

27/27	Ships releases — 9 releases published
36/36	Release recency — latest release 40 days ago
27/27	Release cadence — a release every ~2 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	9
latest_release_tag	v0.5.7
releases_from_tags	no
days_since_latest_release	40
mean_days_between_releases	2

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?

72Good · 17% of overall

Popularity & adoption

57Moderate

How it's scored

43.8/60	Stars — 503 stars
13.4/25	Forks — 42 forks
0/15	Watchers — 1 watchers

Inputs used

forks	42
stars	503
watchers	1
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

92Excellent

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (Apache-2.0)
18/18	CONTRIBUTING guide
13.5/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	yes
readme_badge_services	github.com, shields.io
has_pull_request_template	yes

Ecosystem adoption (downloads)

67Good

How it's scored

53.3/80	Monthly downloads — 9,966 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	@arcships/light-ocr-document, @arcships/light-ocr-medium, @arcships/light-ocr-tiny, @arcships/light-ocr, @arcships/light-ocr-model-ppocrv6-medium
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	9,966
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?

55Moderate · 23% of overall

Maintainer resilience (bus factor)

18Critical

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	4
top_contributor_share	0.966

Issue & PR responsiveness

69Good

How it's scored

31.5/42	Issue resolution — 75% of issues closed
28.9/30	PR acceptance — 51/53 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — Found 1/23 approved changesets -- score normalized to 0

Inputs used

merged_prs	51
open_issues	2
closed_issues	6
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.75
closed_unmerged_prs	2
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

48Weak

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
9.5/25	Owner reach — 20 followers of arcships
8.8/25	Track record — 11 public repos, account ~0 yr old

Inputs used

followers	20
owner_type	Organization
is_verified	no
owner_login	arcships
public_repos	11
account_age_days	166

Package maintenance

100Exceptional

How it's scored

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

Inputs used

packages	@arcships/light-ocr-document, @arcships/light-ocr-medium, @arcships/light-ocr-tiny, @arcships/light-ocr, @arcships/light-ocr-model-ppocrv6-medium
ecosystems	npm
any_deprecated	no
min_days_since_publish	40

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall

Engineering practices

60Moderate

How it's scored

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

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

85Excellent

How it's scored

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

Inputs used

topics	apple-silicon, computer-vision, coreml, cpp17, d3d12, image-processing, machine-learning, napi, native-addon, nodejs, nvidia, ocr, ocr-recognition, offline-ocr, paddleocr, ppocr, text-recognition, typescript, vulkan, webgpu
has_wiki	yes
homepage	—
docs_site	—
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?

62Moderate · 16% of overall

Security posture

53Moderate

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
1.5/2.5	CI-Tests — 9 out of 14 merged PRs checked by a CI test -- score normalized to 6
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 1/23 approved changesets -- score normalized to 0
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
0/7.5	Dependency-Update-Tool — no update tool detected
5/5	Fuzzing — project is fuzzed
2.5/2.5	License — license file detected
0/7.5	Maintained — project was created within the last 90 days. Please review its contents carefully
5/5	Packaging — packaging workflow detected
4/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
5/5	Security-Policy — security policy file detected
0/7.5	Signed-Releases — no data
7.5/7.5	Token-Permissions — GitHub workflow tokens follow principle of least privilege
3/7.5	Vulnerabilities — 6 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	17
scorecard_version	v5.5.0
checks_inconclusive	1
scorecard_aggregate	5.3

Excluded from scoring (no data or not applicable): 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	8
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:@arcships/light-ocr@0.5.7 runtime dependency closure — what installing the published package pulls in — 8 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.

71Good · 4% of overall

Agent context & guidance

85Excellent

How it's scored

45/45	Agent instructions — AGENTS.md
0/15	Machine-readable docs (llms.txt)
40/40	Legible commit history — 99 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.99
agent_instruction_files	AGENTS.md
agent_instruction_max_bytes	1,361

Verify loop (build / test / typecheck)

51Moderate

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — C++ (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
8/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8

Inputs used

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

Code legibility for models

99Exceptional

How it's scored

45/45	Type-checkable code — C++ (statically typed)
54.2/55	Manageable file sizes — 3/198 source files over 60KB

Inputs used

primary_language	C++
largest_source_bytes	97,796
source_files_sampled	198
oversized_source_files	3

Key facts

503GitHub stars

4contributors

145commits, last 12 months

40days since last push

9releases

1bus factor

2open 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 ★ / 42 ⇿

0Stars

42Forks

9Releases

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 8

OpenSSF Scorecard 5.3 / 10

5.3aggregate

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-15 02:57 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
6	CI-Tests	9 out of 14 merged PRs checked by a CI test -- score normalized to 6
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 1/23 approved changesets -- score normalized to 0
3	Contributors	project has 1 contributing companies or organizations -- score normalized to 3
10	Dangerous-Workflow	no dangerous workflow patterns detected
0	Dependency-Update-Tool	no update tool detected
10	Fuzzing	project is fuzzed
10	License	license file detected
0	Maintained	project was created within the last 90 days. Please review its contents carefully
10	Packaging	packaging workflow detected
8	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 8
0	SAST	SAST tool is not run on all commits -- score normalized to 0
10	Security-Policy	security policy file detected
n/a	Signed-Releases	no releases found
10	Token-Permissions	GitHub workflow tokens follow principle of least privilege
4	Vulnerabilities	6 existing vulnerabilities detected

Direct dependencies 10

Registry	Package	Version constraint	Manifest
npm	@arcships/light-ocr	`0.5.7`	packages/light-ocr-document/package.json
npm	@arcships/light-ocr-model-ppocrv6-medium	`0.1.0`	packages/light-ocr-medium/package.json
npm	@arcships/light-ocr-runtime	`0.1.7`	packages/light-ocr-medium/package.json
npm	@arcships/light-ocr	`0.4.0`	packages/light-ocr-server/package.json
npm	express	`5.2.1`	packages/light-ocr-server/package.json
npm	multer	`2.2.0`	packages/light-ocr-server/package.json
npm	@arcships/light-ocr-model-ppocrv6-tiny	`0.1.0`	packages/light-ocr-tiny/package.json
npm	@arcships/light-ocr-runtime	`0.1.7`	packages/light-ocr-tiny/package.json
npm	@arcships/light-ocr-model-ppocrv6-small	`0.3.4`	packages/light-ocr/package.json
npm	@arcships/light-ocr-runtime	`0.1.7`	packages/light-ocr/package.json

All dependencies 107

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

Registry	Package	Version	Relation
npm	@arcships/light-ocr	`0.4.0`	direct
npm	@arcships/light-ocr	`0.5.7`	direct
npm	@arcships/light-ocr-model-ppocrv6-medium	`0.1.0`	direct
npm	@arcships/light-ocr-model-ppocrv6-small	`0.3.4`	direct
npm	@arcships/light-ocr-model-ppocrv6-tiny	`0.1.0`	direct
npm	@arcships/light-ocr-runtime	`0.1.0`	direct
npm	@arcships/light-ocr-runtime	`0.1.7`	direct
npm	express	`5.2.1`	direct
npm	multer	`2.2.0`	direct
npm	@arcships/light-ocr-darwin-arm64	`0.4.0`	indirect
npm	@arcships/light-ocr-darwin-arm64	`0.5.7`	indirect
npm	@arcships/light-ocr-darwin-x64	`0.4.0`	indirect
npm	@arcships/light-ocr-darwin-x64	`0.5.7`	indirect
npm	@arcships/light-ocr-document	`0.1.3`	indirect
npm	@arcships/light-ocr-linux-arm64-gnu	`0.4.0`	indirect
npm	@arcships/light-ocr-linux-arm64-gnu	`0.5.7`	indirect
npm	@arcships/light-ocr-linux-x64-gnu	`0.4.0`	indirect
npm	@arcships/light-ocr-linux-x64-gnu	`0.5.7`	indirect
npm	@arcships/light-ocr-medium	`0.1.6`	indirect
npm	@arcships/light-ocr-server	`0.1.1`	indirect
npm	@arcships/light-ocr-tiny	`0.1.6`	indirect
npm	@arcships/light-ocr-win32-arm64	`0.4.0`	indirect
npm	@arcships/light-ocr-win32-arm64	`0.5.7`	indirect
npm	@arcships/light-ocr-win32-x64	`0.4.0`	indirect
npm	@arcships/light-ocr-win32-x64	`0.5.7`	indirect
npm	@types/node	`22.20.1`	indirect
npm	accepts	`2.0.0`	indirect
npm	append-field	`1.0.0`	indirect
npm	body-parser	`2.3.0`	indirect
npm	buffer-from	`1.1.2`	indirect
npm	busboy	`1.6.0`	indirect
npm	bytes	`3.1.2`	indirect
npm	call-bind-apply-helpers	`1.0.2`	indirect
npm	call-bound	`1.0.4`	indirect
npm	concat-stream	`2.0.0`	indirect
npm	content-disposition	`1.1.0`	indirect
npm	content-type	`1.0.5`	indirect
npm	content-type	`2.0.0`	indirect
npm	cookie	`0.7.2`	indirect
npm	cookie-signature	`1.2.2`	indirect
npm	debug	`4.4.3`	indirect
npm	depd	`2.0.0`	indirect
npm	dunder-proto	`1.0.1`	indirect
npm	ee-first	`1.1.1`	indirect
npm	encodeurl	`2.0.0`	indirect
npm	es-define-property	`1.0.1`	indirect
npm	es-errors	`1.3.0`	indirect
npm	es-object-atoms	`1.1.2`	indirect
npm	escape-html	`1.0.3`	indirect
npm	etag	`1.8.1`	indirect
npm	finalhandler	`2.1.1`	indirect
npm	forwarded	`0.2.0`	indirect
npm	fresh	`2.0.0`	indirect
npm	function-bind	`1.1.2`	indirect
npm	get-intrinsic	`1.3.0`	indirect
npm	get-proto	`1.0.1`	indirect
npm	gopd	`1.2.0`	indirect
npm	has-symbols	`1.1.0`	indirect
npm	hasown	`2.0.4`	indirect
npm	http-errors	`2.0.1`	indirect
npm	iconv-lite	`0.7.3`	indirect
npm	inherits	`2.0.4`	indirect
npm	ipaddr.js	`1.9.1`	indirect
npm	is-promise	`4.0.0`	indirect
npm	math-intrinsics	`1.1.0`	indirect
npm	media-typer	`0.3.0`	indirect
npm	media-typer	`1.1.0`	indirect
npm	merge-descriptors	`2.0.0`	indirect
npm	mime-db	`1.52.0`	indirect
npm	mime-db	`1.54.0`	indirect
npm	mime-types	`2.1.35`	indirect
npm	mime-types	`3.0.2`	indirect
npm	ms	`2.1.3`	indirect
npm	negotiator	`1.0.0`	indirect
npm	object-inspect	`1.13.4`	indirect
npm	on-finished	`2.4.1`	indirect
npm	once	`1.4.0`	indirect
npm	parseurl	`1.3.3`	indirect
npm	path-to-regexp	`8.4.2`	indirect
npm	proxy-addr	`2.0.7`	indirect
npm	qs	`6.15.3`	indirect
npm	range-parser	`1.3.0`	indirect
npm	raw-body	`3.0.2`	indirect
npm	readable-stream	`3.6.2`	indirect
npm	router	`2.2.0`	indirect
npm	safe-buffer	`5.2.1`	indirect
npm	safer-buffer	`2.1.2`	indirect
npm	send	`1.2.1`	indirect
npm	serve-static	`2.2.1`	indirect
npm	setprototypeof	`1.2.0`	indirect
npm	side-channel	`1.1.1`	indirect
npm	side-channel-list	`1.0.1`	indirect
npm	side-channel-map	`1.0.1`	indirect
npm	side-channel-weakmap	`1.0.2`	indirect
npm	statuses	`2.0.2`	indirect
npm	streamsearch	`1.1.0`	indirect
npm	string_decoder	`1.3.0`	indirect
npm	toidentifier	`1.0.1`	indirect
npm	type-is	`1.6.18`	indirect
npm	type-is	`2.1.0`	indirect
npm	typedarray	`0.0.6`	indirect
npm	typescript	`5.9.3`	indirect
npm	undici-types	`6.21.0`	indirect
npm	unpipe	`1.0.0`	indirect
npm	util-deprecate	`1.0.2`	indirect
npm	vary	`1.1.2`	indirect
npm	wrappy	`1.0.2`	indirect

Dependency advisories 0

Installing npm:@arcships/light-ocr@0.5.7 pulls in 8 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