Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 16:12 UTC

unified-product-graph / tools

Unified Product Graph (public beta): SDK, CLI, MCP servers (local + cloud), adapters, markdown.

TypeScriptMIT★ 2 stars⑂ 0 forkssince May 2026View on GitHub ↗
KindLibraryCommand-line toolMCP serverNetwork servicehow this is determined

unified-product-graph/tools holds a health index of 50 out of 100, placing it in the Moderate band. It scores highest on Vitality (79/100) and lowest on Sustainability & Governance (33/100). It was last updated 7 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Unified Product GraphOrganization
2 followers3 public repossince Mar 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@unified-product-graph/cli0.41.03,4511277 days agomcpmcp-servermodel-context-protocol
npm@unified-product-graph/sdk0.41.03,7341277 days agoupgunified-product-graphsdkproduct-managementknowledge-graphgraphopen-standard
npm@unified-product-graph/adapters0.41.03,2141277 days ago—
npm@unified-product-graph/markdown0.41.03,0961277 days agoupgmarkdownproduct-graphentity-referencesgraph-aware-documentsopen-standard
npm@unified-product-graph/mcp-server0.41.03,2961307 days agomcpupgunified-product-graphproduct-managementmodel-context-protocolknowledge-graph
npm@unified-product-graph/cloud-server0.41.03,3371287 days agomcpupgunified-product-graphproduct-managementmodel-context-protocolknowledge-graphpostgresself-hosted

Metrics by category

Vitality

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

79Good · 21% of overall

Development activity

73Good
How it's scored
36/36Push recency — last push 7 days ago
9/36Commit cadence — 13/52 weeks with commits
18/18Commit volume — 176 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year176
human_commit_share1
days_since_last_push7
active_weeks_last_year13

Release discipline

88Excellent
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
36/36Release recency — latest release 7 days ago
27/27Release cadence — a release every ~1.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv0.41.0
releases_from_tagsyes
days_since_latest_release7
mean_days_between_releases1.5
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?

36Weak · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 2 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars2
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold

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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

72Good
How it's scored
57.4/80Monthly downloads — 20,128 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@unified-product-graph/cli, @unified-product-graph/sdk, @unified-product-graph/adapters, @unified-product-graph/markdown, @unified-product-graph/mcp-server, @unified-product-graph/cloud-server
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads20,128
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?

33At Risk · 23% of overall

Maintainer resilience (bus factor)

10Critical
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1

Issue & PR responsiveness

1Critical
How it's scored
0/42Issue resolution — no issues or no data
0/30PR acceptance — no decided pull requests or no data
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_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

39Weak
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
3.4/25Owner reach — 2 followers of unified-product-graph
5.3/25Track record — 3 public repos, account ~0 yr old
Inputs used
followers2
owner_typeOrganization
is_verifiedno
owner_loginunified-product-graph
public_repos3
account_age_days170

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 6 package(s) on npm
35/35Publish recency — latest publish 7 days ago
20/20Version history — 130 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@unified-product-graph/cli, @unified-product-graph/sdk, @unified-product-graph/adapters, @unified-product-graph/markdown, @unified-product-graph/mcp-server, @unified-product-graph/cloud-server
ecosystemsnpm
any_deprecatedno
min_days_since_publish7

Engineering Quality

Are baseline engineering and documentation practices in place?

52Moderate · 19% of overall

Engineering practices

50Moderate
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://unifiedproductgraph.org/
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://unifiedproductgraph.org/
docs_sitehttps://unifiedproductgraph.org/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

47Weak · 16% of overall

Security posture

34At Risk
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
0/2.5CI-Tests — no data
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/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
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
7.5/7.5Maintained — 30 commit(s) and 0 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 — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, 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_packages93
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:@unified-product-graph/cli@0.41.0 runtime dependency closure — what installing the published package pulls in — 93 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.

62Moderate · 4% of overall

Agent context & guidance

55Moderate
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://unifiedproductgraph.org/llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://unifiedproductgraph.org/llms.txt
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

54Moderate
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — packages/adapters/tsconfig.json, packages/cli/tsconfig.json, packages/cloud-server/tsconfig.json, packages/markdown/tsconfig.json, packages/mcp-server/tsconfig.json, packages/mcp-tooling/tsconfig.json, packages/sdk/examples/helm/tsconfig.json, packages/sdk/tsconfig.json
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
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
lockfiles—
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configspackages/adapters/tsconfig.json, packages/cli/tsconfig.json, packages/cloud-server/tsconfig.json, packages/markdown/tsconfig.json, packages/mcp-server/tsconfig.json, packages/mcp-tooling/tsconfig.json, packages/sdk/examples/helm/tsconfig.json, packages/sdk/tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0

Code legibility for models

99Exceptional
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54/55Manageable file sizes — 9/507 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes148,308
source_files_sampled507
oversized_source_files9

