Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-18 22:42 UTC

pelias / openstreetmap

Import pipeline for OSM in to Pelias

JavaScriptMIT★ 121 stars⑂ 77 forkssince Apr 2014View on GitHub ↗

pelias/openstreetmap holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Vitality (75/100) and lowest on AI Readiness (39/100). It was last updated 24 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

PeliasOrganization
208 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 publishTags
npmpelias-openstreetmap9.5.01,84416924 days agopeliasstreamopenstreetmapelasticsearch

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
28.8/36Push recency — last push 24 days ago
5.5/36Commit cadence — 8/52 weeks with commits
14.7/18Commit volume — 42 commits in the last year
10/10OpenSSF Scorecard: Maintained — 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year42
human_commit_share1
days_since_last_push24
active_weeks_last_year8

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 84 releases published
36/36Release recency — latest release 24 days ago
27/27Release cadence — a release every ~17.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count84
latest_release_tagv9.5.0
releases_from_tagsno
days_since_latest_release24
mean_days_between_releases17.1
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?

68Good · 17% of overall
How it's scored
33.7/60Stars — 121 stars
15.7/25Forks — 77 forks
7/15Watchers — 19 watchers
Inputs used
forks77
stars121
watchers19
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
43.5/80Monthly downloads — 1,844 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespelias-openstreetmap
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads1,844
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
13.2/22.5Commit distribution — top contributor authored 41% of commits
13.5/13.5Contributor breadth — 21 contributors
10/10OpenSSF Scorecard: Contributors — project has 11 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled21
top_contributor_share0.414
How it's scored
37.5/42Issue resolution — 89% of issues closed
24.7/30PR acceptance — 399/485 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_prs399
open_issues12
closed_issues99
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.892
closed_unmerged_prs86
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 — 208 followers of pelias
25/25Track record — 61 public repos, account ~12 yr old
Inputs used
followers208
owner_typeOrganization
is_verifiedno
owner_loginpelias
public_repos61
account_age_days4,470

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

60Moderate · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 5 out of 5 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
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?

49Weak · 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
2.5/2.5CI-Tests — 5 out of 5 merged PRs checked by a CI test -- score normalized to 10
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 11 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
7.5/7.5Maintained — 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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_aggregate5.1
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
20.2/35Direct dependencies free of known advisories — 1 affected: joi 14.3.1 (moderate 5.3)
3.3/25Indirect dependencies free of known advisories — 10 affected: braces 2.3.2 (high 7.5), decode-uri-component 0.2.2 (high 7.5), express-handlebars 3.1.0 (high 8.6), +7 more
20.6/40No advisories left outstanding — 6 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,144 days ago
Inputs used
sourceosv
advisories13
affected_packages11
assessed_packages496
unassessed_packages0
affected_by_severityhigh 4, moderate 6, low 1
direct_affected_packages1
Matched the npm:pelias-openstreetmap@9.5.0 runtime dependency closure — what installing the published package pulls in — 496 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.

39Weak · 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 — 80 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.8
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
0/8Automated maintenance — no automated dependency updates observed
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
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/64 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes21,224
source_files_sampled64
oversized_source_files0

Key facts

121GitHub stars
21contributors
42commits, last 12 months
24days since last push
84releases
2bus factor
12open 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 ★ / 77 ⇿
0Stars
77Forks
77Releases

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.

0204060807622015-012020-102026-07
Major 4Minor 44Patch 29

Each point covers 11 days.

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-18 22:42 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests5 out of 5 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/23 approved changesets -- score normalized to 0
10Contributorsproject has 11 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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 16
RegistryPackageVersion constraintManifest
npmasync^3.0.1package.json
npmcombined-stream^1.0.5package.json
npmextend^3.0.0package.json
npmis-object^1.0.1package.json
npmiso-639-3^1.0.0package.json
npmjoi^14.0.0package.json
npmlodash^4.17.4package.json
npmpbf2json^7.0.0package.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
npmpelias-wof-admin-lookup^8.0.0package.json
npmthrough2^3.0.0package.json
npmthrough2-sink^1.0.0package.json
All dependencies 28

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

RegistryPackageVersionRelation
npmasync^3.0.1direct
npmcombined-stream^1.0.5direct
npmextend^3.0.0direct
npmis-object^1.0.1direct
npmiso-639-3^1.0.0direct
npmjoi^14.0.0direct
npmlodash^4.17.4direct
npmpbf2json^7.0.0direct
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
npmpelias-wof-admin-lookup^8.0.0direct
npmthrough2^3.0.0direct
npmthrough2-sink^1.0.0direct
npmcolors^1.1.2indirect
npmdeep-diff^1.0.0indirect
npmistanbul^0.4.3indirect
npmjshint^2.10.3indirect
npmnaivedb^1.0.7indirect
npmpelias-mock-logger^2.0.0indirect
npmprecommit-hook^3.0.0indirect
npmproxyquire^2.0.0indirect
npmstream-mock^2.0.3indirect
npmtaginfo^1.0.1indirect
npmtap-spec^5.0.0indirect
npmtape^5.0.0indirect
Dependency advisories 11

Installing npm:pelias-openstreetmap@9.5.0 pulls in 496 packages, direct and transitive: 11 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
braces2.3.2indirecthigh23.0.3
decode-uri-component0.2.2indirecthigh10.5.0
express-handlebars3.1.0indirecthigh15.3.1
hoek6.1.3indirecthigh19.0.3
joi14.3.1directmoderate218.2.9
csv-parse4.16.3indirectmoderate17.0.2
csv-parse6.2.1indirectmoderate17.0.2
highlight.js9.18.5indirectmoderate110.4.1
micromatch3.1.10indirectmoderate14.0.8
sprintf-js1.0.3indirectmoderate1—
@hapi/joi16.1.8indirectlow118.2.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.