Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 08:50 UTC

lyraai-protocol / lyra

A Sui-native, policy-bound, non-custodial AI finance agent. Natural-language goals → policy-checked PTBs, executed only within approved on-chain scope, with auditable Walrus receipts.

TypeScriptMIT★ 1 star⑂ 1 forksince Jun 2026View on GitHub ↗
KindCommand-line toolLibraryWeb interfacehow this is determined

lyraai-protocol/lyra holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (74/100) and lowest on Community & Adoption (28/100). It was last updated 23 days ago. 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

Lyra AIOrganization
1 follower3 public repossince Jul 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmlyra-ai-agent0.4.3651956 days agolyraaiagentclituisuiwalrusdeepbookdefi
npmlyra-core0.4.1771061 days agolyraaiagentsuitreasurydefipolicy
npmlyra-gateway0.4.1511161 days agolyraaiagentgatewaydaemonsui
npmlyra-plugin-system0.4.1541061 days agolyraaiagentfsshellbrowsersandboxtoolsplugin
npmlyra-plugin-onchain0.4.2571561 days ago—
npmlyra-plugin-telegram0.4.1651061 days agolyraaiagenttelegramgrammyplugin
npmlyra-plugin-onchain-one0.5.041256 days agolyraaiagentsuidefideepbookwalruspolicyplugin

Metrics by category

Vitality

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

70Good · 21% of overall
How it's scored
28.8/36Push recency — last push 23 days ago
3.5/36Commit cadence — 5/52 weeks with commits
18/18Commit volume — 147 commits in the last year
0/10OpenSSF Scorecard: Maintained — project was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year147
human_commit_share1
days_since_last_push23
active_weeks_last_year5

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 7 releases published
36/36Release recency — latest release 54 days ago
27/27Release cadence — a release every ~5.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tagv0.5.0
releases_from_tagsno
days_since_latest_release54
mean_days_between_releases5.4
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?

28At Risk · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars1
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
34/80Monthly downloads — 353 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageslyra-ai-agent, lyra-core, lyra-gateway, lyra-plugin-system, lyra-plugin-telegram, lyra-plugin-onchain-one
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads353
unverified_packages_excludedlyra-plugin-onchain
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?

45Weak · 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
14/42Issue resolution — 33% of issues closed
30/30PR acceptance — 37/37 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/14 approved changesets -- score normalized to 0
Inputs used
merged_prs37
open_issues2
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.333
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): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
2.2/25Owner reach — 1 followers of lyraai-protocol
4.7/25Track record — 3 public repos, account ~0 yr old
Inputs used
followers1
owner_typeOrganization
is_verifiedno
owner_loginlyraai-protocol
public_repos3
account_age_days64

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 7 package(s) on npm
35/35Publish recency — latest publish 56 days ago
20/20Version history — 19 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageslyra-ai-agent, lyra-core, lyra-gateway, lyra-plugin-system, lyra-plugin-onchain, lyra-plugin-telegram, lyra-plugin-onchain-one
ecosystemsnpm
any_deprecatedno
min_days_since_publish56

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — biome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 12 out of 14 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://lyraai.space
10/10Repository description
10/10Topics — 10 topics
0/10Wiki
Inputs used
topicsai-agent, blockchain, deepbook, defi, move, non-custodial, sui, typescript, walrus, web3
has_wikino
homepagehttps://lyraai.space
docs_sitehttps://lyraai.space
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

30At Risk · 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/2.5CI-Tests — 12 out of 14 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/14 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
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
0/7.5Maintained — project was created within the last 90 days. Please review its contents carefully
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 — 53 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate2.4
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
2.3/25Indirect dependencies free of known advisories — 10 affected: vitest 1.6.1 (critical 9.8), uuid 8.3.2 (high 7.5), valibot 0.36.0 (high 7.5), +7 more
17.1/40No advisories left outstanding — 8 advisory-carrying package(s) unaddressed past 90 days; oldest published 579 days ago
Inputs used
sourceosv
advisories13
affected_packages10
assessed_packages628
unassessed_packages0
affected_by_severitycritical 1, high 3, moderate 5, low 1
direct_affected_packages0
Matched the npm:lyra-ai-agent@0.4.3 runtime dependency closure — what installing the published package pulls in — 628 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.

68Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes1,784
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — biome.json
11/11Static type checking — packages/cli/tsconfig.json, packages/core/tsconfig.json, packages/gateway/tsconfig.json, packages/plugin-onchain-one/tsconfig.json, packages/plugin-onchain-two/tsconfig.json, packages/plugin-onchain/tsconfig.json, packages/plugin-system/tsconfig.json, packages/plugin-telegram/tsconfig.json, tsconfig.json
0/10Reproducible environment
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_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configspackages/cli/tsconfig.json, packages/core/tsconfig.json, packages/gateway/tsconfig.json, packages/plugin-onchain-one/tsconfig.json, packages/plugin-onchain-two/tsconfig.json, packages/plugin-onchain/tsconfig.json, packages/plugin-system/tsconfig.json, packages/plugin-telegram/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/355 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes51,042
source_files_sampled355
oversized_source_files0

Key facts

