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

spectra-crypto-cli

v2.0.0

Published

Cryptographic Intelligence Platform & PQC Migration Engine CLI

Readme

Spectra

Build Status Go Version License: MIT CycloneDX 1.7

Quick Start

Install via NPM

npm install -g spectra-crypto-cli

Usage

# Basic terminal scan of current directory
spectra scan .

# Scan an OCI Container Image
spectra scan --image alpine:latest

# Scan a TLS Endpoint
spectra scan --url example.com:443

# Start the interactive web dashboard
spectra dashboard

Output Formats

Terminal Output

Spectra provides a rich, ANSI-colored terminal UI showing findings, aggregate risks, and a prioritized action plan.

CBOM Output

Generates CycloneDX formatted Cryptographic Bill of Materials.

{
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "version": 1,
  "components": [
    {
      "type": "cryptographic-asset",
      "name": "RSA",
      "version": "2048",
      "description": "RSA (2048-bit)",
      "properties": [
        { "name": "spectra:qrs", "value": "50" }
      ]
    }
  ]
}

Quantum Risk Score (QRS)

Spectra evaluates algorithms using a proprietary 0-100 scoring model:

| Score Range | Risk Band | Meaning | | :--- | :--- | :--- | | 80-100 | CRITICAL | Broken algorithm (MD5) or highly vulnerable to Shor's algorithm | | 60-79 | HIGH | Weak algorithm (SHA1, RSA-1024) | | 40-59 | MEDIUM | Acceptable for now, but not quantum-safe (RSA-2048) | | 20-39 | LOW | Strong algorithm (AES-256, SHA-3) | | 0-19 | SAFE | Post-Quantum Cryptography (ML-KEM, ML-DSA) |

CLI Reference

| Command | Description | Example | | :--- | :--- | :--- | | spectra scan [dir] | Scans a directory | spectra scan ./src | | spectra scan --image | Scans a container image | spectra scan --image ubuntu:latest | | spectra scan --url | Scans a TLS endpoint | spectra scan --url google.com:443 | | spectra dashboard | Starts the embedded Web Dashboard | spectra dashboard --port 8080 | | spectra diff | Compares two CBOMs to track progress | spectra diff old.json new.json | | spectra version | Displays the current version | spectra version |

Roadmap

  • [x] Phase 1: MVP Core Scanners
  • [x] Phase 2: Git Blame Integration, TLS Scanning, Container Scanning, Web Dashboard
  • [ ] Phase 3: Advanced CI/CD integrations and API Server

Contributing

Contributions are welcome! Please open an issue before submitting a large PR. Ensure you run go test ./... and golangci-lint before committing.