dsh-deepseek-usage
Shows the DeepSeek account balance as a row in the sidebar footer with a refresh button, and opens a popover with the balance card, daily token and estimated-cost charts over a 7/30-day window, a per-model table, and a link to the platform usage page. The balance comes from the official /user/balance endpoint; usage is aggregated from local DSH session logs and priced with the published peak/off-peak rate card in CNY, so it is labelled an estimate and its scope is stated on the panel.
On this page
Review info: no independent structural review record is currently matched.
Community signals
Category
Usage & Billing
GitHub stars
0
npm downloads
—
Discovery registry added
2026-09-20
Review information
Scanner status
No review data
Review mode
No review data
Last checked
No review data
Build approval required
No review data
Lifecycle scripts
No review data
Runtime artifacts committed
No review data
Documented profiles
No review data
Why this site does not provide the install command
A third-party DSH plugin is executable local code. Even when structural review evidence exists, registry data, stars and metadata cannot prove the code is non-malicious. Read the current author repository and perform your own review in a disposable environment.
Install and usage source
This site links to the author's source, npm page and community registry instead of redistributing commands. A plugin may add Web UI, Settings, agent tools or background capabilities; follow the author README for the actual entry point.
Minimum checks before install
- Confirm package.json, the bundle patch and README belong to the same author repository.
- Inspect preinstall/install/postinstall/prepare, child_process, shell, filesystem, network calls and credential access.
- First install into a disposable profile/workspace without production credentials or an important repository.
- If pnpm asks for allowBuilds/build approval, treat it as permission to execute third-party code during installation; do not approve mechanically.
- For reproducibility, pin an exact npm version or Git commit yourself instead of depending on main/latest.
“Third-party” only means the plugin is not an official DeepSeek plugin. Structural checks improve transparency but cannot prove business logic is non-malicious or fully audit dependencies, future updates or runtime behavior.