Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 18:51 UTC

framework / the-framework

Autonomous AI programming. Stop babysitting your coding agents. You make the important decisions; AI does the rest.

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

framework/the-framework holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Vitality (77/100) and lowest on Community & Adoption (37/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

The FrameworkOrganization
9 followers2 public repossince Jun 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmframework0.7.01,5781523 days agoaiagentclaude-codeorchestrationframeworkcodegencliturnkey
npmagent-driver0.0.0192118 days ago—

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
8.3/36Commit cadence — 12/52 weeks with commits
18/18Commit volume — 1,295 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_year1,295
human_commit_share1
days_since_last_push0
active_weeks_last_year12

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 68 releases published
36/36Release recency — latest release 26 days ago
27/27Release cadence — a release every ~3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count68
latest_release_tag@gemstack/the-framework@1.5.0
releases_from_tagsno
days_since_latest_release26
mean_days_between_releases3
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?

37Weak · 17% of overall
How it's scored
16.2/60Stars — 11 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars11
watchers1
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_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
42.6/80Monthly downloads — 1,578 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesframework
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads1,578
unverified_packages_excludedagent-driver
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?

62Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.1/22.5Commit distribution — top contributor authored 73% of commits
4.1/13.5Contributor breadth — 3 contributors
10/10OpenSSF Scorecard: Contributors — project has 12 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.73
How it's scored
41/42Issue resolution — 98% of issues closed
28.3/30PR acceptance — 960/1,017 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/18 approved changesets -- score normalized to 0
Inputs used
merged_prs960
open_issues18
closed_issues734
prs_merged_7d12
prs_decided_7d12
prs_merged_30d54
prs_decided_30d60
issue_closed_ratio0.976
closed_unmerged_prs57
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
7.2/25Owner reach — 9 followers of framework
15.5/25Track record — 2 public repos, account ~8 yr old
Inputs used
followers9
owner_typeOrganization
is_verifiedno
owner_loginframework
public_repos2
account_age_days3,002

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on npm
35/35Publish recency — latest publish 18 days ago
20/20Version history — 15 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesframework, agent-driver
ecosystemsnpm
any_deprecatedno
min_days_since_publish18

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://the-framework.ai
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://the-framework.ai
docs_sitehttps://the-framework.ai
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 — no data
2.5/2.5CI-Tests — 16 out of 16 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/7.5Code-Review — Found 0/18 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 12 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.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 — 21 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate2.9
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — 1 affected: @tiptap/core 2.27.3 (low)
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages88
unassessed_packages0
affected_by_severitylow 1
direct_affected_packages1
Matched the npm:framework@0.7.0 runtime dependency closure — what installing the published package pulls in — 88 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.

73Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 81 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.81
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes443
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — packages/agent-data/tsconfig.json, packages/agent-driver/tsconfig.json, packages/framework/dashboard/tsconfig.json, packages/framework/tsconfig.json, packages/skill-branches/tsconfig.json, packages/skill-logs/tsconfig.json, packages/skill-queue/tsconfig.json, packages/skill-tickets/tsconfig.json, packages/the-framework.ai/tsconfig.json
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 45 of the last 100 commits agent-authored or agent-credited
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
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configspackages/agent-data/tsconfig.json, packages/agent-driver/tsconfig.json, packages/framework/dashboard/tsconfig.json, packages/framework/tsconfig.json, packages/skill-branches/tsconfig.json, packages/skill-logs/tsconfig.json, packages/skill-queue/tsconfig.json, packages/skill-tickets/tsconfig.json, packages/the-framework.ai/tsconfig.json
agent_commit_share0.45
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.6/55Manageable file sizes — 4/606 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes75,724
source_files_sampled606
oversized_source_files4

Key facts

11GitHub stars
3contributors
1,295commits, last 12 months
0days since last push
68releases
1bus factor
18open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package '@gemstack/routines' from its registry
  • Could not fetch npm package '@gemstack/agent-data' from its registry
  • Could not fetch npm package '@gemstack/skill-logs' from its registry
  • Could not fetch npm package '@gemstack/skill-queue' from its registry
  • Could not fetch npm package '@gemstack/skill-tickets' from its registry
  • Could not fetch npm package '@gemstack/skill-branches' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 2.9 / 10
2.9aggregate

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-14 18:50 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/18 approved changesets -- score normalized to 0
10Contributorsproject has 12 contributing companies or organizations
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
0Vulnerabilities21 existing vulnerabilities detected
Direct dependencies 31
RegistryPackageVersion constraintManifest
npm@base-ui-components/react1.0.0-rc.0packages/framework/package.json
npm@gemstack/agent-dataworkspace:*packages/framework/package.json
npm@gemstack/routinesworkspace:*packages/framework/package.json
npm@gemstack/skill-branchesworkspace:*packages/framework/package.json
npm@gemstack/skill-logsworkspace:*packages/framework/package.json
npm@gemstack/skill-queueworkspace:*packages/framework/package.json
npm@gemstack/skill-ticketsworkspace:*packages/framework/package.json
npm@puppeteer/browsers3.2.1packages/framework/package.json
npm@shadcn/react^0.2.1packages/framework/package.json
npm@tiptap/core^2.10.0packages/framework/package.json
npm@tiptap/pm^2.10.0packages/framework/package.json
npm@tiptap/react^2.10.0packages/framework/package.json
npm@tiptap/starter-kit^2.10.0packages/framework/package.json
npm@tiptap/suggestion^2.10.0packages/framework/package.json
npmagent-driverworkspace:*packages/framework/package.json
npmclass-variance-authority^0.7.1packages/framework/package.json
npmclsx^2.1.1packages/framework/package.json
npmlucide-react^0.469.0packages/framework/package.json
npmreact^19.2.0packages/framework/package.json
npmreact-dom^19.2.0packages/framework/package.json
npmtailwind-merge^2.6.0packages/framework/package.json
npmtiptap-markdown^0.8.10packages/framework/package.json
npmyaml^2.5.0packages/framework/package.json
npm@gemstack/agent-dataworkspace:*packages/skill-branches/package.json
npm@gemstack/agent-dataworkspace:*packages/skill-logs/package.json
npm@gemstack/agent-dataworkspace:*packages/skill-queue/package.json
npm@gemstack/agent-dataworkspace:*packages/skill-tickets/package.json
npmreact^19.2.0packages/the-framework.ai/package.json
npmreact-dom^19.2.0packages/the-framework.ai/package.json
npmvike^0.4.235packages/the-framework.ai/package.json
npmvike-react^0.6.5packages/the-framework.ai/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:framework@0.7.0 pulls in 88 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
@tiptap/core2.27.3directlow13.30.4

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.