Package Health Score

67 / 100

security
No known security issues
popularity
Limited
maintenance
Inactive
community
Active

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
3.1.7	\|	06/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.1.6	\|	10/2020	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.0.8	\|	02/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.0.8	\|	08/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.3.3	\|	04/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Limited

Weekly Downloads (116)

GitHub Stars: 550
Forks: 147
Contributors: 60

Direct Usage Popularity

The npm package @axa-fr/react-oidc-fetch-core receives a total of 116 downloads a week. As such, we scored @axa-fr/react-oidc-fetch-core popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package @axa-fr/react-oidc-fetch-core, we found that it has been starred 550 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 60
Funding: No

With more than 10 contributors for the @axa-fr/react-oidc-fetch-core repository, this is possibly a sign for a growing and inviting community.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

Open Issues: 78
Open PR: 12
Last Release: 3 years ago
Last Commit: 15 days ago

Further analysis of the maintenance status of @axa-fr/react-oidc-fetch-core based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for @axa-fr/react-oidc-fetch-core is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 6 years
Dependencies: 1 Direct
Versions: 52
Install Size: 33.5 kB
Dist-tags: 1
# of Files: 25
Maintainers: 6
TS Typings: No

@axa-fr/react-oidc-fetch-core has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Not sure how to use @axa-fr/react-oidc-fetch-core?

To help you get started, we've collected the most common ways that @axa-fr/react-oidc-fetch-core is being used within popular public projects.

AxaGuilDEv / react-oidc / packages / context-fetch / src / withAuthentication.js View on Github

const enhance = fetch =>
  compose(
    withFetchToken(fetch),
    withFetchSilentAuthenticateAndRetryOn401(),
    withFetchRedirectionOn403()
  );

View more ways to use @axa-fr/react-oidc-fetch-core

@axa-fr/oidc-client

Sample React Oicd

About
Getting Started
Run The Demos
How It Works
Packages
- @axa-fr/oidc-client
- @axa-fr/react-oidc
- @axa-fr/svelte-oidc : we are looking for contributor
- @axa-fr/vue-oidc : we are looking for contributor
- @axa-fr/angular-oidc : we are looking for contributor
FAQ
Migrations
Contribute

About

@axa-fr/oidc-client the lightest and securest library to manage authentication with OpenID Connect (OIDC) and OAuth2 protocol. It is compatible with all OIDC providers. @axa-fr/oidc-client is a pure javascript library. It works with any JavaScript framework or library. @axa-fr/react-oidc is for React (compatible next.js, etc.), we expect soon to provide one for Vue, Angular and Svelte.

Demos:

Try the react demo at https://black-rock-0dc6b0d03.1.azurestaticapps.net/ (most advanced)
Try the pure javascript demo at https://icy-glacier-004ab4303.2.azurestaticapps.net/

@axa-fr/oidc-client is:

Secure :
- With Demonstrating Proof of Possession (DPoP), your access_token and refresh_token are not usable outside your browser context (big protection)
- With the use of Service Worker, your tokens (refresh_token and/or access_token) are not accessible to the JavaScript client code (if you follow good practices from FAQ section)
- OIDC using client side Code Credential Grant with pkce only
Lightweight : Unpacked Size on npm is 274 kB
Simple
- refresh_token and access_token are auto refreshed in background
- with the use of the Service Worker, you do not need to inject the access_token in every fetch, you have only to configure OidcTrustedDomains.js file
Multiple Authentication :
- You can authenticate many times to the same provider with different scope (for example you can acquire a new 'payment' scope for a payment)
- You can authenticate to multiple different providers inside the same SPA (single page application) website
Flexible :
- Work with Service Worker (more secure) and without for older browser (less secure).
- You can disable Service Worker if you want (but less secure) and just use SessionStorage or LocalStorage mode.

Works perfectly well with:

Auth0
Duende Identity Server
Azure AD
Google
AWS
Keycloak
etc., all OIDC providers

Getting Started

Getting Started with @axa-fr/oidc-client

npm install @axa-fr/oidc-client --save

# To install or update OidcServiceWorker.js file, you can run
node ./node_modules/@axa-fr/oidc-client/bin/copy-service-worker-files.mjs public

