DSH Plugin Registry
中文EN
Submit plugin
Plugins/dsh-budget

dsh-budget

Automated evidence available

Per-plugin usage budgets and cost caps on the llm/stream waterfall: per-model usage accounting, session and monthly budgets with warn/block transitions, latency windows, and a carbon-footprint estimate.

Author: PerryLink · Usage & Billing · Catalog snapshot: 2026-09-19

Canonical semantic path

Usage, Cost & Resource GovernanceActive Call Governance & OptimizationBudget & Call Limit Enforcement

One primary path; alternate capabilities remain separate.
communication.webhook-alertsinterface.settings-dashboardusage.carbon-estimationusage.consumption-observability.current-consumption-meteringusage.consumption-observability.historical-consumption-accountingusage.energy-carbon-meteringusage.latency-monitoringusage.model-meteringusage.runtime-telemetry-observability

What it may solve

Per-plugin usage budgets and cost caps on the llm/stream waterfall: per-model usage accounting, session and monthly budgets with warn/block transitions, latency windows, and a carbon-footprint estimate.

Imported third-party catalog description; not a Registry verification conclusion.

Sources and public signals

PerryLink/dsh-budget

9 stars · 3051 downloads

Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19

What can currently be confirmed

Active analysis coverage 1/5. Historical chains are retained but do not count toward current coverage.

Not analyzed

Source structure

Source structure has not been analyzed.

Not analyzed

Repository health

Repository metadata has not been analyzed.

Not analyzed

npm release

npm release metadata has not been analyzed.

Analysis complete

DSH compatibility

Conclusion: Compatibility verification did not pass: the DSH process exited during startup. Test environment: DSH 0.1.6-alpha.2, web profile.

Analysis complete

Dependency audit

Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.

Not analyzed

Functional verification

The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.

Analysis complete

Static risk scan

Conclusion: The scan found 3 characteristics that need attention: declares a prepare script, normally used when building or publishing the package, may execute dynamically constructed code, may access the network. This is a bounded automated observation, not a determination of malicious intent.

Analysis complete

Package integrity

Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-budget@0.4.9; SHA-256: 58c2e337e0d54373391e1865677515c8931ef0b513bbb0550fb6b799ed97287b.

Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.

Continue with the latest plugin manager

Describe your task in a DSH conversation and mention dsh-budget. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.

Install or update the plugin manager (latest)