Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 01:24 UTC

base44 / cli

Command-line interface for building applications with Base44's backend service.

TypeScriptMIT★ 112 stars⑂ 33 forkssince Jan 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

base44/cli holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Vitality (88/100) and lowest on Security (53/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

87
overall / 100
Excellent

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.

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

Ownership

Base44Organization
210 followers10 public repossince Sep 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmbase440.1.14138,091727 days agobase44clicommand-line

Metrics by category

Vitality

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

88Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
21.5/36Commit cadence — 31/52 weeks with commits
18/18Commit volume — 389 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year389
human_commit_share1
days_since_last_push2
active_weeks_last_year31
How it's scored
27/27Ships releases — 68 releases published
36/36Release recency — latest release 7 days ago
27/27Release cadence — a release every ~4.9 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count68
latest_release_tagv0.1.14
releases_from_tagsno
days_since_latest_release7
mean_days_between_releases4.9

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

57Moderate · 17% of overall
How it's scored
33.2/60Stars — 112 stars
12.5/25Forks — 33 forks
0/15Watchers — 1 watchers
Inputs used
forks33
stars112
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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
68.5/80Monthly downloads — 138,091 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesbase44
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads138,091
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?

74Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
14.6/22.5Commit distribution — top contributor authored 35% of commits
13.5/13.5Contributor breadth — 23 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor2
contributors_sampled23
top_contributor_share0.352
How it's scored
36.8/42Issue resolution — 88% of issues closed
24.6/30PR acceptance — 286/349 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-Review — Found 19/30 approved changesets -- score normalized to 6
Inputs used
merged_prs286
open_issues25
closed_issues176
prs_merged_7d1
prs_decided_7d1
prs_merged_30d16
prs_decided_30d18
issue_closed_ratio0.876
closed_unmerged_prs63
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
16.7/25Owner reach — 210 followers of base44
9.5/25Track record — 10 public repos, account ~0 yr old
Inputs used
followers210
owner_typeOrganization
is_verifiedno
owner_loginbase44
public_repos10
account_age_days347

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 7 days ago
20/20Version history — 72 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesbase44
ecosystemsnpm
any_deprecatedno
min_days_since_publish7

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 13 workflow(s)
24/24Tests present
16/16Linter config — biome.json
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests — 17 out of 23 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://docs.base44.com/developers/home
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://docs.base44.com/developers/home
docs_sitehttps://docs.base44.com/developers/home
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

53Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
1.8/2.5CI-Tests — 17 out of 23 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-Review — Found 19/30 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
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
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
4/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
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 — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 103 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4.7
How it's scored
28/35Direct dependencies free of known advisories — 1 affected: esbuild 0.28.0 (low 2.5)
6.9/25Indirect dependencies free of known advisories — 2 affected: sharp 0.35.2 (high 8.4), undici 7.28.0 (high 7.4)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories7
affected_packages3
assessed_packages83
unassessed_packages0
affected_by_severityhigh 2, low 1
direct_affected_packages1
Matched the npm:base44@0.1.14 runtime dependency closure — what installing the published package pulls in — 83 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.

82Excellent · 4% of overall
How it's scored
45/45Agent instructions — .cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc, AGENTS.md, CLAUDE.md, docs/AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.base44.com/llms.txt)
40/40Legible commit history — 95 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.base44.com/llms.txt
legible_history_share0.95
agent_instruction_files.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc, AGENTS.md, CLAUDE.md, docs/AGENTS.md
agent_instruction_max_bytes7,292
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — biome.json
11/11Static type checking — packages/cli/backend-runtime/tsconfig.json, packages/cli/templates/backend-and-client/jsconfig.json, packages/cli/tests/fixtures/with-types-resources/tsconfig.json, packages/cli/tsconfig.json, packages/logger/tsconfig.json
0/10Reproducible environment
10/10Demonstrated agent practice — 46 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
8/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configspackages/cli/backend-runtime/tsconfig.json, packages/cli/templates/backend-and-client/jsconfig.json, packages/cli/tests/fixtures/with-types-resources/tsconfig.json, packages/cli/tsconfig.json, packages/logger/tsconfig.json
agent_commit_share0.46
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/379 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes29,127
source_files_sampled379
oversized_source_files0

Key facts

112GitHub stars
23contributors
389commits, last 12 months
2days since last push
68releases
2bus factor
25open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package 'base44-cli' from its registry
  • Could not fetch npm package '@base44-cli/logger' 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 ★ / 33 ⇿
0Stars
33Forks
68Releases

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.

01325383322026-012026-052026-09
Major 0Minor 1Patch 67
OpenSSF Scorecard 4.7 / 10
4.7aggregate

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-09 01:24 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
7CI-Tests17 out of 23 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 19/30 approved changesets -- score normalized to 6
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities103 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npm@deno/loaderhttps://npm.jsr.io/~/11/@jsr/deno__loader/0.5.0.tgzpackages/cli/package.json
npmesbuild0.28.0packages/cli/package.json
npmminiflare4.20260722.0packages/cli/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 3

Installing npm:base44@0.1.14 pulls in 83 packages, direct and transitive: 3 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
sharp0.35.2indirecthigh10.35.4
undici7.28.0indirecthigh58.9.0
esbuild0.28.0directlow10.28.1

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.