Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 08:55 UTC

Stellar-Light / stellarlight

A discovery layer for everything in the Stellar Ecosystem

TypeScriptMIT★ 4 stars⑂ 2 forkssince Nov 2025View on GitHub ↗
KindLibraryWeb interfaceNetwork serviceMCP serverCommand-line toolhow this is determined

Stellar-Light/stellarlight holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (86/100) and lowest on Community & Adoption (33/100). It was last updated today. A single contributor accounts for most of its recent work.

57
overall / 100
Moderate

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.

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

Ownership

Stellar LightOrganization
2 followers5 public repossince Dec 2023

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

Package ecosystems

Metrics by category

Vitality

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

50Moderate · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
19.4/36Commit cadence — 28/52 weeks with commits
18/18Commit volume — 1,892 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,892
human_commit_share0.82
days_since_last_push0
active_weeks_last_year28
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

33At Risk · 17% of overall
How it's scored
7.7/60Stars — 4 stars
0/25Forks — 2 forks
0/15Watchers — 0 watchers
Inputs used
forks2
stars4
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
38.7/80Monthly downloads — 792 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@stellar-light/scout-mcp, @stellar-light/api-client
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads792
unverified_packages_excludedstellarlight
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?

55Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1/22.5Commit distribution — top contributor authored 96% of commits
4.1/13.5Contributor breadth — 3 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.957
How it's scored
36.6/42Issue resolution — 87% of issues closed
29.5/30PR acceptance — 1,382/1,404 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs1,382
open_issues16
closed_issues108
prs_merged_7d58
prs_decided_7d58
prs_merged_30d59
prs_decided_30d59
issue_closed_ratio0.871
closed_unmerged_prs22
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
3.4/25Owner reach — 2 followers of Stellar-Light
11.2/25Track record — 5 public repos, account ~2 yr old
Inputs used
followers2
owner_typeOrganization
is_verifiedno
owner_loginStellar-Light
public_repos5
account_age_days1,012

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 3 package(s) on npm
35/35Publish recency — latest publish 10 days ago
20/20Version history — 18 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesstellarlight, @stellar-light/scout-mcp, @stellar-light/api-client
ecosystemsnpm
any_deprecatedno
min_days_since_publish10

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 106 workflow(s)
24/24Tests present
16/16Linter config — biome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 11 out of 11 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://stellarlight.xyz
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicsblockchain, community, stellar
has_wikino
homepagehttps://stellarlight.xyz
docs_sitehttps://stellarlight.xyz
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

46Weak · 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 — 11 out of 11 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/30 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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 — 30 commit(s) and 12 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
0/7.5Vulnerabilities — 211 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.3
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_packages95
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:@stellar-light/scout-mcp@1.2.1 runtime dependency closure — what installing the published package pulls in — 95 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.

67Good · 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 — 73 of 82 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.89
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — biome.json
11/11Static type checking — api-client/tsconfig.json, scout-mcp/tsconfig.json, tsconfig.json
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 26 of the last 100 commits agent-authored or agent-credited
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
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsapi-client/tsconfig.json, scout-mcp/tsconfig.json, tsconfig.json
agent_commit_share0.26
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.3/55Manageable file sizes — 11/833 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes407,936
source_files_sampled833
oversized_source_files11
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — specs/openapi.json
20/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_filesspecs/openapi.json
interfaces_expected_ofnetwork-service

Key facts

4GitHub stars
3contributors
1,892commits, last 12 months
0days since last push
0releases
1bus factor
16open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks

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.

111222212026-072026-082026-08
OpenSSF Scorecard 3.3 / 10
3.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-09-11 08:55 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests11 out of 11 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/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 12 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
0Vulnerabilities211 existing vulnerabilities detected
Direct dependencies 60
RegistryPackageVersion constraintManifest
npm@anthropic-ai/sdk^0.109.1package.json
npm@aws-sdk/client-s3^3.926.0package.json
npm@aws-sdk/lib-storage^3.926.0package.json
npm@aws-sdk/s3-request-presigner^3.926.0package.json
npm@blend-capital/blend-sdk^3.3.0package.json
npm@creit.tech/stellar-wallets-kit^2.5.0package.json
npm@next/font^14.2.15package.json
npm@number-flow/react^0.6.0package.json
npm@payloadcms/db-mongodb3.63.0package.json
npm@payloadcms/email-resend3.63.0package.json
npm@payloadcms/next3.63.0package.json
npm@payloadcms/payload-cloud3.63.0package.json
npm@payloadcms/plugin-cloud-storage^3.63.0package.json
npm@payloadcms/richtext-lexical3.63.0package.json
npm@payloadcms/storage-r2^3.63.0package.json
npm@payloadcms/storage-s3^3.63.0package.json
npm@payloadcms/storage-vercel-blob^3.63.0package.json
npm@payloadcms/ui3.63.0package.json
npm@radix-ui/react-dialog^1.1.15package.json
npm@radix-ui/react-dropdown-menu^2.1.16package.json
npm@radix-ui/react-slot^1.2.3package.json
npm@stellar/stellar-sdk^16.0.1package.json
npm@tanstack/react-query^5.90.10package.json
npm@vercel/analytics^2.0.1package.json
npm@vercel/blob^2.0.0package.json
npm@visx/curve4.0.1-alpha.0package.json
npm@visx/event4.0.1-alpha.0package.json
npm@visx/gradient4.0.1-alpha.0package.json
npm@visx/grid4.0.1-alpha.0package.json
npm@visx/pattern4.0.1-alpha.0package.json
npm@visx/responsive4.0.1-alpha.0package.json
npm@visx/scale4.0.1-alpha.0package.json
npm@visx/shape4.0.1-alpha.0package.json
npmairtable^0.12.2package.json
npmcross-env^7.0.3package.json
npmd3-array^3.2.4package.json
npmd3-shape^3.2.0package.json
npmdate-fns^4.1.0package.json
npmdotenv16.4.7package.json
npmembla-carousel-react^8.6.0package.json
npmgraphql^16.8.1package.json
npmjs-yaml^4.1.1package.json
npmmotion^12.38.0package.json
npmnext16.0.10package.json
npmpayload3.63.0package.json
npmpdf-parse^2.4.5package.json
npmreact19.1.0package.json
npmreact-dom19.1.0package.json
npmreact-icons^5.4.0package.json
npmreact-markdown^10.1.0package.json
npmreact-use-measure^2.1.7package.json
npmremark-gfm^4.0.1package.json
npmrss-parser^3.13.0package.json
npmsharp0.34.2package.json
npmsimple-git^3.29.0package.json
npmvaul^1.1.2package.json
npmweb-haptics0.0.6package.json
npmzod^4.1.12package.json
npm@modelcontextprotocol/sdk^1.0.4scout-mcp/package.json
npmzod^3.23.8scout-mcp/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 0

Installing npm:@stellar-light/scout-mcp@1.2.1 pulls in 95 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.