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

pelias / whosonfirst

Importer for Who's on First gazetteer

JavaScriptMIT★ 33 stars⑂ 44 forkssince Sep 2015View on GitHub ↗

pelias/whosonfirst holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (74/100) and lowest on AI Readiness (43/100). It was last updated 58 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

PeliasOrganization
209 followers61 public repossince Jul 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmpelias-whosonfirst9.2.04,47513758 days ago

Metrics by category

Vitality

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

62Moderate · 21% of overall
How it's scored
18/36Push recency — last push 58 days ago
4.8/36Commit cadence — 7/52 weeks with commits
11.7/18Commit volume — 19 commits in the last year
7/10OpenSSF Scorecard: Maintained — 9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year19
human_commit_share0.98
days_since_last_push58
active_weeks_last_year7
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 58 days ago
19.8/27Release cadence — a release every ~53.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv9.2.0
releases_from_tagsno
days_since_latest_release58
mean_days_between_releases53.8
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?

65Good · 17% of overall
How it's scored
24.4/60Stars — 33 stars
13.6/25Forks — 44 forks
6.4/15Watchers — 15 watchers
Inputs used
forks44
stars33
watchers15
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_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
48.7/80Monthly downloads — 4,475 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespelias-whosonfirst
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads4,475
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?

74Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.6/22.5Commit distribution — top contributor authored 49% of commits
13.5/13.5Contributor breadth — 12 contributors
10/10OpenSSF Scorecard: Contributors — project has 13 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled12
top_contributor_share0.486
How it's scored
37.1/42Issue resolution — 88% of issues closed
25.9/30PR acceptance — 369/427 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/23 approved changesets -- score normalized to 0
Inputs used
merged_prs369
open_issues16
closed_issues121
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.883
closed_unmerged_prs58
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
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
16.7/25Owner reach — 209 followers of pelias
25/25Track record — 61 public repos, account ~12 yr old
Inputs used
followers209
owner_typeOrganization
is_verifiedno
owner_loginpelias
public_repos61
account_age_days4,504

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

47Weak · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests — 2 out of 8 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

53Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0.5/2.5CI-Tests — 2 out of 8 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/23 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 13 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
5.2/7.5Maintained — 9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
7.9/25Indirect dependencies free of known advisories — 3 affected: @hapi/joi 16.1.8 (high 7.5), glob 11.1.0 (moderate 5.3), minimatch 10.2.6 (moderate 5.3)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories4
affected_packages3
assessed_packages87
unassessed_packages0
affected_by_severityhigh 1, moderate 2
direct_affected_packages0
Matched the npm:pelias-whosonfirst@9.2.0 runtime dependency closure — what installing the published package pulls in — 87 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.

43Weak · 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 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.898
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 2 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.02
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/37 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes36,886
source_files_sampled37
oversized_source_files0

Key facts

33GitHub stars
12contributors
19commits, last 12 months
58days since last push
100releases
2bus factor
16open 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 ★ / 44 ⇿
0Stars
44Forks
96Releases

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.

010203040504122016-082021-062026-04
Major 6Minor 47Patch 43

Each point covers 9 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-11-21 19:11 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
2CI-Tests2 out of 8 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/23 approved changesets -- score normalized to 0
10Contributorsproject has 13 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
7Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 17
RegistryPackageVersion constraintManifest
npmasync^3.0.1package.json
npmbetter-sqlite313.0.3package.json
npmcombined-stream^1.0.5package.json
npmcommand-exists^1.2.9package.json
npmdownload-file-sync^1.0.4package.json
npmiso3166-1^0.5.0package.json
npmjoi^18.0.0package.json
npmlodash^4.5.1package.json
npmpelias-blacklist-stream^2.0.0package.json
npmpelias-config^7.0.0package.json
npmpelias-dbclient^4.4.0package.json
npmpelias-logger^2.0.0package.json
npmpelias-model^11.0.0package.json
npmthrough2^3.0.0package.json
npmthrough2-filter^3.0.0package.json
npmthrough2-map^3.0.0package.json
npmthrough2-sink^1.0.0package.json
All dependencies 25

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

RegistryPackageVersionRelation
npmasync^3.0.1direct
npmbetter-sqlite313.0.3direct
npmcombined-stream^1.0.5direct
npmcommand-exists^1.2.9direct
npmdownload-file-sync^1.0.4direct
npmiso3166-1^0.5.0direct
npmjoi^18.0.0direct
npmlodash^4.5.1direct
npmpelias-blacklist-stream^2.0.0direct
npmpelias-config^7.0.0direct
npmpelias-dbclient^4.4.0direct
npmpelias-logger^2.0.0direct
npmpelias-model^11.0.0direct
npmthrough2^3.0.0direct
npmthrough2-filter^3.0.0direct
npmthrough2-map^3.0.0direct
npmthrough2-sink^1.0.0direct
npmjshint^2.5.6indirect
npmpelias-mock-logger^2.0.0indirect
npmprecommit-hook^3.0.0indirect
npmproxyquire^2.0.0indirect
npmstream-mock^2.0.5indirect
npmtap-dot^2.0.0indirect
npmtape^5.0.0indirect
npmtemp^0.9.0indirect
Dependency advisories 3

Installing npm:pelias-whosonfirst@9.2.0 pulls in 87 packages, direct and transitive: 3 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
@hapi/joi16.1.8indirecthigh218.3.1
glob11.1.0indirectmoderate114.0.2
minimatch10.2.6indirectmoderate111.0.1

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.