Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-17 16:43 UTC

lemmaoracle / lemma

Give AI proven facts — a cryptographically verified truth layer for agent AI, built on ZK proofs, selective disclosure, and on-chain provenance.

Astro · TypeScript · HTMLCustom license★ 1 star⑂ 1 forksince Feb 2026View on GitHub ↗
KindLibraryMCP serverCommand-line toolhow this is determined

lemmaoracle/lemma holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on AI Readiness (88/100) and lowest on Community & Adoption (30/100). It was last updated today. A single contributor accounts 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

lemmaoracleOrganization
2 followers8 public repossince Feb 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@lemmaoracle/mcp0.0.2323621119 days ago—
npm@lemmaoracle/sdk0.1.32,1004261 days ago—
npm@lemmaoracle/agent0.0.358014119 days agolemmaagentidentitycredentialauthorityschemawasm
npm@lemmaoracle/parser0.0.354524119 days ago—
npm@lemmaoracle/content0.1.017192 days agolemmacontentcommitmentzkcircuit

Metrics by category

Vitality

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

54Moderate · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
26.3/36Commit cadence — 38/52 weeks with commits
18/18Commit volume — 1,778 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,778
human_commit_share1
days_since_last_push0
active_weeks_last_year38
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

30At 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
16.9/22.5License — license file present, not a recognized license
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
44.9/80Monthly downloads — 2,336 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@lemmaoracle/mcp, @lemmaoracle/sdk
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads2,336
unverified_packages_excluded@lemmaoracle/agent, @lemmaoracle/parser, @lemmaoracle/content
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?

58Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.7/22.5Commit distribution — top contributor authored 53% of commits
6.8/13.5Contributor breadth — 5 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.526
How it's scored
26.7/42Issue resolution — 64% of issues closed
29.1/30PR acceptance — 1,126/1,160 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 3/27 approved changesets -- score normalized to 1
Inputs used
merged_prs1,126
open_issues4
closed_issues7
prs_merged_7d22
prs_decided_7d22
prs_merged_30d60
prs_decided_30d60
issue_closed_ratio0.636
closed_unmerged_prs34
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
3.4/25Owner reach — 2 followers of lemmaoracle
8.4/25Track record — 8 public repos, account ~0 yr old
Inputs used
followers2
owner_typeOrganization
is_verifiedno
owner_loginlemmaoracle
public_repos8
account_age_days274

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 5 package(s) on npm
35/35Publish recency — latest publish 61 days ago
20/20Version history — 42 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@lemmaoracle/mcp, @lemmaoracle/sdk, @lemmaoracle/agent, @lemmaoracle/parser, @lemmaoracle/content
ecosystemsnpm
any_deprecatedno
min_days_since_publish61

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js, packages/relay/package.json ("eslintConfig")
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 26 out of 26 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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://lemma.frame00.com/
10/10Repository description
10/10Topics — 10 topics
0/10Wiki
Inputs used
topicsai-agents, did, provenance, rag, selective-disclosure, trusted-web, typescript, verifiable-ai, zero-knowledge-proofs, zk
has_wikino
homepagehttps://lemma.frame00.com/
docs_sitehttps://lemma.frame00.com/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

39Weak · 16% of overall
How it's scored
6/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 26 out of 26 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 3/27 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 5 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
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 — 40 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.5
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: zod 3.25.76 (high 7.5)
5.2/25Indirect dependencies free of known advisories — 4 affected: @modelcontextprotocol/sdk 1.29.0 (high 8.6), picomatch 4.0.7 (high 7.5), underscore 1.13.6 (high 7.5), +1 more
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 258 days ago
Inputs used
sourceosv
advisories10
affected_packages5
assessed_packages198
unassessed_packages0
affected_by_severityhigh 4, moderate 1
direct_affected_packages1
Matched the npm:@lemmaoracle/mcp@0.0.23 runtime dependency closure — what installing the published package pulls in — 198 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.

