npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

degen-auth

v0.30.1

Published

Authentication plugin for offchain signature validation of web3 accounts

Downloads

4

Readme

Degen Auth

Authentication library for web3 enabled applications

How to Use

  1. When a user requests to sign in via web3 with a particular publicAddress, a request is made to your backend which then will call AuthTools.upsertNewChallengeForAccount(publicAddress,serviceName) where serviceName is the name of your Dapp service.
  1. This returns a challenge phrase ['Signing in to SERVICE_NAME as PUBLIC_ADDRESS at UNIXTIME'] which your backend will pass back to the frontend in that same call. The frontend will make metamask request a PersonalSign with that challenge as the message and await the users signature.

  2. Once the user signs in metamask, that signature and the users publicAddress will be the input for a request to your backend which calls AuthTools.generateAuthenticatedSession(publicAddress, signature). This will return an authentication token (random hex string) which will be passed back to the user and will be stored in their localStorage, valid for up to 24 hours. This authentication token is also stored in your mongoDatabase so you can make checks against it.

  3. This user can now use this authentication token for your other api requests . These can require than the authentication token be given to prove that the user has, in the recent past, proven that they know the private key for that public address.

Code Example

import {AuthTools} from 'degen-auth'

let degenAuthInterface = await AuthTools.initializeDatabase()

let challenge = await AuthTools.upsertNewChallengeForAccount(degenAuthInterface,publicAddress, serviceName)

// personal sign challenge in metamask

let signature = userWallet.sign(challenge)

let authtoken = await AuthTools.generateAuthenticatedSession(degenAuthInterface,publicAddress, signature)

//give the authtoken to the user so they store it in their LocalStorage to use for authenticated API requests