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

@continuous-auth/client

v2.3.2

Published

Node.JS Client for the CFA service

Downloads

2,052

Readme

@continuous-auth/client

GitHub Workflow Status GitHub Workflow Status npm version

This module expects to be run in a Supported CI Environment. It infers a lot of variables from environment variables, these config variables are outlined below.

Config

  • CFA_PROJECT_ID - The ID of your project on CFA
  • CFA_SECRET - The secret assoicated with your project on CFA, you get this from the CFA Dashboard

API

getOtp()

Returns Promise<string>.

This promise eventually resolves with a valid OTP code, please be aware that this code is user provided and therefore may have been entered incorrectly. You also need to use OTP codes quite quickly as they typically expire within 30 seconds.

validateConfiguration()

Returns Promise<void>.

This promise will resolve if your project ID and secret are a valid combination for the current CI provider. It will be rejected if they are deemed invalid by the CFA service.

Example

// Publish the package in the CWD with an OTP code from CFA
import { getOtp } from '@continuous-auth/client';
import { spawnSync } from 'child_process';

spawnSync('npm', ['publish', '--otp', await getOtp()])