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

@plurnk/plurnk-execs-git

v1.8.0

Published

Native Git runtime executor for plurnk-service's exec scheme, using direct argv execution without a shell.

Downloads

4,854

Readme

@plurnk/plurnk-execs-git

Native Git for Plurnk Service's EXEC scheme. ## EXEC0 [git] invokes the installed git binary with ordinary Git arguments. Arguments are tokenized into argv and executed directly, never interpreted by a shell.

Contract

  • git means native Git. Plurnk does not replace or reinterpret its commands.
  • Native stdout and stderr are preserved as #stdout and #stderr under the emitted git:///<loop>/<turn>/<sequence> address ({§executor-output-address}).
  • (target) names the repo directory and maps to Git's -C option.
  • Repository-local GIT_* variables inherited from a launcher cannot override the selected workspace or (target); normal Git configuration still applies.
  • An unavailable Git binary makes the runtime unavailable; there is no fallback.
  • Every invocation is host and therefore proposal-gated ({§executor-effect}).

Git may invoke repository hooks, aliases, credential helpers, and network operations. Deployments that do not grant those capabilities should disable the runtime with PLURNK_EXECS_GIT=0.

Usage

## EXEC0 [git]
status --short

## EXEC0 [git]
checkout -b feature/example

## EXEC0 [git]
add .

## EXEC0 [git]
commit -m "save work"

## EXEC0 [git] (./subrepo)
log --oneline -5

The repo's normal Git configuration determines author identity and other native behavior.