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

std-bridge

v0.1.0

Published

Bridge between GitHub Spec Kit and GSD Core - converts tasks.md to .planning/PLAN.md with TDD structure and generates application-specific pentest files

Readme

STD Bridge

Bridge between GitHub Spec Kit and GSD Core — converts tasks.md.planning/PLAN.md with embedded TDD structure and generates application-specific pentest files.

Install

npx std-bridge --init

Or install globally:

npm install -g std-bridge
std-bridge --init

Usage

# Basic (uses default paths)
npx std-bridge

# Custom project path
npx std-bridge ./my-project

# Custom base URL for generated tests
npx std-bridge --base-url https://api.example.com

# Init a new project
npx std-bridge --init
npx std-bridge --init ./my-project

Configuration

After running --init, a .std-bridge.json file is created in your project root:

{
  "baseUrl": "http://localhost:3000"
}

You can also override these paths in .std-bridge.json:

{
  "baseUrl": "https://api.example.com",
  "tasksPath": "docs/specs/tasks.md",
  "specPath": "docs/specs/spec.md",
  "planOut": ".planning/PLAN.md",
  "pentestDir": "tests/security"
}

CLI flags take precedence over the config file:

  • --base-url overrides baseUrl in .std-bridge.json
  • First positional arg sets the project directory

What it does

  1. Reads docs/specs/tasks.md (from SpecKit)
  2. Reads docs/specs/spec.md (from SpecKit)
  3. Generates .planning/PLAN.md with TDD Red/Green/Refactor/Pentest per task
  4. Generates tests/security/ with application-specific pentest files:
    • tests/security/api/*.spec.js — endpoint pentests (SQLi, IDOR, rate limit)
    • tests/security/auth/*.spec.js — auth pentests (JWT tampering, brute force)
    • tests/security/business-logic/*.spec.js — rule pentests (race, overflow)
    • tests/security/data/*.spec.js — data pentests (leakage, mass assignment)

Integration

Works as a hook between /speckit.tasks and /gsd-execute-phase:

/speckit.specify → /speckit.plan → /speckit.tasks
                                         ↓
                               npx std-bridge
                                         ↓
                              /gsd-execute-phase

Security

Each generated pentest targets specific endpoints, models, auth flows, and business rules from your spec — not generic tests.