Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-21 15:16 UTC

YounndAI / lyt

LYT™ — Link Your Think: federated markdown vaults — the storage architecture for AI-native knowledge work, AI-first by design. Mint vaults you own, weave meshes you share, forge Your Pod. Markdown-in-Git, YON-structured, never phones home. 7 npm packages under @younndai. Apache-2.0 · free forever · alpha. By YounndAI — younndai.com.

TypeScriptApache-2.0★ 2 stars⑂ 1 forksince Jun 2026View on GitHub ↗
KindCommand-line toolMCP serverLibraryhow this is determined

YounndAI/lyt holds a health index of 41 out of 100, placing it in the Weak band. It scores highest on Vitality (68/100) and lowest on Engineering Quality (27/100). It was last updated 12 days ago. A single contributor accounts for most of its recent work.

41
overall / 100
Weak

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.

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

Ownership

YounndAIOrganization
0 followers6 public repossince Jan 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@younndai/lyt0.20.261,99359106 days agolytvaultmeshobsidianmarkdowncliyounndai
npm@younndai/lyt-llm0.20.263,11560106 days agolytllmaiollamabyokyounndai
npm@younndai/lyt-mcp0.20.262,20459106 days agolytmcpmodel-context-protocolyounndai
npm@younndai/lyt-mesh0.20.262,27060106 days agolytmeshfederationgitcliyounndai
npm@younndai/lyt-vault0.20.262,88060106 days agolytvaultobsidianmarkdowncliyounndai
npm@younndai/lyt-runner0.20.261,98760106 days agolytrunneryonautomatoryounndai
npm@younndai/lyt-skills0.20.262,21960106 days agolytclaude-codeskillharnessyounndai

Metrics by category

Vitality

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

68Good · 21% of overall
How it's scored
28.8/36Push recency — last push 12 days ago
9/36Commit cadence — 13/52 weeks with commits
16.1/18Commit volume — 61 commits in the last year
10/10OpenSSF Scorecard: Maintained — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year61
human_commit_share1
days_since_last_push12
active_weeks_last_year13
How it's scored
27/27Ships releases — 1 releases published
27/36Release recency — latest release 109 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv0.20.22
releases_from_tagsno
days_since_latest_release109
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?

48Weak · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars2
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
56.3/80Monthly downloads — 16,668 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@younndai/lyt, @younndai/lyt-llm, @younndai/lyt-mcp, @younndai/lyt-mesh, @younndai/lyt-vault, @younndai/lyt-runner, @younndai/lyt-skills
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads16,668
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
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
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.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
0/25Owner reach — 0 followers of YounndAI
7.8/25Track record — 6 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginYounndAI
public_repos6
account_age_days294

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 7 package(s) on npm
35/35Publish recency — latest publish 106 days ago
20/20Version history — 60 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@younndai/lyt, @younndai/lyt-llm, @younndai/lyt-mcp, @younndai/lyt-mesh, @younndai/lyt-vault, @younndai/lyt-runner, @younndai/lyt-skills
ecosystemsnpm
any_deprecatedno
min_days_since_publish106

Engineering Quality

Are baseline engineering and documentation practices in place?

27At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://linkyourthink.com
10/10Repository description
10/10Topics — 19 topics
0/10Wiki
Inputs used
topicsai-agents, ai-first, cli, git, knowledge-management, knowledge-mesh, local-first, lyt, markdown, mcp, obsidian, vault, yon, younndai, agentic-ai, agents, ai, developer-tools, typescript
has_wikino
homepagehttps://linkyourthink.com
docs_sitehttps://linkyourthink.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

43Weak · 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
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 — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 97 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.3
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
10/25Indirect dependencies free of known advisories — 1 affected: zod 3.25.76 (high 7.5)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages222
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages0
Matched the npm:@younndai/lyt@0.20.26 runtime dependency closure — what installing the published package pulls in — 222 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.

