Generate or verify a Proof Key for Code Exchange (PKCE) challenge pair
78%
Total Score
50
100
94
80
100
Only one registry account has publish access. This is a modest publishing-resilience concern, though the repository's observed activity is the stronger maintenance evidence.
The repository is owned by an individual user rather than an organization, so the concentrated contributor activity and single registry publisher are not offset by visible organizational backing.
All two recent commits came from one contributor, giving the project a very concentrated recent bus factor and increasing continuity risk if that contributor becomes unavailable.
The repository had only two commits in the last three months from one active maintainer. This shows some ongoing maintenance but a thin and relatively quiet recent activity level.
There are no open issues and six open pull requests, but no issues or pull requests were merged during the last month. The pending pull requests modestly weaken evidence of active responsiveness.
We didn't find any vulnerabilities for this package.
No direct dependencies.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.