Is @viverse/sdk safe to use?

@viverse/sdk has no known vulnerabilities on the latest version (1.3.3). DepScope rates its health at 43/100 (high risk).

What is the latest version of @viverse/sdk?

The latest version of @viverse/sdk is 1.3.3, released 2025-11-20.

Does @viverse/sdk have known vulnerabilities?

No known vulnerabilities on the latest version of @viverse/sdk.

Is @viverse/sdk deprecated?

No, @viverse/sdk is actively maintained. Latest release: 1.3.3 (2025-11-20).

What are alternatives to @viverse/sdk?

Popular alternatives to @viverse/sdk in npm include: ?, minimatch, debug, ansi-styles, brace-expansion.

What license does @viverse/sdk use?

@viverse/sdk is licensed under SEE LICENSE IN LICENSE.md.

@viverse/sdk

npmv1.3.3

VIVERSE SDK

License SEE LICENSE IN LICENSE.md9 versions1 maintainers3 deps

https://ssh.dev.azure.com/v3/viveportengineering/VIVEPORTWEB/viverse-sdk

/ 100

Health

use with caution

@viverse/[email protected] low health (43/100) — consider alternatives

Moderate health score (43/100) — verify manually

Health breakdown0 – 100

10/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (3)

crypto-js es-cookie jsencrypt

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@viverse/sdk