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

@sphior/scan

v0.1.1

Published

Deterministic source scanner — hardcoded secrets and insecure patterns (CWE) with AST/taint analysis. No AI, no network, no source upload. CLI + LSP for editors and CI.

Readme

@sphior/scan

Deterministic security scanner for source code — hardcoded secrets and insecure patterns (CWE) — with no AI, no network and no source upload.

Detection is 100% deterministic (regex + entropy + AST/taint analysis), so the same code always produces the same findings. The scan makes no network requests at all: your source never leaves the machine it runs on, and it works offline.

npx @sphior/scan run ./src

Install

# one-off
npx @sphior/scan run ./src

# or install globally
npm install -g @sphior/scan
sphior-scan run ./src

Requires Node.js 18 or newer.

Usage

sphior-scan run <dir> [options]

Options:
  --sarif <file>         write SARIF 2.1.0 (GitHub code scanning, most CI tools)
  --json <file>          write raw findings as JSON
  --fix-context <file>   write finding context for an AI assistant to act on
  --fail-on <severity>   exit non-zero at or above this severity
                         (critical | high | medium | low)

SARIF is written to stdout as well, so it pipes cleanly:

sphior-scan run ./src --fail-on high

Exit code is 0 when nothing at or above --fail-on was found, non-zero otherwise — which is what you want in CI.

GitHub Actions

- run: npx @sphior/scan run . --sarif results.sarif --fail-on high
- uses: github/codeql-action/upload-sarif@v3
  if: always()
  with:
    sarif_file: results.sarif

What it detects

| Category | How | |---|---| | Hardcoded secrets | Provider-specific patterns + entropy analysis. Well-known documentation placeholders are excluded, so example keys don't create noise. | | Insecure patterns (CWE) | AST-based, including taint tracking from untrusted sources to dangerous sinks (SQL injection, XSS, command injection and similar). |

Dependency (SCA) scanning is not part of this CLI. The engine accepts SCA input, but the run command only analyses source files. Dependency vulnerabilities are surfaced by SPHIOR CODE on GitHub, which resolves lockfiles against the OSV database.

Findings carry a rule id, severity, CWE where applicable, and the exact file and line.

Language server

The package also ships a Language Server Protocol server, so editors can show findings inline while you type:

node node_modules/@sphior/scan/dist/server.cjs --stdio

The SPHIOR CODE extensions for VS Code and JetBrains connect to this server. Everything is analysed locally — nothing is sent anywhere.

Privacy

The scanner reads your files and reports what it found. It makes no network requests: no source upload, no telemetry, no language model, no account. It runs correctly with networking disabled.

Links

License

MIT — see LICENSE.