Public record
Software health reportschema 0.27.0 · metrics 2.5.0 · 2026-08-01 01:11 UTC

PT-Perkasa-Pilar-Utama / ppu-paddle-ocr

Lightweight, probably the fastest PaddleOCR SDK in TypeScript. Multilingual Support. Runs anywhere JavaScript runs: Node.js, Bun, Deno, mobile react-native, web browsers, and browser extensions. Docker & CLI supported. The official SDK is browser-only.

TypeScript · HTMLMIT★ 113 stars⑂ 14 forkssince May 2025View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

PT-Perkasa-Pilar-Utama/ppu-paddle-ocr holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Security (92/100) and lowest on AI Readiness (57/100). It was last updated today. A single contributor accounts for most of its recent work.

90
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.

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

Ownership

18 followers30 public repossince Nov 2024

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

Package ecosystems

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
13.2/36Commit cadence — 19/52 weeks with commits
18/18Commit volume — 305 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year305
human_commit_share0.88
days_since_last_push0
active_weeks_last_year19

Release discipline

98Exceptional
How it's scored
27/27Ships releases — 27 releases published
36/36Release recency — latest release 9 days ago
27/27Release cadence — a release every ~6.6 days
8/10OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count27
latest_release_tagv6.2.0
releases_from_tagsno
days_since_latest_release9
mean_days_between_releases6.6

Community & Adoption

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

69Good · 17% of overall
How it's scored
33.2/60Stars — 113 stars
9.3/25Forks — 14 forks
2.7/15Watchers — 4 watchers
Inputs used
forks14
stars113
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
60.4/80Monthly downloads — 33,862 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesppu-paddle-ocr
dependents
ecosystemsnpm
total_downloads
monthly_downloads33,862
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.4/22.5Commit distribution — top contributor authored 98% of commits
5.4/13.5Contributor breadth — 4 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.983
How it's scored
42/42Issue resolution — 100% of issues closed
24.3/30PR acceptance — 55/68 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/8 approved changesets -- score normalized to 0
Inputs used
merged_prs55
open_issues0
closed_issues15
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs13
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): newcomer_pr_acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
9.2/25Owner reach — 18 followers of PT-Perkasa-Pilar-Utama
14.3/25Track record — 30 public repos, account ~1 yr old
Inputs used
followers18
owner_typeOrganization
is_verified
owner_loginPT-Perkasa-Pilar-Utama
public_repos30
account_age_days632

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 9 days ago
20/20Version history — 58 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesppu-paddle-ocr
ecosystemsnpm
any_deprecatedno
min_days_since_publish9

Engineering Quality

Are baseline engineering and documentation practices in place?

81Excellent · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 8 out of 8 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://ppu-paddle-ocr.snowfluke.workers.dev/
10/10Repository description
10/10Topics — 20 topics
10/10Wiki
Inputs used
topicsbun, computer-vision, image-processing, image-text-extraction, javascript-ocr, node-js, ocr, onnxruntime, optical-character-recognition, paddleocr, paddlepaddle, text-detection, text-extraction, text-recognition, typescript-ocr, deno, nodejs, docker, cli-tool, react-native
has_wikiyes
homepagehttps://ppu-paddle-ocr.snowfluke.workers.dev/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

92Excellent · 16% of overall

Security posture

90Excellent
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
6.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 8 out of 8 merged PRs checked by a CI test -- score normalized to 10
2.5/2.5CII-Best-Practices — badge detected: Gold
0/7.5Code-Review — Found 0/8 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
6/7.5Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate9

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages14
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:ppu-paddle-ocr@6.2.0 runtime dependency closure — what installing the published package pulls in — 14 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.

57Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 88 of 88 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — apps/serve/tsconfig.json, tsconfig.json
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 12 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configsapps/serve/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.12
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/114 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes14,281
source_files_sampled114
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — examples, notebooks
Inputs used
example_dirsexamples, notebooks
has_mcp_signalno
api_schema_files

Key facts

113GitHub stars
4contributors
305commits, last 12 months
0days since last push
27releases
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 ★ / 14 ⇿
0Stars
14Forks
24Releases

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.

03581013151412025-072026-012026-07
Major 2Minor 10Patch 12
OpenSSF Scorecard 9.0 / 10
9.0aggregate

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-01 01:10 UTC

10Binary-Artifactsno binaries found in the repo
9Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests8 out of 8 merged PRs checked by a CI test -- score normalized to 10
10CII-Best-Practicesbadge detected: Gold
0Code-ReviewFound 0/8 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmppu-ocv^4.0.0package.json
All dependencies 22

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

RegistryPackageVersionRelation
npmppu-ocv^4.0.0direct
npm@hono/zod-openapi^1.4.0indirect
npm@hono/zod-validator^0.8.0indirect
npm@napi-rs/canvas^1.0.2indirect
npm@scalar/hono-api-reference^0.11.9indirect
npm@types/bun^1.3.14indirect
npm@types/uglify-js^3.17.5indirect
npmcanvas^3.2.3indirect
npmfast-check^4.9.0indirect
npmhono^4.12.29indirect
npmhusky^9.1.7indirect
npmlint-staged^17.0.8indirect
npmonnxruntime-common^1.27.0indirect
npmonnxruntime-node^1.27.0indirect
npmonnxruntime-react-native^1.24.3indirect
npmonnxruntime-web^1.27.0indirect
npmoxfmt^0.58.0indirect
npmoxlint^1.73.0indirect
npmtsx^4.23.0indirect
npmtypescript^7.0.2indirect
npmuglify-js^3.19.3indirect
npmzod^4.4.3indirect
Dependency advisories 0

Installing npm:ppu-paddle-ocr@6.2.0 pulls in 14 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

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.5.0, schema v0.27.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.