1GitHub stars
1contributors
147commits, last 12 months
23days since last push
7releases
1bus factor
2open 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 2.4 / 10
2.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-13 08:49 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests12 out of 14 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/14 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
0Maintainedproject was created within the last 90 days. Please review its contents carefully
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
0Vulnerabilities53 existing vulnerabilities detected
Direct dependencies 56
RegistryPackageVersion constraintManifest
npmagent-browser^0.26.0package.json
npm@clack/prompts^0.8.2packages/cli/package.json
npm@mysten/sui^1.45.2packages/cli/package.json
npm@opentui/core^0.1.97packages/cli/package.json
npm@opentui/solid^0.1.97packages/cli/package.json
npmlyra-core^0.5.1packages/cli/package.json
npmlyra-gateway^0.5.1packages/cli/package.json
npmlyra-plugin-onchain^0.5.1packages/cli/package.json
npmlyra-plugin-system^0.5.1packages/cli/package.json
npmlyra-plugin-telegram^0.5.1packages/cli/package.json
npmpicocolors^1.1.1packages/cli/package.json
npmqrcode-terminal^0.12.0packages/cli/package.json
npmsolid-js^1.9.12packages/cli/package.json
npm@mysten/sui^1.40.0packages/core/package.json
npm@noble/curves^2.2.0packages/core/package.json
npm@noble/hashes^2.2.0packages/core/package.json
npmgray-matter^4.0.3packages/core/package.json
npmqrcode-terminal^0.12.0packages/core/package.json
npmzod^3.24.1packages/core/package.json
npm@mysten/sui^1.45.2packages/gateway/package.json
npm@noble/curves^2.2.0packages/gateway/package.json
npm@noble/hashes^2.2.0packages/gateway/package.json
npmlyra-core^0.5.1packages/gateway/package.json
npmlyra-plugin-onchain^0.5.1packages/gateway/package.json
npmlyra-plugin-system^0.5.1packages/gateway/package.json
npmlyra-plugin-telegram^0.5.1packages/gateway/package.json
npmzod^3.24.1packages/gateway/package.json
npm@7kprotocol/sdk-ts^4.0.0packages/plugin-onchain-one/package.json
npm@cetusprotocol/aggregator-sdk^1.6.1packages/plugin-onchain-one/package.json
npm@mysten/deepbook-v3^0.18.0packages/plugin-onchain-one/package.json
npm@mysten/sui^1.40.0packages/plugin-onchain-one/package.json
npm@mysten/walrus^0.6.4packages/plugin-onchain-one/package.json
npm@pythnetwork/pyth-sui-js2.2.0packages/plugin-onchain-one/package.json
npm@scallop-io/sui-scallop-sdk^2.4.5packages/plugin-onchain-one/package.json
npm@suilend/sdk1.1.99packages/plugin-onchain-one/package.json
npm@suilend/sui-fe0.3.49packages/plugin-onchain-one/package.json
npmlyra-core^0.5.1packages/plugin-onchain-one/package.json
npmnavi-sdk^1.7.3packages/plugin-onchain-one/package.json
npmzod^3.23.8packages/plugin-onchain-one/package.json
npm@mysten/sui^2.20.3packages/plugin-onchain-two/package.json
npm@wormhole-foundation/sdk^6.1.0packages/plugin-onchain-two/package.json
npm@wormhole-foundation/sdk-sui^6.1.0packages/plugin-onchain-two/package.json
npmlyra-coreworkspace:*packages/plugin-onchain-two/package.json
npm@wormhole-foundation/sdk-evm^6.1.0packages/plugin-onchain-two/package.json
npm@wormhole-foundation/sdk-sui-cctp^6.1.0packages/plugin-onchain-two/package.json
npm@wormhole-foundation/sdk-evm-cctp^6.1.0packages/plugin-onchain-two/package.json
npm@wormhole-foundation/sdk-base^6.1.0packages/plugin-onchain-two/package.json
npmlyra-coreworkspace:*packages/plugin-onchain/package.json
npmlyra-plugin-onchain-oneworkspace:*packages/plugin-onchain/package.json
npmlyra-core^0.5.1packages/plugin-system/package.json
npmagent-browser^0.26.0packages/plugin-system/package.json
npmzod^3.24.1packages/plugin-system/package.json
npm@mysten/sui^1.45.0packages/plugin-telegram/package.json
npmgrammy^1.42.0packages/plugin-telegram/package.json
npmlyra-core^0.5.1packages/plugin-telegram/package.json
npmzod^3.23.8packages/plugin-telegram/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 10

Installing npm:lyra-ai-agent@0.4.3 pulls in 628 packages, direct and transitive: 10 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
vitest1.6.1indirectcritical14.1.0
uuid8.3.2indirecthigh113.0.1
valibot0.36.0indirecthigh21.4.2
vite5.4.21indirecthigh38.0.16
diff8.0.2indirectmoderate18.0.3
esbuild0.21.5indirectmoderate10.25.0
esbuild0.24.2indirectmoderate10.25.0
file-type16.5.4indirectmoderate121.3.1
stream-json1.9.1indirectmoderate13.5.0
@babel/core7.28.0indirectlow18.0.0-rc.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.