Package Health Score

60 / 100

security
Security review needed
popularity
Small
maintenance
Inactive
community
Active

Explore Similar Packages

Security

Security review needed

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

Security and license risk for significant versions

Version			Vulnerabilities	License Risk
1.2.4	\|	07/2021	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.1.3	\|	04/2021	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.0.38	\|	04/2021	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

ISC

Security Policy

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

Small

Weekly Downloads (3)

GitHub Stars: 24.55K
Forks: 3.45K
Contributors: 460

Direct Usage Popularity

The npm package coda-auth receives a total of 3 downloads a week. As such, we scored coda-auth popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package coda-auth, we found that it has been starred 24,553 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: No
Code of Conduct: Yes
Contributors: 460
Funding: Yes

A good and healthy external contribution signal for coda-auth project, which invites more than one hundred open source maintainers to collaborate on the repository.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

Open Issues: 280
Open PR: 91
Last Release: 3 years ago
Last Commit: 26 days ago

Further analysis of the maintenance status of coda-auth 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 coda-auth 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: 4 years
Dependencies: 12 Direct
Versions: 49
Install Size: 297 kB
Dist-tags: 1
# of Files: 98
Maintainers: 1
TS Typings: No

coda-auth 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.

Readme

Next.js + Authentication

WARNING

This does not use dynamic values. This is currently for personal use and has values hardcoded for my setup. You probably should be using npm next-auth instead. Please do use this in anykind of production environment. That being said you can follow through my edits if you want to fork a version for yourself.

Purpose

Fork of npm next-auth which used a runtime environment variable of NEXTAUTH_URL to determine base url of authentication. When using the serverless-next.js Severless Framework Component it will be deployed at Lambda@Edge. This does not allow the use of adding environment variables and thus conflicts with the way next-auth handles routing. This package instead searches the lambda name for occurances of -prod- or -dev- and will pick a static base url from that. Where does it get the static base url? It is hardcoded right now. So, you probably should avoid this package unless you too want to fork and hardcode.

List of Edits

created /dist/config.js
specified a personally used url to become the export when lambda@edge -prod- or -dev- is found in the lambda name
import this config into /dist/client/index.js a. any mentions of process.env.NEXTAUTH_URL will now also search for a url from this config
import this config into /dist/server/index.js a. any mentions of process.env.NEXTAUTH_URL will now also search for a url from this config

Future

This package needs extensive testing and should be made more dynamic. Setting the baseUrl in the options of [...nextauth].js should be possible.

coda-auth dependencies

crypto-js futoin-hkdf jose jsonwebtoken nodemailer oauth pkce-challenge preact preact-render-to-string querystring require_optional typeorm

FAQs

What is coda-auth?

Static Authentication for Next.js. Visit Snyk Advisor to see a full health score report for coda-auth, including popularity, security, maintenance & community analysis.

Is coda-auth popular?

The npm package coda-auth receives a total of 3 weekly downloads. As such, coda-auth popularity was classified as small. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is coda-auth well maintained?

We found indications that coda-auth is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is coda-auth safe to use?

While scanning the latest version of coda-auth, we found that a security review is needed. A total of 0 vulnerabilities or license issues were detected. See the full security scan results.

Last updated on 6 November-2024, at 10:34 (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

coda-auth

Static Authentication for Next.js For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Explore Similar Packages

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (3)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Readme

Next.js + Authentication

WARNING

Purpose

List of Edits

Future

coda-auth dependencies

coda-auth development dependencies

FAQs

What is coda-auth?

Is coda-auth popular?

Is coda-auth well maintained?

Is coda-auth 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

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (3)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

Next.js + Authentication

WARNING

Purpose

List of Edits

Future

coda-auth dependencies

coda-auth development dependencies

FAQs

What is coda-auth?

Is coda-auth popular?

Is coda-auth well maintained?

Is coda-auth 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