Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 03:51 UTC

MergeSignal / mergesignal

TypeScriptApache-2.0★ 0 stars⑂ 0 forkssince Feb 2026View on GitHub ↗
KindNetwork serviceWeb interfaceLibraryhow this is determined

MergeSignal/mergesignal holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (76/100) and lowest on Community & Adoption (31/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

MergeSignalOrganization
0 followers1 public reposince Feb 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@mergesignal/shared0.18.01,438360 days ago
npm@mergesignal/scan-prep0.1.633250 days ago

Metrics by category

Vitality

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

69Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
16.6/36Commit cadence24/52 weeks with commits
18/18Commit volume406 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year406
human_commit_share1
days_since_last_push0
active_weeks_last_year24
How it's scored
16.2/27Ships releases1 version tags (no GitHub releases)
16.2/36Release recencylatest release 192 days ago
12.6/27Release cadencecadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count1
latest_release_tagv0.1.0
releases_from_tagsyes
days_since_latest_release192
mean_days_between_releases
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?

31At Risk · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
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
43.3/80Monthly downloads1,770 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@mergesignal/shared, @mergesignal/scan-prep
dependents
ecosystemsnpm
total_downloads
monthly_downloads1,770
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?

37Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.4/22.5Commit distributiontop contributor authored 98% of commits
2.7/13.5Contributor breadth2 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.983
How it's scored
0/42Issue resolutionno issues or no data
10/30PR acceptance9/27 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/24 approved changesets -- score normalized to 0
Inputs used
merged_prs9
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d4
prs_decided_30d5
issue_closed_ratio
closed_unmerged_prs18
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
0/25Owner reach0 followers of MergeSignal
3.3/25Track record1 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginMergeSignal
public_repos1
account_age_days196

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on npm
35/35Publish recencylatest publish 0 days ago
20/20Version history36 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@mergesignal/shared, @mergesignal/scan-prep
ecosystemsnpm
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests4 out of 4 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
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionno

Security

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

36Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests4 out of 4 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/24 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities105 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

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.

59Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history84 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.84
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.js
11/11Static type checkingapps/api/tsconfig.json, apps/cli/tsconfig.json, apps/web/tsconfig.json, apps/worker/tsconfig.json, packages/engine-stub/tsconfig.json, packages/engine-test-fixture/tsconfig.json, packages/engine/tsconfig.json, packages/scan-prep/tsconfig.json, packages/shared/tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice88 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsapps/api/tsconfig.json, apps/cli/tsconfig.json, apps/web/tsconfig.json, apps/worker/tsconfig.json, packages/engine-stub/tsconfig.json, packages/engine-test-fixture/tsconfig.json, packages/engine/tsconfig.json, packages/scan-prep/tsconfig.json, packages/shared/tsconfig.json
agent_commit_share0.88
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/415 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes27,334
source_files_sampled415
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

0GitHub stars
2contributors
406commits, last 12 months
0days since last push
1releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index npm:@mergesignal/shared@0.18.0; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 3.6 / 10
3.6aggregate

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-10 03:51 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests4 out of 4 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/24 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow 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
0Vulnerabilities105 existing vulnerabilities detected
Direct dependencies 48
RegistryPackageVersion constraintManifest
npm@fastify/cors^11.2.0apps/api/package.json
npm@fastify/rate-limit^10.3.0apps/api/package.json
npm@mergesignal/engineworkspace:^apps/api/package.json
npm@mergesignal/sharedworkspace:^apps/api/package.json
npm@octokit/app^16.1.2apps/api/package.json
npm@sentry/node8apps/api/package.json
npmbullmq^5.70.1apps/api/package.json
npmdotenv^17.4.2apps/api/package.json
npmfastify^5.7.4apps/api/package.json
npmfastify-raw-body^5.0.0apps/api/package.json
npmioredis^5.9.3apps/api/package.json
npmpg^8.19.0apps/api/package.json
npmzod^4.4.3apps/api/package.json
npm@mergesignal/engineworkspace:^apps/cli/package.json
npm@mergesignal/sharedworkspace:^apps/cli/package.json
npm@mantine/core^9.1.1apps/web/package.json
npm@mantine/hooks^9.1.1apps/web/package.json
npm@mergesignal/sharedworkspace:*apps/web/package.json
npm@sentry/node8apps/web/package.json
npmautoprefixer^10.5.0apps/web/package.json
npmlucide-react^1.11.0apps/web/package.json
npmnext16.1.5apps/web/package.json
npmnext-auth5.0.0-beta.30apps/web/package.json
npmpostcss^8.5.14apps/web/package.json
npmpostcss-preset-mantine^1.18.0apps/web/package.json
npmpostcss-simple-vars^7.0.1apps/web/package.json
npmreact^19.2.0apps/web/package.json
npmreact-dom^19.2.0apps/web/package.json
npmreact-markdown9apps/web/package.json
npmremark-gfm4apps/web/package.json
npmserver-only^0.0.1apps/web/package.json
npm@mergesignal/engineworkspace:^apps/worker/package.json
npm@mergesignal/scan-prepworkspace:^apps/worker/package.json
npm@mergesignal/sharedworkspace:^apps/worker/package.json
npm@octokit/auth-app^8.2.0apps/worker/package.json
npm@sentry/node^8.55.1apps/worker/package.json
npmbullmq^5.70.1apps/worker/package.json
npmdotenv^17.4.2apps/worker/package.json
npmoctokit^3.1.2apps/worker/package.json
npmpg^8.19.0apps/worker/package.json
npm@mergesignal/sharedworkspace:^packages/engine-stub/package.json
npm@mergesignal/sharedworkspace:^packages/engine-test-fixture/package.json
npm@mergesignal/engine-stubworkspace:^packages/engine/package.json
npm@mergesignal/sharedworkspace:^packages/engine/package.json
npm@mergesignal/shared0.18.0packages/scan-prep/package.json
npm@octokit/auth-app^7.1.4packages/scan-prep/package.json
npmoctokit^4.1.2packages/scan-prep/package.json
npmzod^4.4.3packages/shared/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

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