Is SAP HANA CLI safe and trustworthy?

tashan scores SAP HANA CLI on public evidence — tashan score 55.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, it runs a script at install time, its declared dependencies reach: credentials, filesystem. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install SAP HANA CLI?

In Claude Code: run `claude mcp add hana-cli -- npx -y hana-cli`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains SAP HANA CLI?

source: SAP-samples/hana-developer-cli-tool-example.

‹ The Index

SAP HANA CLI

npm

150+ SAP HANA database tools as MCP tools for AI assistants

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Work: Database access

Who it is for: Software engineer · Data analyst

Install (Claude Code):

claude mcp add hana-cli -- npx -y hana-cli

tashan score: 55.0
Adoption: 428/wk
Upkeep: 66.0
Freshness: 80.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: SEE LICENSE IN LICENSE

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 4.202607.1 — this package, not its dependency tree

Runs a script at install timecodenode scripts/postinstall.js

Handles credentials or secrets · Reads and writes filesfrom declared dependencies

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-09-13 the tashan score for hana-cli fell to 55.0, from 60.0 Upkeep, freshness or adoption moved enough to change how this measures.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 1 change to SAP HANA CLI in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-hana-cli.svg)](https://tashan.sh/capability/pkg-hana-cli.html)

npm ↗ · source ↗ · pkg:hana-cli

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?