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

@grekt/cli

v6.48.1

Published

AI tools versioned, synced, and shared across tools and teams

Readme

Snyk Socket

Local-first AI tooling infrastructure. Audit, manage, and secure MCPs, agents, skills, hooks, and commands across Claude Code, Cursor, and more from your machine, with no cloud dependency.

Free to use. grekt is free for personal and commercial use. The source is available under BSL 1.1, which means you can't use this code to build something that competes with grekt. Each version converts to MIT after two years.

Why grekt?

You are running AI tools you have never checked. Every time you install a skill from a registry, add an MCP server, or pull an agent config you are trusting code that has direct access to your editor, your files, and your workflow.

No sandbox. No review. No audit. 20% of skills in public registries have been flagged as malicious. 84% of developers use AI tools daily, but only 29% trust what they're running. The gap between adoption and trust is growing. grekt closes it.

grekt gives you three things:

  • Visibility. See every AI artifact in your projects. What it does, what it touches, whether anyone has actually checked it.
  • Verification. Every artifact scanned for security risks and evaluated for quality. PASS, FAIL, or WARN -- no ambiguity.
  • Control. Lock versions. Pin hashes. Sync verified configurations across your team. Your tools, your machine, your rules.

Installation

Linux / macOS

curl -fsSL https://cli.grekt.com/install.sh | sh

macOS (Homebrew)

brew install grekt-labs/tap/grekt

npm

npm install -g @grekt/cli

Quick Start

grekt init                        # Initialize a project
grekt add @scope/artifact-name    # Add an artifact
grekt install                     # Install from lockfile
grekt sync                        # Sync to your AI tools

Verify your stack

grekt scan                        # Scan artifacts for security risks
grekt eval                        # Evaluate artifact quality and behavior
grekt check                       # Check lockfile integrity and drift

Manage artifacts

grekt list                        # List installed artifacts
grekt outdated                    # Check for available updates
grekt upgrade                     # Upgrade artifacts
grekt trust @scope/artifact       # Mark an artifact as trusted

Artifacts can come from:

  • Your self-hosted registry on GitHub or GitLab
  • The public registry (@scope/name)
  • Official repos on GitHub (github:user/repo) or GitLab (gitlab:host/user/repo)
  • A local path on your machine (./path)

Supported tools

grekt syncs to Claude Code, Cursor, Windsurf, Cline, GitHub Copilot, Aider, Continue, OpenCode, Amazon Q, and any tool following the agentskills.io standard.

For the full command reference and guides, visit the documentation.

Contributing

See CONTRIBUTING.md. Feature requests and bug reports are welcome.

License

BSL 1.1 -- What does this mean?