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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@assisisolutions/sfdx-ci-plugin

v1.0.1

Published

SFDX plugin to set up a connected app usable for continuous integration with "one click"

Readme

sfdx-ci-plugin

SFDX plugin to set up a connected app usable for continuous integration with "one click".

This plugin simplifies the process of creating a connected app that you can use with sfdx auth:jwt:grant to non-interactively connect SFDX to a sandbox or production org so that you can deploy your SFDX project. It:

  • creates an RSA private key and an X.509 certificate
  • creates a permission set that controls access to the connected app
  • creates the connected app and configures it with the X.509 certificate for digital signatures and connects it to the permission set

After this, you can connect to the org with a single command:

sfdx auth:jwt:grant -u [email protected] -f privkey.pem -i <OAuth client id>

Version Codecov Known Vulnerabilities Downloads/week License

$ npm install -g @assisisolutions/sfdx-ci-plugin
$ sfdx COMMAND
running command...
$ sfdx (-v|--version|version)
@assisisolutions/sfdx-ci-plugin/1.0.1 darwin-x64 node-v15.4.0
$ sfdx --help [COMMAND]
USAGE
  $ sfdx COMMAND
...

sfdx ci:setup [-n <string>] [-p <string>] [-f] [-c <filepath>] [-d <directory>] [-u <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

Sets up an org as the target of a continuous integration pipeline

Sets up an org as the target of a continuous integration pipeline

USAGE
  $ sfdx ci:setup [-n <string>] [-p <string>] [-f] [-c <filepath>] [-d <directory>] [-u <string>] [--apiversion 
  <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

OPTIONS
  -c, --certfile=certfile
      path to the X.509 certificate to configure the connected app to use for authentication

  -d, --outputdir=outputdir
      [default: .] path to which the X.509 certificate and private key file will be written

  -f, --force
      overwrite an existing connected app

  -n, --name=name
      [default: Continuous Integration] name of the connected app to create

  -p, --permissionsetname=permissionsetname
      name of the permission set that will determine which users have access to the connected app. If not provided, the 
      permission set will have the same name as the connected app. In either case, the permission set is created if it 
      doesn't exist yet.

  -u, --targetusername=targetusername
      username or alias for the target org; overrides default target org

  --apiversion=apiversion
      override the api version used for api requests made by this command

  --json
      format output as json

  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)
      [default: warn] logging level for this command invocation

EXAMPLES
  $ sfdx ci:setup --targetusername [email protected] --name "Continuous Integration App" --permissionsetname "Admin 
  Access"
  $ sfdx ci:setup --targetusername [email protected] --certfile mycert.pem

See code: lib/commands/ci/setup.js