Is @hypertune/openfeature-base-provider safe to use?

@hypertune/openfeature-base-provider has no known vulnerabilities on the latest version (0.1.2). DepScope rates its health at 40/100 (high risk).

What is the latest version of @hypertune/openfeature-base-provider?

The latest version of @hypertune/openfeature-base-provider is 0.1.2, released 2024-08-16.

Does @hypertune/openfeature-base-provider have known vulnerabilities?

No known vulnerabilities on the latest version of @hypertune/openfeature-base-provider.

Is @hypertune/openfeature-base-provider deprecated?

No, @hypertune/openfeature-base-provider is actively maintained. Latest release: 0.1.2 (2024-08-16).

What are alternatives to @hypertune/openfeature-base-provider?

Popular alternatives to @hypertune/openfeature-base-provider in npm include: semver, debug, ansi-styles, minimatch, strip-ansi.

What license does @hypertune/openfeature-base-provider use?

@hypertune/openfeature-base-provider is licensed under Apache-2.0.

@hypertune/openfeature-base-provider

npmv0.1.2

OpenFeature provider for Hypertune.

License Apache-2.0permissive8 versions3 maintainers2 deps

hypertunehq/openfeature-provider-js

/ 100

Health

safe to use

@hypertune/[email protected] is safe to use (health: 40/100)

Health breakdown0 – 100

5/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (2)

@openfeature/core hypertune

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@hypertune/openfeature-base-provider