Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 17:30 UTC

memo-fs / memofs

File-first memory runtime for AI agents — versioned, portable, and always there when the next session starts.

TypeScript · MDXMIT★ 6 stars⑂ 2 forkssince Jul 2026View on GitHub ↗
KindCommand-line toolMCP serverLibraryhow this is determined

memo-fs/memofs holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on AI Readiness (84/100) and lowest on Vitality (35/100). It was last updated 12 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

MemoFSOrganization · verified domain
2 followers1 public reposince Jul 2026

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

Package ecosystems

Metrics by category

Vitality

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

35Weak · 21% of overall
How it's scored
28.8/36Push recencylast push 12 days ago
11.1/36Commit cadence16/52 weeks with commits
18/18Commit volume427 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year427
human_commit_share1
days_since_last_push12
active_weeks_last_year16
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno 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?

49Weak · 17% of overall
How it's scored
11.3/60Stars6 stars
0/25Forks2 forks
0/15Watchers0 watchers
Inputs used
forks2
stars6
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
40.5/80Monthly downloads1,082 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@memofs/cli, @memofs/core, @memofs/server, @memofs/testing, @memofs/json-rpc, @memofs/adapter-r2, @memofs/connectors
dependents
ecosystemsnpm
total_downloads
monthly_downloads1,082
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?

58Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution100% of issues closed
26.5/30PR acceptance15/17 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/5 approved changesets -- score normalized to 0
Inputs used
merged_prs15
open_issues0
closed_issues7
prs_merged_7d0
prs_decided_7d0
prs_merged_30d6
prs_decided_30d8
issue_closed_ratio1
closed_unmerged_prs2
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 backingorganization-owned
20/20Verified domain
3.4/25Owner reach2 followers of memo-fs
2.6/25Track record1 public repos, account ~0 yr old
Inputs used
followers2
owner_typeOrganization
is_verifiedyes
owner_loginmemo-fs
public_repos1
account_age_days68

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable7 package(s) on npm
35/35Publish recencylatest publish 33 days ago
20/20Version history8 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@memofs/cli, @memofs/core, @memofs/server, @memofs/testing, @memofs/json-rpc, @memofs/adapter-r2, @memofs/connectors
ecosystemsnpm
any_deprecatedno
min_days_since_publish33

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configbiome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests1 out of 5 merged PRs checked by a CI test -- score normalized to 2
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 sitehttps://docs.memofs.dev
10/10Repository description
10/10Topics20 topics
10/10Wiki
Inputs used
topicsai, ai-memory, ai-memory-system, recall, vector-search, ai-agents, claude-code, claude-code-hooks, codex, codex-hooks, developer-tools, llm-memory, opencode, opencode-plugin, agent-memory, claude-code-plugin, coding-agents, mcp, mcp-server, model-context-protocol
has_wikiyes
homepagehttps://docs.memofs.dev
docs_sitehttps://docs.memofs.dev
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

52Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0.5/2.5CI-Tests1 out of 5 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/5 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
0/5Packagingno data
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
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities43 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages4
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:@memofs/cli@1.3.0-beta.2 runtime dependency closure — what installing the published package pulls in — 4 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.

84Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://docs.memofs.dev/llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.memofs.dev/llms.txt
legible_history_share1
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes2,546
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configbiome.json
11/11Static type checkingapps/docs/tsconfig.json, benchmarks/tsconfig.json, examples/tsconfig.json, packages/adapter-ai-sdk/tsconfig.json, packages/adapter-openai/tsconfig.json, packages/adapter-r2/tsconfig.json, packages/adapter-transformers/tsconfig.json, packages/adapter-turso/tsconfig.json, packages/adapter-voyage/tsconfig.json, packages/adapter-workers-ai/tsconfig.json, packages/benchmark-kit/tsconfig.json, packages/cli/tsconfig.json, packages/connectors/tsconfig.json, packages/core/tsconfig.json, packages/json-rpc/tsconfig.json, packages/mcp-server/tsconfig.json, packages/server/tsconfig.json, packages/spec/tsconfig.json, packages/testing/tsconfig.json, tooling/utils/tsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json, pnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsapps/docs/tsconfig.json, benchmarks/tsconfig.json, examples/tsconfig.json, packages/adapter-ai-sdk/tsconfig.json, packages/adapter-openai/tsconfig.json, packages/adapter-r2/tsconfig.json, packages/adapter-transformers/tsconfig.json, packages/adapter-turso/tsconfig.json, packages/adapter-voyage/tsconfig.json, packages/adapter-workers-ai/tsconfig.json, packages/benchmark-kit/tsconfig.json, packages/cli/tsconfig.json, packages/connectors/tsconfig.json, packages/core/tsconfig.json, packages/json-rpc/tsconfig.json, packages/mcp-server/tsconfig.json, packages/server/tsconfig.json, packages/spec/tsconfig.json, packages/testing/tsconfig.json, tooling/utils/tsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/678 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes26,238
source_files_sampled678
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
20/20MCP server
40/40Runnable examplesexamples
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

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

Data collection warnings

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

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

111222212026-082026-082026-08
OpenSSF Scorecard 4.0 / 10
4.0aggregate

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-18 17:29 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
2CI-Tests1 out of 5 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/5 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities43 existing vulnerabilities detected
Direct dependencies 23
RegistryPackageVersion constraintManifest
npm@memofs/coreworkspace:^packages/adapter-ai-sdk/package.json
npmzod^4.4.2packages/adapter-ai-sdk/package.json
npm@memofs/coreworkspace:^packages/adapter-openai/package.json
npmopenai^6.10.0packages/adapter-openai/package.json
npm@memofs/coreworkspace:^packages/adapter-r2/package.json
npm@huggingface/transformers^3.7.6packages/adapter-transformers/package.json
npm@memofs/coreworkspace:^packages/adapter-transformers/package.json
npm@memofs/coreworkspace:^packages/adapter-turso/package.json
npm@memofs/coreworkspace:^packages/adapter-voyage/package.json
npm@memofs/coreworkspace:^packages/adapter-workers-ai/package.json
npm@memofs/coreworkspace:^packages/benchmark-kit/package.json
npm@memofs/testingworkspace:^packages/benchmark-kit/package.json
npm@memofs/coreworkspace:^packages/cli/package.json
npm@memofs/connectorsworkspace:^packages/cli/package.json
npmcommander^14.0.3packages/cli/package.json
npm@memofs/coreworkspace:^packages/connectors/package.json
npmzod^4.4.2packages/core/package.json
npm@modelcontextprotocol/sdk>=1.29.0packages/mcp-server/package.json
npm@memofs/coreworkspace:^packages/mcp-server/package.json
npm@memofs/json-rpcworkspace:^packages/mcp-server/package.json
npm@memofs/coreworkspace:^packages/server/package.json
npm@memofs/json-rpcworkspace:^packages/server/package.json
npmajv^8.20.0packages/spec/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 0

Installing npm:@memofs/cli@1.3.0-beta.2 pulls in 4 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.

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.