Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-30 13:46 UTC

starkinfra / core-node

Core functionalities for the StarkInfra and StarkBank JS SDKs

JavaScriptMIT★ 0 stars⑂ 1 forksince Mar 2022View on GitHub ↗
KindLibraryhow this is determined

starkinfra/core-node holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (82/100) and lowest on AI Readiness (34/100). It was last updated 8 days ago. 3 contributors account for most of its recent work.

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

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

Ownership

STARK INFRAOrganization
16 followers18 public repossince Nov 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmstarkcore0.4.0124,358148 days agostarkinfrastarkbankinfraopenbankingopenbanking

Metrics by category

Vitality

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

68Good · 21% of overall

Development activity

52Moderate
How it's scored
28.8/36Push recency — last push 8 days ago
4.8/36Commit cadence — 7/52 weeks with commits
12.1/18Commit volume — 21 commits in the last year
6/10OpenSSF Scorecard: Maintained — 8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year21
human_commit_share1
days_since_last_push8
active_weeks_last_year7

Release discipline

92Excellent
How it's scored
27/27Ships releases — 14 releases published
36/36Release recency — latest release 8 days ago
19.8/27Release cadence — a release every ~83.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count14
latest_release_tagv0.4.0
releases_from_tagsno
days_since_latest_release8
mean_days_between_releases83.3
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?

39Weak · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 0 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars0
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
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_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

85Excellent
How it's scored
67.9/80Monthly downloads — 124,358 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesstarkcore
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads124,358
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?

82Excellent · 23% of overall

Maintainer resilience (bus factor)

69Good
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
18.2/22.5Commit distribution — top contributor authored 19% of commits
12.2/13.5Contributor breadth — 9 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor3
contributors_sampled9
top_contributor_share0.192

Issue & PR responsiveness

92Excellent
How it's scored
42/42Issue resolution — 100% of issues closed
26.2/30PR acceptance — 21/24 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-Review — Found 13/15 approved changesets -- score normalized to 8
Inputs used
merged_prs21
open_issues0
closed_issues1
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio1
closed_unmerged_prs3
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

72Good
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
8.8/25Owner reach — 16 followers of starkinfra
18.7/25Track record — 18 public repos, account ~4 yr old
Inputs used
followers16
owner_typeOrganization
is_verified—
owner_loginstarkinfra
public_repos18
account_age_days1,708
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

34At Risk · 19% of overall

Engineering practices

24At Risk
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 13 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
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?

50Moderate · 16% of overall

Security posture

37Weak
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
4.5/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — 0 out of 13 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6/7.5Code-Review — Found 13/15 approved changesets -- score normalized to 8
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
4.5/7.5Maintained — 8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
0/7.5Vulnerabilities — 49 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.7
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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_packages35
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:starkcore@0.4.0 runtime dependency closure — what installing the published package pulls in — 35 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.

34At Risk · 4% of overall

Agent context & guidance

21At Risk
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
21.1/40Legible commit history — 21 of 53 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.396
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

36Weak
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 53
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

55Moderate
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/19 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes10,411
source_files_sampled19
oversized_source_files0

Key facts

0GitHub stars
9contributors
21commits, last 12 months
8days since last push
14releases
3bus factor
0open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 3.7 / 10
3.7aggregate

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-07-30 13:46 UTC

10Binary-Artifactsno binaries found in the repo
6Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 13 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 13/15 approved changesets -- score normalized to 8
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
6Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities49 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npmaxios^1.4.0package.json
npmenum^3.0.4package.json
npmstarkbank-ecdsa1.2.0package.json
npmutf8^3.0.0package.json
All dependencies 92

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

RegistryPackageVersionRelation
npmaxios1.6.4direct
npmenum3.0.4direct
npmstarkbank-ecdsa1.2.0direct
npmutf83.0.0direct
npmansi-colors4.1.1indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmanymatch3.1.3indirect
npmargparse2.0.1indirect
npmasynckit0.4.0indirect
npmbalanced-match1.0.2indirect
npmbig-integer1.6.51indirect
npmbinary-extensions2.2.0indirect
npmbrace-expansion1.1.11indirect
npmbrace-expansion2.0.1indirect
npmbraces3.0.3indirect
npmbrowser-stdout1.3.1indirect
npmcamelcase6.3.0indirect
npmchalk4.1.2indirect
npmchokidar3.5.3indirect
npmcliui7.0.4indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcombined-stream1.0.8indirect
npmconcat-map0.0.1indirect
npmdebug4.3.4indirect
npmdecamelize4.0.0indirect
npmdelayed-stream1.0.0indirect
npmdiff5.0.0indirect
npmemoji-regex8.0.0indirect
npmescalade3.1.1indirect
npmescape-string-regexp4.0.0indirect
npmfill-range7.1.1indirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmfollow-redirects1.15.6indirect
npmform-data4.0.0indirect
npmfs.realpath1.0.0indirect
npmfsevents2.3.3indirect
npmget-caller-file2.0.5indirect
npmglob7.2.0indirect
npmglob-parent5.1.2indirect
npmhas-flag4.0.0indirect
npmhe1.2.0indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-binary-path2.1.0indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-plain-obj2.1.0indirect
npmis-unicode-supported0.1.0indirect
npmjs-sha2560.9.0indirect
npmjs-yaml4.1.0indirect
npmlocate-path6.0.0indirect
npmlog-symbols4.1.0indirect
npmmime-db1.52.0indirect
npmmime-types2.1.35indirect
npmminimatch3.1.2indirect
npmminimatch5.0.1indirect
npmmocha10.2.0indirect
npmms2.1.2indirect
npmms2.1.3indirect
npmnanoid3.3.3indirect
npmnormalize-path3.0.0indirect
npmonce1.4.0indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpath-exists4.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpicomatch2.3.1indirect
npmproxy-from-env1.1.0indirect
npmrandombytes2.1.0indirect
npmreaddirp3.6.0indirect
npmrequire-directory2.1.1indirect
npmsafe-buffer5.2.1indirect
npmserialize-javascript6.0.0indirect
npmstring-width4.2.3indirect
npmstrip-ansi6.0.1indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmto-regex-range5.0.1indirect
npmworkerpool6.2.1indirect
npmwrap-ansi7.0.0indirect
npmwrappy1.0.2indirect
npmy18n5.0.8indirect
npmyargs16.2.0indirect
npmyargs-parser20.2.4indirect
npmyargs-unparser2.0.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:starkcore@0.4.0 pulls in 35 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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with starkinfra/core-node. Read them side by side →

56starkinfra/sdk-nodeSDK to facilitate Node integrations with the Stark Infra APIModerate83pluggyai/pluggy-nodeOfficial Node SDK for Pluggy APIExcellent78starkbank/sdk-nodeSDK to facilitate Node JS integrations with the Stark Bank APIGood75open-banking-io/clientsZero-knowledge open banking — server-to-server SDKs (.NET, Node, Python, Rust, Go, Java, Ruby, PHP) and the openbanking CLI for open-banking.ioGood28brocc-ab/se-bank-account-jsSwedish bank account details and validation for JavaScriptAt Risk57brokeyourbike/clearbank-api-client-goClearBank API Client for GoModerate

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.27.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.