Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 07:36 UTC

osmlab / name-suggestion-index

Canonical common brand names, operators, transit, and flags for OpenStreetMap.

JSONBSD-3-Clause★ 888 stars⑂ 1,064 forkssince Oct 2013View on GitHub ↗

osmlab/name-suggestion-index holds a health index of 96 out of 100, placing it in the Exceptional band. It scores highest on Vitality (95/100) and lowest on Security (63/100). It was last updated today. 6 contributors account for most of its recent work.

96
overall / 100
Exceptional

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.

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

Ownership

OSM LabOrganization
237 followers128 public repossince Mar 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmname-suggestion-index8.0.2026091816,33226132 days agobrandscanonicalizationflagsfranchisesjavascriptnamesopenstreetmapoperatorsosmroutestransitwikidata

Metrics by category

Vitality

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

95Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recency — last push 0 days ago
36/36Commit cadence — 52/52 weeks with commits
18/18Commit volume — 2,263 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year2,263
human_commit_share0.99
days_since_last_push0
active_weeks_last_year52
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
36/36Release recency — latest release 32 days ago
27/27Release cadence — a release every ~16 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv8.0.20260918
releases_from_tagsyes
days_since_latest_release32
mean_days_between_releases16
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?

74Good · 17% of overall
How it's scored
47.8/60Stars — 888 stars
25/25Forks — 1,064 forks
8.5/15Watchers — 35 watchers
Inputs used
forks1,064
stars888
watchers35
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-3-Clause)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, github.com
has_pull_request_templateno
How it's scored
56.2/80Monthly downloads — 16,332 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesname-suggestion-index
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads16,332
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?

86Excellent · 23% of overall
How it's scored
48.6/54Bus factor — 6 contributor(s) cover half of all commits
19/22.5Commit distribution — top contributor authored 15% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 30 contributing companies or organizations
Inputs used
bus_factor6
contributors_sampled99
top_contributor_share0.154
How it's scored
39.4/42Issue resolution — 94% of issues closed
26.7/30PR acceptance — 7,070/7,943 decided PRs merged
13/13Newcomer PR acceptance — 4/4 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 10/30 approved changesets -- score normalized to 3
Inputs used
merged_prs7,070
open_issues302
closed_issues4,633
prs_merged_7d37
prs_decided_7d37
prs_merged_30d50
prs_decided_30d52
issue_closed_ratio0.939
closed_unmerged_prs873
first_time_authors_30d4
first_time_prs_merged_30d4
first_time_prs_decided_30d4
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
17.1/25Owner reach — 237 followers of osmlab
25/25Track record — 128 public repos, account ~13 yr old
Inputs used
followers237
owner_typeOrganization
is_verifiedno
owner_loginosmlab
public_repos128
account_age_days4,969

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 32 days ago
20/20Version history — 261 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesname-suggestion-index
ecosystemsnpm
any_deprecatedno
min_days_since_publish32

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://nsi.guide
10/10Repository description
10/10Topics — 12 topics
10/10Wiki
Inputs used
topicsopenstreetmap, osm, names, brands, javascript, operators, transit, flags, mapping, wikidata, hacktoberfest, typescript
has_wikiyes
homepagehttps://nsi.guide
docs_sitehttps://nsi.guide
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

63Moderate · 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
2.5/2.5CI-Tests — 10 out of 10 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
2.2/7.5Code-Review — Found 10/30 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 30 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 3 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
0/5Security-Policy — security policy file not 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.4
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

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_packages21
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:name-suggestion-index@8.0.20260918 runtime dependency closure — what installing the published package pulls in — 21 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.

69Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
35/40Legible commit history — 65 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.657
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes3,556
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — tsconfig.json
0/10Reproducible environment
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.03
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — JSON with type-check config (tsconfig.json)
55/55Manageable file sizes — 0/42 source files over 60KB
Inputs used
primary_languageJSON
largest_source_bytes40,943
source_files_sampled42
oversized_source_files0

Key facts

888GitHub stars
99contributors
2,263commits, last 12 months
0days since last push
100releases
6bus factor
302open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • First-time contributor figures cover 12 of 19 authors (cap 12)

More detail

Star and fork history 0 ★ / 1,064 ⇿
0Stars
1,064Forks
100Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

02004006008001,0001,2001,064332018-102022-102026-10
Major 0Minor 0Patch 100

Each point covers 8 days.

OpenSSF Scorecard 5.4 / 10
5.4aggregate

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-21 07:36 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 10/30 approved changesets -- score normalized to 3
10Contributorsproject has 30 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 3 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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
npm@rapideditor/location-conflation^3.0.1package.json
npm@types/diacritics^1.3.3package.json
npm@types/geojson^7946.0.16package.json
npmdiacritics^1.3.0package.json
npmfast-xml-builder^1.3.1package.json
All dependencies 33

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

RegistryPackageVersionRelation
npm@rapideditor/location-conflation^3.0.1direct
npm@types/diacritics^1.3.3direct
npm@types/geojson^7946.0.16direct
npmdiacritics^1.3.0direct
npmfast-xml-builder^1.3.1direct
npm@eslint/js^10.0.1indirect
npm@fortawesome/free-brands-svg-icons^7.3.1indirect
npm@fortawesome/free-solid-svg-icons^7.3.1indirect
npm@fortawesome/react-fontawesome^3.5.0indirect
npm@ideditor/nsi-collector1.0.20250817indirect
npm@mapbox/geojson-area^0.2.2indirect
npm@mapbox/geojson-rewind^0.5.2indirect
npm@openstreetmap/id-tagging-schema^7.3.0indirect
npm@types/bun^1.4.3indirect
npm@types/geojson-precision^1.0.0indirect
npm@types/mapbox__geojson-rewind^0.5.0indirect
npm@types/safe-regex^1.1.6indirect
npmeslint^10.12.0indirect
npmeslint-plugin-import^2.32.0indirect
npmgeojson-bounds^1.0.4indirect
npmgeojson-precision^1.0.0indirect
npmglobals^17.13.0indirect
npmjson-stringify-pretty-compact^4.0.0indirect
npmjson5^2.2.3indirect
npmjsonschema^1.5.0indirect
npmreact^19.3.0indirect
npmreact-dom^19.3.0indirect
npmreact-router-dom^7.18.4indirect
npmsafe-regex^2.1.1indirect
npmtypescript^6.0.3indirect
npmtypescript-eslint^8.71.2indirect
npmwikibase-edit^8.2.3indirect
npmwikibase-sdk^11.6.6indirect
Dependency advisories 0

Installing npm:name-suggestion-index@8.0.20260918 pulls in 21 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.

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.