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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@iac-factory/tty-testing

v0.1.9

Published

...

Downloads

8

Vulnerabilities

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

Links

Maintainers

segmentationalsegmentational

Keywords

Readme

@iac-factory/tty-testing

Demonstrative npm package that highlights the different methods, and limitations, of spawning child-processes via node.js runtimes.

Note - Anything with a ⓘ is a dropdown containing additional, contextual information.

Usage(s)

Disclaimer

CLI utilities can be incredibly dangerous.

  • stdin, os.exec, and shells are easy to interface and therefore exploit.
  • Having the ability to issue os.exec or interface stdin always makes the application dangerous.
  • Protecting against harmful bugs or malicious actors isn't difficult if the application's logic is handled correctly, and so long as precautions are made to disable REPLs (but allowing SIGKILL, SIGSTOP, and other user-controlled signals).

A language's packaging utility (npx, pep, cargo, etc.) extends some amazing capabilities, but should never have the opportunity to be taken advantage of (Development Supply-Chain Attacks).

Ensure due diligence in writing cli applications.

Global

npx --yes @iac-factory/tty-testing@latest --always-spawn

System

npm install --global @iac-factory/tty-testing@latest && tty-testing

Local

npm run start

Setup (Development)

Please note: the following section is only required if usage relates to local development where the tty-testing package is locally cloned.

All other usage can be limited to npx or otherwise a system install of @iac-factory/tty-testing.

# --> (1) Clone the repository
# --> (2) Change into the local clone's directory
# --> (3) Install package dependencies

git clone "https://github.com/iac-factory/tty-testing.git" \
    || git clone [email protected]:iac-factory/tty-testing.git

cd tty-testing && npm install