Is @smithers-orchestrator/usage safe to use?

@smithers-orchestrator/usage has no known vulnerabilities on the latest version (0.32.0). DepScope rates its health at 62/100 (moderate risk).

What is the latest version of @smithers-orchestrator/usage?

The latest version of @smithers-orchestrator/usage is 0.32.0, released 2026-08-01.

Does @smithers-orchestrator/usage have known vulnerabilities?

No known vulnerabilities on the latest version of @smithers-orchestrator/usage.

Is @smithers-orchestrator/usage deprecated?

No, @smithers-orchestrator/usage is actively maintained. Latest release: 0.32.0 (2026-08-01).

What are alternatives to @smithers-orchestrator/usage?

Popular alternatives to @smithers-orchestrator/usage in npm include: ?, semver, debug, minimatch.

What license does @smithers-orchestrator/usage use?

License information for @smithers-orchestrator/usage is not declared in the registry metadata.

@smithers-orchestrator/usage

npmv0.32.0

Report how much rate limit or subscription quota each registered Smithers account has consumed, across Claude, Codex, OpenAI, Anthropic, and Google providers.

16 versions1 maintainers1 deps4,897 weekly dl

/ 100

Health

use with caution

@smithers-orchestrator/[email protected] low health (62/100) — consider alternatives

Moderate health score (62/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

6/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

@smithers-orchestrator/accounts

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@smithers-orchestrator/usage