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

@beyondthecloud/sf-veles

v0.1.2

Published

SF CLI plugin for Veles — set up Veles on existing scratch orgs and sandboxes and connect them to your Veles Hub

Readme

@beyondthecloud/sf-veles

SF CLI plugin for Veles — set up Veles on an existing scratch org or sandbox and connect it to your Veles Hub.

Installation

sf plugins install @beyondthecloud/sf-veles

Usage

Note: This command does not create scratch orgs or sandboxes. The target org must already exist and be authorized with the Salesforce CLI before running sf veles setup. For sandboxes, an Environment__c record for that sandbox must also already exist on the Hub.

sf veles setup --target-org <scratch-or-sandbox> [--target-dev-hub <hub>] [--group <name>] [--installation-key <key>]

What it does

  1. Provisions the org on your Veles Hub (creates Environment record + connection token)
  2. Installs the Veles managed package (if not already present)
  3. Deploys Remote Site Settings for Hub communication
  4. Configures the connection metadata
  5. Connects the org to the Hub

Examples

# Set up Veles on an existing scratch org (uses default DevHub)
sf veles setup --target-org my-scratch

# Set up Veles on an existing scratch org with explicit DevHub and group
sf veles setup --target-org my-scratch --target-dev-hub my-hub --group MyGroup

# Set up Veles on an existing sandbox with explicit Hub
sf veles setup --target-org my-sandbox --target-dev-hub my-hub

# With package installation key
sf veles setup --target-org my-scratch --installation-key MyKey123

Flags

| Flag | Alias | Required | Description | | -------------------- | ----- | -------- | --------------------------------------------------------------- | | --target-org | -o | Yes | Already-created and authorized scratch org or sandbox to set up | | --target-dev-hub | -v | No | Hub/DevHub org (defaults to SF CLI default) | | --group | -g | No | Environment group name on the Hub | | --installation-key | -k | No | Installation key for the Veles package |

Prerequisites

  • The target org must already be created and authorized via the Salesforce CLI. This command does not create scratch orgs or sandboxes.
  • Salesforce CLI installed
  • Veles managed package installed on your Hub org
  • Authenticated to both the target org and Hub/DevHub
  • For sandboxes: an Environment__c record for the sandbox must already exist on the Hub

License

MIT