pkce-challenge

v4.1.0

Generate or verify a Proof Key for Code Exchange (PKCE) challenge pair For more information about how to use this package see README

Latest version published 3 months ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

72 / 100

Security

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

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
4.1.0 | 01/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.0.1 | 05/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.1.0 | 03/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.2.0 | 05/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.1.0 | 12/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

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

Popular

Weekly Downloads (131,805)

Download trend
GitHub Stars
62
Forks
12
Contributors
8

Direct Usage Popularity

TOP 5%

The npm package pkce-challenge receives a total of 131,805 downloads a week. As such, we scored pkce-challenge popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package pkce-challenge, we found that it has been starred 62 times.

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

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
8
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like pkce-challenge is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 72/100 package health 72/100

Maintenance

Sustainable

Commit Frequency

Open Issues
0
Open PR
0
Last Release
3 months ago
Last Commit
3 months ago

Further analysis of the maintenance status of pkce-challenge based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that pkce-challenge demonstrates a positive version release cadence with at least one new version released in the past 12 months.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
>=16.20.0

Age
5 years
Dependencies
0 Direct
Versions
13
Install Size
10.5 kB
Dist-tags
1
# of Files
7
Maintainers
1
TS Typings
Yes

pkce-challenge 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.