# If you have a "public" folder, the 2 files will be created :
# ./public/OidcServiceWorker.js &lt;-- will be updated at each "npm install"
# ./public/OidcTrustedDomains.js &lt;-- won't be updated if already exist

WARNING : If you use Service Worker mode, the OidcServiceWorker.js file should always be up to date with the version of the library. You may setup a postinstall script in your package.json file to update it at each npm install. For example :

  "scripts": {
    ...
    "postinstall": "node ./node_modules/@axa-fr/oidc-client/bin/copy-service-worker-files.mjs public"
  },

Getting Started with @axa-fr/react-oidc

npm install @axa-fr/react-oidc --save

# To install or update OidcServiceWorker.js file, you can run
node ./node_modules/@axa-fr/react-oidc/bin/copy-service-worker-files.mjs public

# If you have a "public" folder, the 2 files will be created :
# ./public/OidcServiceWorker.js &lt;-- will be updated at each "npm install"
# ./public/OidcTrustedDomains.js &lt;-- won't be updated if already exist

  "scripts": {
    ...
    "postinstall": "node ./node_modules/@axa-fr/react-oidc/bin/copy-service-worker-files.mjs public"
  },

Run The Demos

git clone https://github.com/AxaFrance/oidc-client.git

cd oidc-client
pnpm install

# oidc client demo
cd examples/oidc-client-demo
pnpm install
pnpm start
# then navigate to https://localhost:5174

# react vite demo
cd examples/react-oidc-demo
pnpm install
pnpm start
# then navigate to https://localhost:4200

# react NextJS demo
cd examples/nextjs-demo
pnpm install
pnpm run dev
# then navigate to https://localhost:3001

How It Works

Schema Authorization Code Grant with pcke flow on the using service worker
The service worker catch access_token and refresh_token that will never be accessible to the client.

These components encapsulate the use of "@axa-fr/oidc-client" in order to hide workflow complexity. Internally for "@axa-fr/react-oidc", native History API is used to be router library agnostic.

More information about OIDC :

FAQ

Frequented Asked Question FAQ

Migrations

Migrating from v3 to v4 guide
Migrating from v3 to v5 guide
Migrating from v4 to v5 guide
Migrating from v5 to v6 guide
Migrating from v6 to v7 guide

Contribute

@axa-fr/react-oidc-fetch-core dependencies

@axa-fr/react-oidc-core

FAQs

What is @axa-fr/react-oidc-fetch-core?

. Visit Snyk Advisor to see a full health score report for @axa-fr/react-oidc-fetch-core, including popularity, security, maintenance & community analysis.

Is @axa-fr/react-oidc-fetch-core popular?

The npm package @axa-fr/react-oidc-fetch-core receives a total of 116 weekly downloads. As such, @axa-fr/react-oidc-fetch-core popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @axa-fr/react-oidc-fetch-core well maintained?

We found indications that @axa-fr/react-oidc-fetch-core is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is @axa-fr/react-oidc-fetch-core safe to use?

The npm package @axa-fr/react-oidc-fetch-core was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 5 May-2024, at 16:17 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

@axa-fr/react-oidc-fetch-core

undefined For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (116)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Not sure how to use @axa-fr/react-oidc-fetch-core?

@axa-fr/oidc-client

About

Getting Started

Getting Started with @axa-fr/oidc-client

Getting Started with @axa-fr/react-oidc

Run The Demos

How It Works

FAQ

Migrations

Contribute

@axa-fr/react-oidc-fetch-core dependencies

FAQs

What is @axa-fr/react-oidc-fetch-core?

Is @axa-fr/react-oidc-fetch-core popular?

Is @axa-fr/react-oidc-fetch-core well maintained?

Is @axa-fr/react-oidc-fetch-core safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (116)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use @axa-fr/react-oidc-fetch-core?

@axa-fr/oidc-client

About

Getting Started

Getting Started with @axa-fr/oidc-client

Getting Started with @axa-fr/react-oidc

Run The Demos

How It Works

FAQ

Migrations

Contribute

@axa-fr/react-oidc-fetch-core dependencies

FAQs

What is @axa-fr/react-oidc-fetch-core?

Is @axa-fr/react-oidc-fetch-core popular?

Is @axa-fr/react-oidc-fetch-core well maintained?

Is @axa-fr/react-oidc-fetch-core safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues