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

shwet46-portfolio

v2.0.3

Published

Beautiful terminal portfolio

Readme

Terminal Portfolio </>

Demo


Create Your Own Terminal Portfolio

Follow these steps to customize and deploy your own CLI portfolio.


1. Clone or Fork the Repository

You can either fork this repository or clone it locally.

git clone https://github.com/shwet46/CLI-portfolio.git
cd CLI-portfolio
npm install

2. Customize Your Portfolio Data

Update the data.json file with your personal information. This file controls most of the displayed content.

You can also modify index.js if you want to change the structure or style of the portfolio.


3. Change Package and Command Name

Open package.json and update the name and bin fields:

{
  "name": "your-package-name",
  "version": "1.0.0",
  "bin": {
    "your-command-name": "./index.js"
  }
}
  • name: This will be the name of your package on npm.
  • your-command-name: This is the command users will run with npx, try to keep it same as package name.

For example:

{
  "name": "shwet46-portfolio",
  "bin": {
    "shwet46": "./index.js"
  }
}

4. Test Locally

Run the following command inside your project to link your package locally:

npm link

Then you can test your command:

your-command-name

5. Publish to NPM

If you want others to be able to run your portfolio with npx, you'll need to publish it to npm.

Login to npm

npm login

Publish Package

npm publish

Once published, anyone can run your portfolio using:

npx your-package-name

or

npx your-command-name

Hope you liked this and created your own portfolio :)

License

MIT License. See LICENSE file for details.