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

@olydi/cli

v0.1.1

Published

OLYDI DevSecOps CLI — scan your code from the terminal

Downloads

19

Readme

@olydi/cli

OLYDI DevSecOps CLI — scan your code from the terminal.

Install

# npm (global)
npm install -g @olydi/cli

# npx (no install)
npx @olydi/cli scan --wait

# From source
git clone https://github.com/olydi/autonomous-workflow-harness
cd autonomous-workflow-harness/cli && npm link

Requires Node.js 18+ (uses built-in fetch). Zero npm dependencies.

Quick Start

# 1. Authenticate with your API key
olydi login --token olydi_sk_your_key_here

# 2. Run a scan (auto-detects repo from git remote)
olydi scan --wait

# 3. View findings
olydi findings --severity critical,high

# 4. Auto-fix critical findings
olydi fix --severity critical

Commands

olydi scan

Trigger a security scan on your repository.

olydi scan                           # queue scan, exit immediately
olydi scan --wait                    # wait for scan to complete
olydi scan --repo owner/repo --wait  # explicit repo
olydi scan --format json             # machine-readable output

Options:

| Flag | Description | |------|-------------| | --repo <owner/repo> | Target repository. Auto-detected from git remote if omitted. | | --wait | Poll until the scan completes, then print the findings summary. | | --sarif <path> | Write findings as SARIF 2.1.0 to <path>. Implies --wait. | | --fail-on <level> | Exit 1 if findings at/above this severity exist. Implies --wait. | | --format text\|json | Output format. Default: text. |

olydi findings

List findings from your latest scan.

olydi findings                          # all findings
olydi findings --severity critical      # critical only
olydi findings --severity critical,high # critical + high
olydi findings --gate secrets           # filter by gate
olydi findings --format json            # JSON output for scripting

Options:

| Flag | Description | |------|-------------| | --severity <level> | Filter by severity. Comma-separated: critical,high,medium,low. | | --gate <name> | Filter by security gate. Comma-separated. | | --limit <n> | Max findings to return. Default: 50. | | --format text\|json | Output format. Default: text. |

olydi fix

Request auto-remediation for findings.

olydi fix --severity critical           # fix all critical findings
olydi fix --finding fp_a1b2c3d4         # fix a specific finding
olydi fix --finding fp_abc,fp_def       # fix multiple findings

Options:

| Flag | Description | |------|-------------| | --severity <level> | Fix all findings at this severity level. | | --finding <id> | Fix specific finding(s) by ID. Comma-separated. | | --format text\|json | Output format. Default: text. |

olydi login

Authenticate with OLYDI.

olydi login --token olydi_sk_your_key_here
olydi login --token $OLYDI_TOKEN --api-url https://custom.api.example.com

Credentials are saved to ~/.config/olydi/credentials.json (mode 0600).

Options:

| Flag | Description | |------|-------------| | --token <api-key> | API key for authentication. Generate at app.olydi.com/settings/api-keys. | | --api-url <url> | Override the API base URL. |

olydi status

Show current authentication and repository context.

olydi status

Authentication

The CLI resolves auth tokens in this order:

  1. --token flag (highest priority)
  2. OLYDI_TOKEN environment variable
  3. ~/.config/olydi/credentials.json file

CI/CD Usage

Set the OLYDI_TOKEN environment variable in your CI pipeline:

# GitHub Actions
- name: OLYDI Scan
  env:
    OLYDI_TOKEN: ${{ secrets.OLYDI_TOKEN }}
  run: npx @olydi/cli scan --wait --format json
# GitLab CI
olydi-scan:
  script:
    - npx @olydi/cli scan --wait --format json
  variables:
    OLYDI_TOKEN: $OLYDI_TOKEN

JSON Output

All commands support --format json for scripting and CI integration:

# Scan and capture run ID
RUN_ID=$(olydi scan --format json | jq -r '.run_id')

# Get critical findings as JSON
olydi findings --severity critical --format json | jq '.items[]'

# Count findings by severity
olydi findings --format json | jq '.total'

Environment Variables

| Variable | Description | |----------|-------------| | OLYDI_TOKEN | API authentication token | | OLYDI_API_URL | Override the API base URL (default: https://api.olydi.com) | | VALTY_URL | Override the API base URL. Takes priority over OLYDI_API_URL (and the saved api_url). Opt-in only — unset by default, so behavior is unchanged unless set explicitly. | | NO_COLOR | Disable colored output (no-color.org) |

License

Apache-2.0