Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-20 05:38 UTC

upstash / cli

Upstash CLI

TypeScriptMIT★ 31 stars⑂ 2 forkssince May 2022View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

upstash/cli holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (79/100) and lowest on Community & Adoption (44/100). It was last updated 8 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

UpstashOrganization
1,581 followers138 public repossince Nov 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@upstash/cli1.3.03,6873112 days agoupstashcli

Metrics by category

Vitality

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

70Good · 21% of overall

Development activity

56Moderate
How it's scored
28.8/36Push recency — last push 8 days ago
4.2/36Commit cadence — 6/52 weeks with commits
14/18Commit volume — 35 commits in the last year
9/10OpenSSF Scorecard: Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year35
human_commit_share1
days_since_last_push8
active_weeks_last_year6

Release discipline

92Excellent
How it's scored
27/27Ships releases — 24 releases published
36/36Release recency — latest release 12 days ago
19.8/27Release cadence — a release every ~71.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count24
latest_release_tagv1.3.0
releases_from_tagsno
days_since_latest_release12
mean_days_between_releases71.3
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?

44Weak · 17% of overall

Popularity & adoption

28At Risk
How it's scored
24/60Stars — 31 stars
0/25Forks — 2 forks
3.9/15Watchers — 6 watchers
Inputs used
forks2
stars31
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
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_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Ecosystem adoption (downloads)

60Moderate
How it's scored
47.6/80Monthly downloads — 3,687 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@upstash/cli
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads3,687
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?

79Good · 23% of overall

Maintainer resilience (bus factor)

55Moderate
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.4/22.5Commit distribution — top contributor authored 40% of commits
6.8/13.5Contributor breadth — 5 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor2
contributors_sampled5
top_contributor_share0.403

Issue & PR responsiveness

92Excellent
How it's scored
42/42Issue resolution — 100% of issues closed
27.7/30PR acceptance — 12/13 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 6/8 approved changesets -- score normalized to 7
Inputs used
merged_prs12
open_issues0
closed_issues6
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio1
closed_unmerged_prs1
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.

Ownership & stewardship

78Good
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
23/25Owner reach — 1,581 followers of upstash
24.6/25Track record — 138 public repos, account ~5 yr old
Inputs used
followers1,581
owner_typeOrganization
is_verifiedno
owner_loginupstash
public_repos138
account_age_days2,125

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 12 days ago
20/20Version history — 31 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@upstash/cli
ecosystemsnpm
any_deprecatedno
min_days_since_publish12

Engineering Quality

Are baseline engineering and documentation practices in place?

58Moderate · 19% of overall

Engineering practices

64Moderate
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 7 out of 8 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

55Moderate · 16% of overall

Security posture

44Weak
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2/2.5CI-Tests — 7 out of 8 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-Review — Found 6/8 approved changesets -- score normalized to 7
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
6.8/7.5Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
5/5Packaging — packaging workflow detected
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
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 — 13 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

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

60Moderate · 4% of overall

Agent context & guidance

55Moderate
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://upstash.com/llms.txt)
40/40Legible commit history — 55 of 62 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://upstash.com/llms.txt
legible_history_share0.887
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

49Weak
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
3.2/10Demonstrated agent practice — 1 of the last 62 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0.016
toolchain_manifests—
dependency_bot_commit_share0

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/92 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes19,252
source_files_sampled92
oversized_source_files0

Key facts

31GitHub stars
5contributors
35commits, last 12 months
8days since last push
24releases
2bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

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

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.

111222212023-072024-122026-06
Major 0Minor 1Patch 0

Each point covers 3 days.

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-09-20 05:37 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests7 out of 8 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 6/8 approved changesets -- score normalized to 7
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
9Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
10Packagingpackaging workflow detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
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
0Vulnerabilities13 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmcommander^13.0.0package.json
npmdotenv^16.4.5package.json
All dependencies 95

