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

vector-hub-cli

v1.3.0

Published

CLI for Vector Technologies

Readme

Vector CLI

Vector CLI is an advanced command-line interface developed by Vector Technologies, designed to empower users with seamless model deployment and management capabilities directly from their terminal. With Vector CLI, users can efficiently interact with Vector’s robust platform to handle tasks such as model deployment, configuration, version control, and real-time monitoring, all within a streamlined command-line experience. This tool is ideal for developers, data scientists, and engineers who require a high level of control and integration for managing machine learning models in a fast, intuitive way.

Installation

To install the CLI, use npm:

npm i vector-hub-cli

Table of Contents

Quick Start

Once installed, try running your first command to see a list of all available options:

vector --help

Commands Overview

  • A list of available commands, with a brief description of each. This can serve as a quick reference.

  • deploy - Deploys a model at the specified path.

  • list - Lists all deployed models in the current environment.

  • delete - Deletes a model based on its unique ID.

  • status - Displays the deployment status of a specific model.

  • logs - Fetches and displays the logs for a model.

Detailed Commands

Deploy

Deploy a model to Vector's platform.

Usage:

vector deploy <modelPath> [--name <name>] [--version <version>]
  • name : Optional custom name for the deployment.
  • version : Specify a version number if deploying multiple versions

List

Lists all models currently deployed.

Usage:

vector list [--verbose]

Configuration

Details on any configuration files or environment variables required for custom setups.

Vector CLI requires a configuration file, vector.config.json, to manage deployments and other settings.

Sample vector.config.json file:

{
    "api_key": "your_api_key_here",
    "project_id": "your_project_id_here",
    "default_env": "production"
}

Error Handling

  • Information on common errors, possible causes, and solutions.

If you encounter issues, refer to the error codes below:

  • Error Code 101: "Model path not found" - Verify the specified model path exists.
  • Error Code 403: "Unauthorized Access" - Ensure your API key is valid and has the necessary permissions.

Examples

Deploying a New Model Version

vector deploy ./models/updated_model --version "2.0" --name "UpdatedSentimentModel"

Checking Model Status

vector status 12345  # where 12345 is the model ID

Troubleshooting

A guide for solving common installation, configuration, and usage issues.

CLI Not Recognized

  • Ensure vector is globally accessible by verifying its installation location or reinstalling with npm install -g.

Permission Issues

  • If permission errors occur, try running with sudo, or ensure your vector.config.json has the correct API keys.

Contributing

Contributions are welcome! Please see the CONTRIBUTING.md file for guidelines.