88Excellent · 4% of overall
How it's scored
45/45Agent instructions — .cursorrules, AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://lemma.frame00.com/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://lemma.frame00.com/llms.txt
legible_history_share1
agent_instruction_files.cursorrules, AGENTS.md, CLAUDE.md
agent_instruction_max_bytes1,233
How it's scored
12.6/18One-command bootstrap — packages/agent/Cargo.toml, packages/agent/normalize/Cargo.toml, packages/canonical-sort/normalize/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — eslint.config.js, packages/relay/package.json ("eslintConfig")
11/11Static type checking — packages/account-change/circuits/tsconfig.json, packages/account-change/tsconfig.json, packages/agent/tsconfig.json, packages/artifacts/tsconfig.json, packages/blog-article/circuits/tsconfig.json, packages/canonical-sort/tsconfig.json, packages/content/circuits/tsconfig.json, packages/content/tsconfig.json, packages/data-commitment/tsconfig.json, packages/demo/tsconfig.json, packages/feeds/tsconfig.json, packages/fetcher/tsconfig.json, packages/mcp/tsconfig.json, packages/parser/tsconfig.json, packages/passthrough/tsconfig.json, packages/relay/tsconfig.json, packages/sdk/tsconfig.json, packages/seal/tsconfig.json, packages/spec/tsconfig.json, packages/transform/tsconfig.json, packages/trust402/tsconfig.json, packages/verify/tsconfig.json, packages/web/tsconfig.json, packages/x402/tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 69 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
1/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, package-lock.json, pnpm-lock.yaml
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configspackages/account-change/circuits/tsconfig.json, packages/account-change/tsconfig.json, packages/agent/tsconfig.json, packages/artifacts/tsconfig.json, packages/blog-article/circuits/tsconfig.json, packages/canonical-sort/tsconfig.json, packages/content/circuits/tsconfig.json, packages/content/tsconfig.json, packages/data-commitment/tsconfig.json, packages/demo/tsconfig.json, packages/feeds/tsconfig.json, packages/fetcher/tsconfig.json, packages/mcp/tsconfig.json, packages/parser/tsconfig.json, packages/passthrough/tsconfig.json, packages/relay/tsconfig.json, packages/sdk/tsconfig.json, packages/seal/tsconfig.json, packages/spec/tsconfig.json, packages/transform/tsconfig.json, packages/trust402/tsconfig.json, packages/verify/tsconfig.json, packages/web/tsconfig.json, packages/x402/tsconfig.json
agent_commit_share0.69
toolchain_manifestspackages/agent/Cargo.toml, packages/agent/normalize/Cargo.toml, packages/canonical-sort/normalize/Cargo.toml, packages/passthrough/Cargo.toml, packages/transform/normalize/Cargo.toml
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Astro with type-check config (packages/account-change/circuits/tsconfig.json, packages/account-change/tsconfig.json, packages/agent/tsconfig.json, packages/artifacts/tsconfig.json, packages/blog-article/circuits/tsconfig.json, packages/canonical-sort/tsconfig.json, packages/content/circuits/tsconfig.json, packages/content/tsconfig.json, packages/data-commitment/tsconfig.json, packages/demo/tsconfig.json, packages/feeds/tsconfig.json, packages/fetcher/tsconfig.json, packages/mcp/tsconfig.json, packages/parser/tsconfig.json, packages/passthrough/tsconfig.json, packages/relay/tsconfig.json, packages/sdk/tsconfig.json, packages/seal/tsconfig.json, packages/spec/tsconfig.json, packages/transform/tsconfig.json, packages/trust402/tsconfig.json, packages/verify/tsconfig.json, packages/web/tsconfig.json, packages/x402/tsconfig.json)
54.4/55Manageable file sizes — 4/360 source files over 60KB
Inputs used
primary_languageAstro
largest_source_bytes144,599
source_files_sampled360
oversized_source_files4
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
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

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

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'lemma-agent' from its registry
  • Could not fetch npm package '@lemmaoracle/feeds' from its registry
  • Could not fetch npm package '@lemmaoracle/roles' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 3.5 / 10
3.5aggregate

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-17 16:42 UTC

8Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests26 out of 26 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/27 approved changesets -- score normalized to 1
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
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
0Vulnerabilities40 existing vulnerabilities detected
Direct dependencies 58
RegistryPackageVersion constraintManifest
npm@lemmaoracle/sdkworkspace:*packages/account-change/package.json
npm@lemmaoracle/specworkspace:*packages/account-change/package.json
npmdotenv^16.4.5packages/account-change/package.json
crates.iowasm-bindgen0.2packages/agent/Cargo.toml
crates.iojs-sys0.3packages/agent/Cargo.toml
crates.ioserde1packages/agent/Cargo.toml
crates.ioserde_json1packages/agent/Cargo.toml
npm@lemmaoracle/sdkworkspace:*packages/agent/package.json
npm@lemmaoracle/specworkspace:*packages/agent/package.json
npmposeidon-lite0.3.0packages/agent/package.json
npmramda0.30.1packages/agent/package.json
npm@lemmaoracle/sdkworkspace:*packages/attestation/package.json
npm@lemmaoracle/specworkspace:*packages/attestation/package.json
npmsnarkjs^0.7.6packages/attestation/package.json
npm@lemmaoracle/sdkworkspace:*packages/blog-article/package.json
npm@lemmaoracle/specworkspace:*packages/blog-article/package.json
npmposeidon-lite^0.3.0packages/content/package.json
npm@lemmaoracle/sdkworkspace:*packages/content/package.json
npm@lemmaoracle/specworkspace:*packages/content/package.json
npm@lemmaoracle/canonical-sortworkspace:*packages/data-commitment/package.json
npm@lemmaoracle/sdkworkspace:*packages/data-commitment/package.json
npm@noble/hashes^1.7.0packages/data-commitment/package.json
npmposeidon-lite^0.2.0packages/data-commitment/package.json
npm@lemmaoracle/fetcherworkspace:*packages/feeds/package.json
npm@lemmaoracle/sdkworkspace:*packages/feeds/package.json
npm@trust402/sdkworkspace:*packages/feeds/package.json
npmposeidon-lite^0.2.0packages/feeds/package.json
npm@lemmaoracle/sdkworkspace:*packages/fetcher/package.json
npm@lemmaoracle/sdk^0.0.31packages/mcp/package.json
npm@lemmaoracle/spec^0.0.30packages/mcp/package.json
npm@modelcontextprotocol/sdk1.29.0packages/mcp/package.json
npmagents^0.11.4packages/mcp/package.json
npmramda^0.30.1packages/mcp/package.json
npmzod^3.24.0packages/mcp/package.json
npm@huggingface/transformers^3.8.0packages/parser/package.json
npmonnxruntime-node^1.21.0packages/parser/package.json
npmramda^0.30.1packages/parser/package.json
crates.iowasm-bindgen0.2packages/passthrough/Cargo.toml
crates.iojs-sys0.3packages/passthrough/Cargo.toml
npm@lemmaoracle/sdkworkspace:*packages/passthrough/package.json
npm@lemmaoracle/specworkspace:*packages/passthrough/package.json
npmramda0.30.1packages/passthrough/package.json
npm@lemmaoracle/sdkworkspace:*packages/relay/package.json
npmramda^0.30.1packages/relay/package.json
npm@lemmaoracle/sdkworkspace:*packages/roles/package.json
npm@lemmaoracle/specworkspace:*packages/roles/package.json
npm@trust402/sdkworkspace:*packages/roles/package.json
npmdotenv^16.4.5packages/roles/package.json
npmsnarkjs^0.7.6packages/roles/package.json
npm@docknetwork/crypto-wasm^0.35.0packages/sdk/package.json
npm@lemmaoracle/specworkspace:*packages/sdk/package.json
npm@noble/ciphers^1.2.0packages/sdk/package.json
npm@noble/curves^1.8.0packages/sdk/package.json
npm@noble/hashes^1.7.0packages/sdk/package.json
npmbuffer^6.0.3packages/sdk/package.json
npmposeidon-lite^0.2.0packages/sdk/package.json
npmramda^0.30.1packages/sdk/package.json
npmsnarkjs^0.7.5packages/sdk/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 5

Installing npm:@lemmaoracle/mcp@0.0.23 pulls in 198 packages, direct and transitive: 5 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
zod3.25.76directhigh14.6.6
@modelcontextprotocol/sdk1.29.0indirecthigh62.3.1
picomatch4.0.7indirecthigh1—
underscore1.13.6indirecthigh11.13.8
@hono/node-server1.19.18indirectmoderate12.1.3

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.