Full resolved dependency set from the GitHub dependency graph: 2 direct and 93 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npmcommander13.1.0direct
npmdotenv16.6.1direct
npm@esbuild/aix-ppc640.21.5indirect
npm@esbuild/android-arm0.21.5indirect
npm@esbuild/android-arm640.21.5indirect
npm@esbuild/android-x640.21.5indirect
npm@esbuild/darwin-arm640.21.5indirect
npm@esbuild/darwin-x640.21.5indirect
npm@esbuild/freebsd-arm640.21.5indirect
npm@esbuild/freebsd-x640.21.5indirect
npm@esbuild/linux-arm0.21.5indirect
npm@esbuild/linux-arm640.21.5indirect
npm@esbuild/linux-ia320.21.5indirect
npm@esbuild/linux-loong640.21.5indirect
npm@esbuild/linux-mips64el0.21.5indirect
npm@esbuild/linux-ppc640.21.5indirect
npm@esbuild/linux-riscv640.21.5indirect
npm@esbuild/linux-s390x0.21.5indirect
npm@esbuild/linux-x640.21.5indirect
npm@esbuild/netbsd-x640.21.5indirect
npm@esbuild/openbsd-x640.21.5indirect
npm@esbuild/sunos-x640.21.5indirect
npm@esbuild/win32-arm640.21.5indirect
npm@esbuild/win32-ia320.21.5indirect
npm@esbuild/win32-x640.21.5indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@rollup/rollup-android-arm-eabi4.60.1indirect
npm@rollup/rollup-android-arm644.60.1indirect
npm@rollup/rollup-darwin-arm644.60.1indirect
npm@rollup/rollup-darwin-x644.60.1indirect
npm@rollup/rollup-freebsd-arm644.60.1indirect
npm@rollup/rollup-freebsd-x644.60.1indirect
npm@rollup/rollup-linux-arm-gnueabihf4.60.1indirect
npm@rollup/rollup-linux-arm-musleabihf4.60.1indirect
npm@rollup/rollup-linux-arm64-gnu4.60.1indirect
npm@rollup/rollup-linux-arm64-musl4.60.1indirect
npm@rollup/rollup-linux-loong64-gnu4.60.1indirect
npm@rollup/rollup-linux-loong64-musl4.60.1indirect
npm@rollup/rollup-linux-ppc64-gnu4.60.1indirect
npm@rollup/rollup-linux-ppc64-musl4.60.1indirect
npm@rollup/rollup-linux-riscv64-gnu4.60.1indirect
npm@rollup/rollup-linux-riscv64-musl4.60.1indirect
npm@rollup/rollup-linux-s390x-gnu4.60.1indirect
npm@rollup/rollup-linux-x64-gnu4.60.1indirect
npm@rollup/rollup-linux-x64-musl4.60.1indirect
npm@rollup/rollup-openbsd-x644.60.1indirect
npm@rollup/rollup-openharmony-arm644.60.1indirect
npm@rollup/rollup-win32-arm64-msvc4.60.1indirect
npm@rollup/rollup-win32-ia32-msvc4.60.1indirect
npm@rollup/rollup-win32-x64-gnu4.60.1indirect
npm@rollup/rollup-win32-x64-msvc4.60.1indirect
npm@types/estree1.0.8indirect
npm@types/node20.19.37indirect
npm@vitest/expect2.1.9indirect
npm@vitest/mocker2.1.9indirect
npm@vitest/pretty-format2.1.9indirect
npm@vitest/runner2.1.9indirect
npm@vitest/snapshot2.1.9indirect
npm@vitest/spy2.1.9indirect
npm@vitest/utils2.1.9indirect
npmassertion-error2.0.1indirect
npmcac6.7.14indirect
npmchai5.3.3indirect
npmcheck-error2.1.3indirect
npmdebug4.4.3indirect
npmdeep-eql5.0.2indirect
npmes-module-lexer1.7.0indirect
npmesbuild0.21.5indirect
npmestree-walker3.0.3indirect
npmexpect-type1.3.0indirect
npmfsevents2.3.3indirect
npmloupe3.2.1indirect
npmmagic-string0.30.21indirect
npmms2.1.3indirect
npmnanoid3.3.11indirect
npmpathe1.1.2indirect
npmpathval2.0.1indirect
npmpicocolors1.1.1indirect
npmpostcss8.5.8indirect
npmrollup4.60.1indirect
npmsiginfo2.0.0indirect
npmsource-map-js1.2.1indirect
npmstackback0.0.2indirect
npmstd-env3.10.0indirect
npmtinybench2.9.0indirect
npmtinyexec0.3.2indirect
npmtinypool1.1.1indirect
npmtinyrainbow1.2.0indirect
npmtinyspy3.0.2indirect
npmtypescript5.9.3indirect
npmundici-types6.21.0indirect
npmvite5.4.21indirect
npmvite-node2.1.9indirect
npmvitest2.1.9indirect
npmwhy-is-node-running2.3.0indirect
Dependency advisories 0

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

Related records

Inspected repositories sharing catalogue tags or ecosystems with upstash/cli. Read them side by side →

94upstash/context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editorsExceptional99cloudposse/atmosAtmos is the open-source runtime for infrastructure — it builds, authenticates, and ships Terraform, OpenTofu, Packer, Ansible, Kubernetes, Helm, and containers the same way on your laptop, in CI, and with AI agents.Exceptional99apache/supersetApache Superset is a Data Visualization and Data Exploration PlatformExceptional99netlify/cliNetlify Command Line InterfaceExceptional99angular/angular-cliCLI tool for AngularExceptional98nrwl/nxThe Monorepo Platform that amplifies both developers and AI agents. Nx optimizes your builds, scales your CI, and fixes failed PRs automatically. Ship in half the time.Exceptional

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.