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

@securityreviewai/vibereview

v0.2.5

Published

Bootstrap the VibeReview MCP server and workspace rules / skills / hooks for AI IDEs.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

haricharanaharicharanaabhaysecrevabhaysecrev

Keywords

vibereviewmcpsecurity-reviewai-idecursorclaudecodexgeminiwindsurfvscode

Readme

VibeReview Kit

Bootstrap VibeReview MCP configuration, workspace rules, skills, and hooks for AI IDEs.

Usage

Run this inside the repository/workspace you open in your IDE:

npx -y @securityreviewai/vibereview@latest init

Follow the prompts for:

  • VibeReview MCP server URL
  • VibeReview API URL
  • VibeReview API key
  • Project selection
  • IDE target

The CLI writes only the files required for the selected IDE. Server-side repository profiling and guardrail selection are handled by VibeReview.

Skills

init stamps the VibeReview security workflow into each target's skill directory (e.g. .cursor/skills/, .claude/skills/, .github/skills/, .codex/skills/, .factory/skills/). The skills run as a hard pre-write gate for any security-relevant coding task, in this order:

  1. guardrails-selection — shortlist the relevant project guardrails before any code is written.
  2. threat-modelling — PWNISMS threat model across all seven categories.
  3. osv-dependency-scan — on-the-fly software composition analysis (SCA). Whenever a task adds, upgrades, or imports a third-party package, this skill scans the exact name@version against the public OSV.dev database before the dependency is introduced. It does not block the developer's flow: for a HIGH/CRITICAL finding it automatically substitutes the recommended safe (fixed) version, keeps building, flags the avoided vuln in the response, and records it in telemetry. It ships a zero-dependency Node scanner at osv-dependency-scan/scripts/osv-scan.mjs (no API key required) that also emits a recommended safe version per package.
  4. vibereview-sync — write and sync the structured JSON scan artifact, including the dependency-scan results (each avoided vuln as a supply-chain threats_mitigated row, A06:2021 OWASP mapping, and an IDE-generated guardrail).

Sync One Scan Artifact

For normal IDE workflows, sync the JSON file created for the current event only:

npx -y @securityreviewai/vibereview@latest sync --file .vibereview/scans/<event>.json

Plain vibereview sync drains every JSON artifact in .vibereview/scans/ and is intended for manual recovery/backstop syncs.