Is @jfront/oauth-context safe to use?

@jfront/oauth-context has no known vulnerabilities on the latest version (0.3.0). DepScope rates its health at 42/100 (high risk).

What is the latest version of @jfront/oauth-context?

The latest version of @jfront/oauth-context is 0.3.0, released 2023-07-30.

Does @jfront/oauth-context have known vulnerabilities?

No known vulnerabilities on the latest version of @jfront/oauth-context.

Is @jfront/oauth-context deprecated?

No, @jfront/oauth-context is actively maintained. Latest release: 0.3.0 (2023-07-30).

What are alternatives to @jfront/oauth-context?

Popular alternatives to @jfront/oauth-context in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @jfront/oauth-context use?

@jfront/oauth-context is licensed under Apache-2.0.

@jfront/oauth-context

npmv0.3.0

React Context API OAuth 2.0 authorization management.

License Apache-2.0permissive14 versions5 maintainers1 deps33 weekly dl

Jepria/jfront-oauth

/ 100

Health

use with caution

@jfront/[email protected] low health (42/100) — consider alternatives

Moderate health score (42/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

5/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (1)

@jfront/oauth-core

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@jfront/oauth-context