57Moderate · 4% of overall
How it's scored
45/45Agent instructions — packages/lyt-vault/src/help/topics/agents.md, packages/lyt-vault/templates/agents.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://linkyourthink.com/llms.txt)
31.5/40Legible commit history — 36 of 61 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://linkyourthink.com/llms.txt
legible_history_share0.59
agent_instruction_filespackages/lyt-vault/src/help/topics/agents.md, packages/lyt-vault/templates/agents.md
agent_instruction_max_bytes2,507
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checking — packages/lyt-llm/tsconfig.json, packages/lyt-mcp/tsconfig.json, packages/lyt-mesh/tsconfig.json, packages/lyt-runner/tsconfig.json, packages/lyt-skills/tsconfig.json, packages/lyt-vault/tsconfig.json, packages/lyt/tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 61
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configspackages/lyt-llm/tsconfig.json, packages/lyt-mcp/tsconfig.json, packages/lyt-mesh/tsconfig.json, packages/lyt-runner/tsconfig.json, packages/lyt-skills/tsconfig.json, packages/lyt-vault/tsconfig.json, packages/lyt/tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
53.9/55Manageable file sizes — 10/512 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes114,686
source_files_sampled512
oversized_source_files10
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

2GitHub stars
1contributors
61commits, last 12 months
12days since last push
1releases
1bus factor
0open 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

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-11-21 15:16 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
10Maintained13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities97 existing vulnerabilities detected
Direct dependencies 37
RegistryPackageVersion constraintManifest
npm@younndai/ai-relay^3.0.0package.json
npm@younndai/domains^2.0.0package.json
npm@younndai/yon-parser^2.0.0package.json
npm@younndai/yon-runner^2.0.0package.json
npm@younndai/ai-relay^3.0.0packages/lyt-llm/package.json
npm@modelcontextprotocol/sdk^1.29.0packages/lyt-mcp/package.json
npm@younndai/lyt-mesh0.21.12packages/lyt-mcp/package.json
npm@younndai/lyt-vault0.21.12packages/lyt-mcp/package.json
npmcommander^12.1.0packages/lyt-mcp/package.json
npmzod^3.25.0packages/lyt-mcp/package.json
npm@libsql/client^0.15.15packages/lyt-mesh/package.json
npm@younndai/lyt-vault0.21.12packages/lyt-mesh/package.json
npmchokidar^4.0.3packages/lyt-mesh/package.json
npmcommander^12.1.0packages/lyt-mesh/package.json
npm@libsql/client^0.15.15packages/lyt-runner/package.json
npm@younndai/lyt-llm0.21.12packages/lyt-runner/package.json
npm@younndai/lyt-vault0.21.12packages/lyt-runner/package.json
npm@younndai/yon-parser^2.0.0packages/lyt-runner/package.json
npm@younndai/yon-runner^2.0.0packages/lyt-runner/package.json
npm@younndai/lyt-vault0.21.12packages/lyt-skills/package.json
npmcommander^12.1.0packages/lyt-skills/package.json
npmsemver^7.7.1packages/lyt-skills/package.json
npm@libsql/client^0.15.15packages/lyt-vault/package.json
npmcommander^12.1.0packages/lyt-vault/package.json
npmlibsql0.5.29packages/lyt-vault/package.json
npmmarked^15.0.12packages/lyt-vault/package.json
npmmarked-terminal^7.3.0packages/lyt-vault/package.json
npmtar^7.5.19packages/lyt-vault/package.json
npmuuid^11.0.0packages/lyt-vault/package.json
npmzod^3.25.76packages/lyt-vault/package.json
npm@libsql/client^0.15.15packages/lyt/package.json
npm@younndai/lyt-mcp0.21.12packages/lyt/package.json
npm@younndai/lyt-mesh0.21.12packages/lyt/package.json
npm@younndai/lyt-runner0.21.12packages/lyt/package.json
npm@younndai/lyt-skills0.21.12packages/lyt/package.json
npm@younndai/lyt-vault0.21.12packages/lyt/package.json
npmcommander^12.1.0packages/lyt/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 1

Installing npm:@younndai/lyt@0.20.26 pulls in 222 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
zod3.25.76indirecthigh14.6.6

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.