Public record
Software health reportschema 0.13.0 · metrics 2.10.0 · 2026-07-18 15:15 UTC

smartmemory / compose

AI-powered product lifecycle orchestrator — takes a product idea from intent to shipped code through agent-driven pipelines (Claude + Codex) with human gates, postconditions, and auditable traces.

JavaScriptMIT★ 2 stars⑂ 1 forksince Apr 2026View on GitHub ↗
KindMCP serverLibraryNetwork serviceWeb interfacehow this is determined

smartmemory/compose holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Vitality (87/100) and lowest on Community & Adoption (32/100). It was last updated today. A single contributor accounts for most of its recent work.

65
overall / 100
Good

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.

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

Ownership

SmartMemoryOrganization
0 followers10 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@smartmemory/compose0.2.512,85010528 days agocomposesmartmemoryaiorchestrationagentpipelinestratumclaudecodexcli

Metrics by category

Vitality

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

87Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
13.8/36Commit cadence20/52 weeks with commits
18/18Commit volume938 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year938
human_commit_share
days_since_last_push0
active_weeks_last_year20

Release discipline

100Exceptional
How it's scored
27/27Ships releases2 releases published
36/36Release recencylatest release 28 days ago
27/27Release cadencea release every ~21.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count2
latest_release_tagv0.2.51
releases_from_tagsno
days_since_latest_release28
mean_days_between_releases21.6
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?

32At Risk · 17% of overall
How it's scored
0/60Stars2 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars2
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
46.1/80Monthly downloads2,850 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@smartmemory/compose
dependents
ecosystemsnpm
total_downloads
monthly_downloads2,850
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.1/22.5Commit distributiontop contributor authored 91% of commits
5.4/13.5Contributor breadth4 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.908
How it's scored
33.6/42Issue resolution80% of issues closed
28/30PR acceptance14/15 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs14
open_issues4
closed_issues16
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.8
closed_unmerged_prs1
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
0/25Owner reach0 followers of smartmemory
8.5/25Track record10 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verified
owner_loginsmartmemory
public_repos10
account_age_days164
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 28 days ago
20/20Version history105 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@smartmemory/compose
ecosystemsnpm
any_deprecatedno
min_days_since_publish28

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://github.com/smartmemory/stratum
10/10Repository description
10/10Topics6 topics
10/10Wiki
Inputs used
topicsagent-orchestration, ai-agents, claude, codex, developer-tools, llm
has_wikiyes
homepagehttps://github.com/smartmemory/stratum
docs_sitehttps://github.com/smartmemory/stratum
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

44Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): CI-Tests, Signed-Releases. Remaining weights renormalized.

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.

45Weak · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md, docs/agents.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesCLAUDE.md, docs/agents.md
agent_instruction_max_bytes2,704
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
54.7/55Manageable file sizes5/875 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes202,962
source_files_sampled875
oversized_source_files5
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalyes
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

2GitHub stars
4contributors
938commits, last 12 months
0days since last push
2releases
1bus factor
4open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • Could not fetch npm package '@smartmemory/compose-mcp' from its registry
  • Could not fetch pypi package 'stratum-mcp-kernel' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.4 / 10
4.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-07-18 15:15 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
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow 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
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 43
RegistryPackageVersion constraintManifest
npm@smartmemory/compose^0.1.5-betacompose-mcp/package.json
npm@anthropic-ai/claude-agent-sdk^0.2.47package.json
npm@dagrejs/dagre^2.0.4package.json
npm@hello-pangea/dnd^18.0.1package.json
npm@modelcontextprotocol/sdk^1.26.0package.json
npm@opencode-ai/sdk^1.2.17package.json
npm@radix-ui/react-collapsible^1.1.12package.json
npm@radix-ui/react-dialog^1.1.15package.json
npm@radix-ui/react-dropdown-menu^2.1.16package.json
npm@radix-ui/react-scroll-area^1.2.10package.json
npm@radix-ui/react-select^2.2.6package.json
npm@radix-ui/react-separator^1.1.8package.json
npm@radix-ui/react-slot^1.2.4package.json
npm@radix-ui/react-toggle^1.1.10package.json
npm@radix-ui/react-toggle-group^1.1.11package.json
npm@radix-ui/react-tooltip^1.2.8package.json
npm@tanstack/react-virtual^3.13.23package.json
npmajv^8.18.0package.json
npmajv-formats^3.0.1package.json
npmclass-variance-authority^0.7.1package.json
npmclsx^2.1.1package.json
npmcors^2.8.5package.json
npmcytoscape^3.33.1package.json
npmcytoscape-dagre^2.5.0package.json
npmcytoscape-fcose^2.2.0package.json
npmdate-fns^3.6.0package.json
npmdiff^8.0.4package.json
npmexpress^4.21.0package.json
npmlucide-react^0.563.0package.json
npmmermaid^11.13.0package.json
npmqrcode^1.5.4package.json
npmqrcode-terminal^0.12.0package.json
npmreact^19.2.5package.json
npmreact-dom^19.2.5package.json
npmreact-markdown^10.1.0package.json
npmremark-gfm^4.0.1package.json
npmtailwind-merge^3.4.0package.json
npmtailwindcss-animate^1.0.7package.json
npmuuid^11.0.0package.json
npmws^8.18.0package.json
npmyaml^2.8.2package.json
npmzustand^5.0.11package.json
PyPIpyyaml>=6.0stratum-mcp/pyproject.toml
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

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.13.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.