Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-22 04:08 UTC

GEOLYTIX / xyz

An open source javascript framework for spatial data and application interfaces.

JavaScriptMIT★ 133 stars⑂ 45 forkssince Dec 2017View on GitHub ↗
KindLibraryNetwork servicehow this is determined

GEOLYTIX/xyz holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Vitality (96/100) and lowest on AI Readiness (49/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

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

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

Ownership

GEOLYTIXOrganization
31 followers15 public repossince Oct 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmxyzpoints to another repo — not scored5.0.011,698161055 days agoclipublishreleasetool
npm@geolytix/mapp5.1.0-rc.123128 days agogeolytixxyzmappopenlayersmapgis

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 350 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year350
human_commit_share0.97
days_since_last_push1
active_weeks_last_year43

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 8 days ago
27/27Release cadence — a release every ~9.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv5.0.9
releases_from_tagsno
days_since_latest_release8
mean_days_between_releases9.4
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?

66Good · 17% of overall
How it's scored
34.4/60Stars — 133 stars
13.7/25Forks — 45 forks
5.3/15Watchers — 10 watchers
Inputs used
forks45
stars133
watchers10
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

100Exceptional
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io, sonarcloud.io
has_pull_request_templateyes
How it's scored
31.5/80Monthly downloads — 231 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@geolytix/mapp
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads231
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?

73Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.8/22.5Commit distribution — top contributor authored 43% of commits
13.5/13.5Contributor breadth — 10 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor2
contributors_sampled10
top_contributor_share0.429
How it's scored
38.3/42Issue resolution — 91% of issues closed
27.3/30PR acceptance — 1,481/1,628 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 18/25 approved changesets -- score normalized to 7
Inputs used
merged_prs1,481
open_issues87
closed_issues906
prs_merged_7d24
prs_decided_7d24
prs_merged_30d53
prs_decided_30d56
issue_closed_ratio0.912
closed_unmerged_prs147
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
10.8/25Owner reach — 31 followers of GEOLYTIX
20.8/25Track record — 15 public repos, account ~10 yr old
Inputs used
followers31
owner_typeOrganization
is_verifiedno
owner_loginGEOLYTIX
public_repos15
account_age_days3,686
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 8 days ago
12/20Version history — 2 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@geolytix/mapp
ecosystemsnpm
any_deprecatedno
min_days_since_publish8

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicsspatial-data, openlayers, postgis, mvt, nodejs, javascript, xyz
has_wikiyes
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?

61Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 22 out of 22 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
5.2/7.5Code-Review — Found 18/25 approved changesets -- score normalized to 7
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
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
2.5/5SAST — SAST tool is not run on all commits -- score normalized to 5
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_aggregate6.8
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
4/35Direct dependencies free of known advisories — 5 affected: @node-saml/node-saml catalog: (critical 10.0), pg catalog: (critical 9.8), jsonwebtoken catalog: (high 8.1), +2 more
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
20/40No advisories left outstanding — 5 advisory-carrying package(s) unaddressed past 90 days; oldest published 3,042 days ago
Inputs used
sourceosv
advisories61
affected_packages9
assessed_packages28
unassessed_packages0
affected_by_severitycritical 3, high 3, moderate 3
direct_affected_packages5
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 28 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

49Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
34.6/40Legible commit history — 63 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.649
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — biome.json
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice — 8 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.08
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
54.7/55Manageable file sizes — 2/379 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes141,523
source_files_sampled379
oversized_source_files2

Key facts

133GitHub stars
10contributors
350commits, last 12 months
1days since last push
100releases
2bus factor
87open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package 'xyz' points at a different repository (https://github.com/davidchambers/xyz); excluded from ecosystem scoring
  • Could not fetch npm package '@geolytix/xyz-app' from its registry
  • Could not fetch npm package '@geolytix/xyz-auth-app' from its registry
  • Could not fetch npm package '@geolytix/xyz-saml-app' from its registry

More detail

Star and fork history 0 ★ / 45 ⇿
0Stars
45Forks
99Releases

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.

0102030405045102018-072022-092026-11
Major 1Minor 16Patch 82

Each point covers 8 days.

OpenSSF Scorecard 6.8 / 10
6.8aggregate

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-22 04:07 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests22 out of 22 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 18/25 approved changesets -- score normalized to 7
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
5SASTSAST tool is not run on all commits -- score normalized to 5
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 27
RegistryPackageVersion constraintManifest
npm@geolytix/mappworkspace:*package.json
npm@geolytix/xyz-auth-appworkspace:*package.json
npm@geolytix/xyz-appworkspace:*package.json
npm@geolytix/xyz-saml-appworkspace:*package.json
npm@varlock/google-secret-manager-plugincatalog:package.json
npmvarlockcatalog:package.json
npm@geolytix/xyz-appworkspace:*apps/auth/package.json
npmexpresscatalog:apps/auth/package.json
npm@node-saml/node-samlcatalog:apps/saml/package.json
npm@geolytix/xyz-appworkspace:*apps/saml/package.json
npmexpresscatalog:apps/saml/package.json
npmjsonwebtokencatalog:apps/saml/package.json
npm@opentelemetry/apicatalog:apps/xyz/package.json
npm@varlock/google-secret-manager-plugincatalog:apps/xyz/package.json
npmbcryptcatalog:apps/xyz/package.json
npmcookie-parsercatalog:apps/xyz/package.json
npmexpresscatalog:apps/xyz/package.json
npmexpress-rate-limitcatalog:apps/xyz/package.json
npmjsonwebtokencatalog:apps/xyz/package.json
npmpgcatalog:apps/xyz/package.json
npmvarlockcatalog:apps/xyz/package.json
npm@electric-sql/pglitecatalog:packages/devdb/package.json
npm@electric-sql/pglite-postgiscatalog:packages/devdb/package.json
npm@electric-sql/pglite-socketcatalog:packages/devdb/package.json
npm@geolytix/xyz-appworkspace:*packages/testview/package.json
npm@geolytix/xyz-devdbworkspace:*packages/testview/package.json
npmexpresscatalog:packages/testview/package.json
All dependencies 28

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

RegistryPackageVersionRelation
npm@electric-sql/pglitecatalog:direct
npm@electric-sql/pglite-postgiscatalog:direct
npm@electric-sql/pglite-socketcatalog:direct
npm@node-saml/node-samlcatalog:direct
npm@opentelemetry/apicatalog:direct
npm@varlock/google-secret-manager-plugincatalog:direct
npmbcryptcatalog:direct
npmcookie-parsercatalog:direct
npmexpresscatalog:direct
npmexpress-rate-limitcatalog:direct
npmjsonwebtokencatalog:direct
npmpgcatalog:direct
npmvarlockcatalog:direct
npm@aws-sdk/client-s3catalog:indirect
npm@aws-sdk/cloudfront-signercatalog:indirect
npm@aws-sdk/s3-request-presignercatalog:indirect
npm@biomejs/biomecatalog:indirect
npm@opentelemetry/exporter-trace-otlp-httpcatalog:indirect
npm@opentelemetry/resourcescatalog:indirect
npm@opentelemetry/sdk-trace-nodecatalog:indirect
npm@vitest/coverage-v8catalog:indirect
npmclean-jsdoc-themecatalog:indirect
npmnode-mocks-httpcatalog:indirect
npmresendcatalog:indirect
npmturbocatalog:indirect
npmundicicatalog:indirect
npmvitecatalog:indirect
npmvitestcatalog:indirect
Dependency advisories 9

This repository publishes no package the index resolves, so its own dependency graph was assessed — 28 packages, which also include development and test pins that never ship: 9 carry known advisories, of which 5 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
@node-saml/node-samlcatalog:directcritical45.1.0
pgcatalog:directcritical17.1.2
vitestcatalog:indirectcritical24.1.0
jsonwebtokencatalog:directhigh49.0.0
undicicatalog:indirecthigh238.10.2
vitecatalog:indirecthigh218.3.3
bcryptcatalog:directmoderate15.0.0
expresscatalog:directmoderate45.0.0-beta.3
turbocatalog:indirectmoderate12.9.14

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.