Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-11 03:21 UTC

Sellsuki / thai-address-database

ฐานข้อมูลที่อยู่ในไทย ไม่ต้องใช้ Server Side!

JavaScriptNo license detected★ 75 stars⑂ 59 forkssince Jul 2017forkView on GitHub ↗

Sellsuki/thai-address-database holds a health index of 41 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (68/100) and lowest on Security (34/100). It was last updated 37 days ago. 2 contributors account for most of its recent work.

41
overall / 100
Weak

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.

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

Ownership

SellsukiOrganization
8 followers26 public repossince Feb 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmthai-address-database0.0.3323,8982137 days ago

Metrics by category

Vitality

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

37Weak · 21% of overall
How it's scored
18/36Push recency — last push 37 days ago
2.8/36Commit cadence — 4/52 weeks with commits
9.4/18Commit volume — 10 commits in the last year
5/10OpenSSF Scorecard: Maintained — 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year10
human_commit_share1
days_since_last_push37
active_weeks_last_year4
How it's scored
16.2/27Ships releases — 1 version tags (no GitHub releases)
7.2/36Release recency — latest release 710 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv0.0.30
releases_from_tagsyes
days_since_latest_release710
mean_days_between_releases—
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?

37Weak · 17% of overall
How it's scored
30.3/60Stars — 75 stars
14.7/25Forks — 59 forks
0/15Watchers — 2 watchers
Inputs used
forks59
stars75
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesapi.codeclimate.com, travis-ci.org
has_pull_request_templateno
How it's scored
58.4/80Monthly downloads — 23,898 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesthai-address-database
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads23,898
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?

68Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.9/22.5Commit distribution — top contributor authored 47% of commits
13.5/13.5Contributor breadth — 11 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor2
contributors_sampled11
top_contributor_share0.472
How it's scored
0/42Issue resolution — no issues or no data
22.8/30PR acceptance — 22/29 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 4/13 approved changesets -- score normalized to 3
Inputs used
merged_prs22
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs7
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
6.9/25Owner reach — 8 followers of Sellsuki
22.4/25Track record — 26 public repos, account ~10 yr old
Inputs used
followers8
owner_typeOrganization
is_verifiedno
owner_loginSellsuki
public_repos26
account_age_days3,893

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 37 days ago
20/20Version history — 21 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesthai-address-database
ecosystemsnpm
any_deprecatedno
min_days_since_publish37

Engineering Quality

Are baseline engineering and documentation practices in place?

38Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 9 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

25At Risk
How it's scored
0/30README
0/25Documentation directory
15/15Documentation / homepage site — https://github.com/earthchie/jquery.Thailand.js
0/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicsjavascript, thai, address
has_wikino
homepagehttps://github.com/earthchie/jquery.Thailand.js
docs_sitehttps://github.com/earthchie/jquery.Thailand.js
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

34At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 4/13 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
3.8/7.5Maintained — 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 35 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.3
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
7.4/25Indirect dependencies free of known advisories — 2 affected: braces 3.0.3 (high 7.5), serialize-javascript 6.0.2 (high 8.1)
33.3/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 225 days ago
Inputs used
sourceosv
advisories3
affected_packages2
assessed_packages270
unassessed_packages0
affected_by_severityhigh 2
direct_affected_packages0
Matched the npm:thai-address-database@0.0.33 runtime dependency closure — what installing the published package pulls in — 270 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.

40Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
16/40Legible commit history — 30 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.3
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
0/11Static type checking
10/10Reproducible environment — lockfile
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json, yarn.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.02
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/9 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes10,492
source_files_sampled9
oversized_source_files0

Key facts

75GitHub stars
11contributors
10commits, last 12 months
37days since last push
1releases
2bus factor
0open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 59 ⇿
0Stars
59Forks
1Releases

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.

01020304050605932017-072021-102026-02
Major 0Minor 0Patch 1

Each point covers 8 days.

OpenSSF Scorecard 2.3 / 10
2.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-10-11 03:21 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 4/13 approved changesets -- score normalized to 3
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
5Maintained7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities35 existing vulnerabilities detected
Direct dependencies 14
RegistryPackageVersion constraintManifest
npm@babel/cli^7.25.9package.json
npm@babel/core^7.26.0package.json
npm@babel/eslint-parser^7.25.9package.json
npm@babel/preset-env^7.26.0package.json
npm@babel/register^7.25.9package.json
npm@babel/runtime^7.26.0package.json
npmcore-js^3.38.1package.json
npmeslint-plugin-promise^3.8.0package.json
npmeslint-plugin-standard^3.1.0package.json
npmmkdirp^3.0.1package.json
npmmocha^10.7.3package.json
npmregenerator-runtime^0.14.1package.json
npmrimraf^6.0.1package.json
npmwordcut^0.8.2package.json
All dependencies 20

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

RegistryPackageVersionRelation
npm@babel/cli^7.25.9direct
npm@babel/core^7.26.0direct
npm@babel/eslint-parser^7.25.9direct
npm@babel/preset-env^7.26.0direct
npm@babel/register^7.25.9direct
npm@babel/runtime^7.26.0direct
npmcore-js^3.38.1direct
npmeslint-plugin-promise^3.8.0direct
npmeslint-plugin-standard^3.1.0direct
npmmkdirp^3.0.1direct
npmmocha^10.7.3direct
npmregenerator-runtime^0.14.1direct
npmrimraf^6.0.1direct
npmwordcut^0.8.2direct
npm@eslint/eslintrc^3.1.0indirect
npm@eslint/js^9.13.0indirect
npmchai^4.5.0indirect
npmeslint^9.13.0indirect
npmeslint-config-standard^6.2.1indirect
npmeslint-friendly-formatter^3.0.0indirect
Dependency advisories 2

Installing npm:thai-address-database@0.0.33 pulls in 270 packages, direct and transitive: 2 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
braces3.0.3indirecthigh1—
serialize-javascript6.0.2indirecthigh27.0.5

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