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

@squadzero/veil

v0.6.4

Published

A TypeScript library for selective context access, visibility control & safety enforcement for LLMs

Readme

Veil 🎭

LLM visibility firewall - Control what AI can access in your project.

npm TypeScript License: MIT

What It Does

  • 🛡️ Block dangerous commands - Prevent rm -rf /, wrangler deploy, etc.
  • 🔒 Protect secrets - Mask or deny access to API keys and tokens
  • 📁 Hide sensitive files - Block reading/writing .env, secrets/, etc.
  • 📝 Audit logging - Track all AI command attempts for review
  • 💡 Guide the AI - Provide safe alternatives when blocking

Quick Start

1. Install

npm install -g @squadzero/veil
veil install
source ~/.zshrc

2. Add VS Code Settings

{
  "terminal.integrated.env.linux": { "VEIL_ENABLED": "1" },
  "terminal.integrated.env.osx": { "VEIL_ENABLED": "1" }
}

3. Create Rules

// veil.config.ts
export default {
  cliRules: [
    {
      match: /^wrangler\s+deploy/,
      action: 'deny',
      reason: 'Use npm run deploy:stage instead',
      safeAlternatives: ['npm run deploy:stage']
    }
  ]
};

4. Test It

# Human terminal (outside VS Code) - passes through
wrangler deploy  # ✅ Works

# AI terminal (in VS Code) - blocked
wrangler deploy  # 🛡️ Blocked with alternatives

MCP Integration

Add to .vscode/mcp.json for AI tool call interception:

{
  "servers": {
    "veil": {
      "type": "stdio",
      "command": "npx",
      "args": ["@squadzero/veil", "mcp"],
      "cwd": "/path/to/workspace"
    }
  }
}

Dynamic Config Loading

Veil automatically loads project-specific rules based on the working directory:

  • When cwd is passed to a tool, Veil walks up from that directory to find veil.config.ts
  • For file operations, rules are loaded from the file's parent directory
  • Each project in a poly-repo can have its own veil.config.ts
/workspace
├── .vscode/mcp.json          # Single MCP config
├── project-a/
│   └── veil.config.ts        # Rules for project-a
└── project-b/
    └── veil.config.ts        # Rules for project-b

MCP Tools

| Tool | Description | | --------------- | ------------------------------------- | | run_command | Execute commands with Veil validation | | check_command | Pre-flight check without executing | | get_env | Get env vars with masking/blocking | | check_env | Check if env var is accessible | | check_file | Check if file access is allowed | | read_file | Read files with Veil validation | | write_file | Write files with Veil validation | | get_audit_log | View audit trail of all operations |

Most tools accept an optional cwd parameter to specify which project's rules to use.

Audit Logging

Set environment variables to configure audit logging:

VEIL_AUDIT_LOG=.veil/audit.log  # Log file path (default)
VEIL_AUDIT_FORMAT=text          # 'text' or 'json'

CLI Commands

| Command | Description | | ---------------------- | -------------------------------------- | | veil install | Add shell wrapper (AI-only by default) | | veil install --force | Protect ALL terminals | | veil uninstall | Remove shell wrapper | | veil init | Create config with preset | | veil check <target> | Test if something is blocked | | veil mcp | Start MCP server |


Documentation

| Guide | Description | | ---------------------------------------------- | ---------------------------------- | | Setup Guide | Complete installation instructions | | CLI Reference | All commands and options | | API Reference | TypeScript API docs | | Presets & Rules | Rule configuration |


How It Works

Human Terminal          VS Code Terminal (AI)
      │                        │
      ▼                        ▼
  wrangler deploy         wrangler deploy
      │                        │
      │                  VEIL_ENABLED=1
      │                        │
      ▼                        ▼
  ✅ Executes            🛡️ veil-wrap
                               │
                               ▼
                         veil.config.ts
                               │
                    ┌──────────┴──────────┐
                    │                     │
                    ▼                     ▼
               ✅ Allowed            ❌ Blocked
                    │                     │
                    ▼                     ▼
                Executes         Shows alternatives

License

MIT © Squad-Zero