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

@saltcorn/bash

v0.3.6

Published

Run bash actions in Saltcorn

Readme

bash

Run bash actions in Saltcorn

The run_bash_script action allows you to run shell code. It used to be restricted to bash scripts, but you can now use any shell interpreter (including Python).

Setting the shell interpreter

If you want to use a different shell interpreter than bash, you can set the first line to a shebang

Accessing the row

If the action is run against a specific row (e.g. as a button in List or Show views, or Insert/Update triggers), the fields are used to set environment variables. These are named ROW_{field name in upper case}. For instance, if the row contains a field called name then the environment variable ROW_NAME will be set. To access this in a bash script you should proceeded by a dollar sign ($), for instance:

echo $ROW_NAME

Accessing the user

The environment variables SC_USER_ID and SC_USER_ROLE are set to the user ID and the user's role ID, respectively

In workflows

To use this in workflows you use environment variables to access variables in the context. You cannot use interpolation in the code as this might conflict with your chosen shell interpreter.

After the action has completed, the following variables will be set in the context

  • exitcode: the exit code as a number
  • stdout: the process standard output
  • stderr: the process standard error