Machine-readable interfaces

60Moderate
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

2GitHub stars
1contributors
176commits, last 12 months
7days since last push
100releases
1bus factor
0open issues
—package ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-06-05: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 2 stars today.

More detail

OpenSSF Scorecard 3.4 / 10
3.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-09-12 16:12 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
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
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 28
RegistryPackageVersion constraintManifest
npm@linear/sdk^5.0.0packages/adapters/package.json
npm@notionhq/client^2.3.0packages/adapters/package.json
npm@unified-product-graph/core0.41.0packages/adapters/package.json
npm@linear/sdk^5.0.0packages/cli/package.json
npm@octokit/rest^20.0.0packages/cli/package.json
npm@unified-product-graph/core0.41.0packages/cli/package.json
npm@unified-product-graph/sdk0.41.0packages/cli/package.json
npmchalk^4.1.2packages/cli/package.json
npmcommander^13.0.0packages/cli/package.json
npminquirer^12.0.0packages/cli/package.json
npmora^8.0.0packages/cli/package.json
npm@modelcontextprotocol/sdk^1.27.0packages/cloud-server/package.json
npm@unified-product-graph/core0.41.0packages/cloud-server/package.json
npm@unified-product-graph/sdk0.41.0packages/cloud-server/package.json
npmnanoid^5.1.0packages/cloud-server/package.json
npmpg^8.13.0packages/cloud-server/package.json
npm@modelcontextprotocol/sdk^1.27.0packages/mcp-server/package.json
npm@unified-product-graph/core0.41.0packages/mcp-server/package.json
npm@unified-product-graph/sdk0.41.0packages/mcp-server/package.json
npmchokidar^4.0.0packages/mcp-server/package.json
npmnanoid^5.1.0packages/mcp-server/package.json
npm@unified-product-graph/core*packages/mcp-tooling/package.json
npmtypescript^5.6.0packages/mcp-tooling/package.json
npm@unified-product-graph/core0.41.0packages/sdk/package.json
npm@unified-product-graph/templates0.41.0packages/sdk/package.json
npmchokidar^4.0.0packages/sdk/package.json
npmnanoid^5.1.0packages/sdk/package.json
npmproper-lockfile^4.1.2packages/sdk/package.json
All dependencies 35

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

RegistryPackageVersionRelation
npm@linear/sdk^5.0.0direct
npm@modelcontextprotocol/sdk^1.27.0direct
npm@notionhq/client^2.3.0direct
npm@octokit/rest^20.0.0direct
npm@unified-product-graph/core*direct
npm@unified-product-graph/core0.41.0direct
npm@unified-product-graph/sdk*direct
npm@unified-product-graph/sdk0.41.0direct
npm@unified-product-graph/templates0.41.0direct
npmchalk^4.1.2direct
npmchalk^5.3.0direct
npmchokidar^4.0.0direct
npmcommander^13.0.0direct
npminquirer^12.0.0direct
npmnanoid^5.1.0direct
npmora^8.0.0direct
npmpg^8.13.0direct
npmproper-lockfile^4.1.2direct
npmtypescript^5.6.0direct
npmtypescript^5.8.0direct
npmtypescript^5.8.3direct
npm@types/node^22.0.0indirect
npm@types/node^25.6.0indirect
npm@types/pg^8.11.0indirect
npm@types/proper-lockfile^4.1.4indirect
npm@unified-product-graph/adapters*indirect
npm@unified-product-graph/mcp-server*indirect
npm@unified-product-graph/mcp-tooling*indirect
npmeslint^9.0.0indirect
npmtsup^8.0.0indirect
npmtsup^8.5.1indirect
npmtsx^4.0.0indirect
npmtsx^4.19.0indirect
npmtypescript-eslint^8.0.0indirect
npmvitest^4.1.0indirect
Dependency advisories 0

Installing npm:@unified-product-graph/cli@0.41.0 pulls in 93 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 unified-product-graph/tools. Read them side by side →

98n8n-io/n8nFair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.Exceptional97Observal/ObservalObserval is self-hosted registry for your coding agent extensions with a built in insight engine. Setup Observal, define the scope and share your Skills, MCPs and Agents with your peers.Exceptional96electric-sql/electricThe agent platform built on sync.Exceptional96mcp-use/mcp-useThe fullstack MCP framework to develop MCP Apps for ChatGPT / Claude & MCP Servers for AI Agents.Exceptional96PrefectHQ/fastmcp🚀 The fast, Pythonic way to build MCP servers and clients.Exceptional99IBM/mcp-context-forgeAn AI Gateway, registry, and proxy that sits in front of any MCP, A2A, or REST/gRPC APIs, exposing a unified endpoint with centralized discovery, guardrails and management. Optimizes Agent & Tool calling, and supports plugins.Exceptional

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.