Is @qdrant/openapi-typescript-fetch safe to use?

@qdrant/openapi-typescript-fetch has no known vulnerabilities on the latest version (1.2.6). DepScope rates its health at 34/100 (critical risk).

What is the latest version of @qdrant/openapi-typescript-fetch?

The latest version of @qdrant/openapi-typescript-fetch is 1.2.6, released 2024-03-04.

Does @qdrant/openapi-typescript-fetch have known vulnerabilities?

No known vulnerabilities on the latest version of @qdrant/openapi-typescript-fetch.

Is @qdrant/openapi-typescript-fetch deprecated?

No, @qdrant/openapi-typescript-fetch is actively maintained. Latest release: 1.2.6 (2024-03-04).

What are alternatives to @qdrant/openapi-typescript-fetch?

Popular alternatives to @qdrant/openapi-typescript-fetch in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does @qdrant/openapi-typescript-fetch use?

@qdrant/openapi-typescript-fetch is licensed under MIT.

@qdrant/openapi-typescript-fetch

npmv1.2.6

A typed fetch client for openapi-typescript

License MITpermissive7 versions2 maintainers0 deps

qdrant/openapi-typescript-fetch

/ 100

Health

use with caution

@qdrant/[email protected] low health (34/100) — consider alternatives

Low health score (34/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@qdrant/openapi-typescript-fetch