Is @voyantjs/cruises-contracts safe to use?

@voyantjs/cruises-contracts has no known vulnerabilities on the latest version (0.105.2). DepScope rates its health at 57/100 (high risk).

What is the latest version of @voyantjs/cruises-contracts?

The latest version of @voyantjs/cruises-contracts is 0.105.2, released 2026-06-11.

Does @voyantjs/cruises-contracts have known vulnerabilities?

No known vulnerabilities on the latest version of @voyantjs/cruises-contracts.

Is @voyantjs/cruises-contracts deprecated?

No, @voyantjs/cruises-contracts is actively maintained. Latest release: 0.105.2 (2026-06-11).

What are alternatives to @voyantjs/cruises-contracts?

Popular alternatives to @voyantjs/cruises-contracts in npm include: ?, semver, minimatch, debug, ansi-styles.

What license does @voyantjs/cruises-contracts use?

@voyantjs/cruises-contracts is licensed under Apache-2.0.

@voyantjs/cruises-contracts

npmv0.105.2

Pure cruise content contracts for adapter implementers and external consumers that need to validate `cruises/v1` rich content payloads without installing the full cruises runtime package.

License Apache-2.0permissive17 versions2 maintainers2 deps7 weekly dl

voyantjs/voyant

/ 100

Health

use with caution

@voyantjs/[email protected] low health (57/100) — consider alternatives

Moderate health score (57/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (2)

zod @voyantjs/catalog-contracts

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@voyantjs/cruises-contracts