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

own-term

v0.1.0

Published

Create a beautiful, interactive terminal portfolio — installable via npx or npm i -g

Readme

Own-term 🚀

Own-term Banner

Create a beautiful, interactive terminal portfolio — installable via npx or npm i -g

npm version License: MIT PRs Welcome

FeaturesQuick StartDocumentationContributing


🎯 What is Own-term?

Own-term is a powerful, reusable framework for creating beautiful terminal portfolios.
Not just a single person's portfolio — it's a complete framework that lets anyone create their own interactive terminal experience.

Why Own-term?

  • 🎨 Beautiful by default - Stunning themes, gradients, and ASCII art
  • 🔌 Plugin system - Extend with custom commands and features
  • 🎭 Multiple themes - 6 built-in themes (dark, light, hacker, neo, dracula, nordic)
  • 💻 Dynamic prompts - 5 configurable prompt styles (git, time, dashboard, minimal, cyberpunk)
  • Zero config - Works out of the box, customize when you want
  • 📦 Easy to use - Run with npx or install globally
  • 🛠️ Developer friendly - TypeScript, well-documented, tested

✨ Features

Core Features

  • ✅ Interactive shell with commands: about, projects, skills, contact, resume, theme, help
  • ✅ Config file (termfolio.config.ts) for easy customization
  • ✅ Beautiful ASCII logo with Claude-style gradient (orange → pink → purple)
  • ✅ 6 color themes with gradient support
  • ✅ 5 dynamic prompt styles (git-style, time-based, dashboard, minimal, cyberpunk)
  • ✅ Context-aware prompts (changes based on current command)
  • ✅ Animated boot sequence and welcome screen
  • ✅ Installable via npm / runnable via npx

Advanced Features

  • 🔌 Plugin system for custom commands
  • 🎨 Theme system with 6 built-in themes
  • 📊 Beautiful rendering components (tables, progress bars, cards)
  • 🧪 Full test coverage
  • 🚀 CI/CD pipeline with GitHub Actions
  • 📚 Comprehensive documentation

🚀 Quick Start

Try it instantly

npx own-term

Install globally

npm install -g own-term
own-term

Create your own portfolio

  1. Create a config file (termfolio.config.ts):
export default {
  name: "Your Name",
  title: "Your Title",
  about: "A brief description about yourself",
  theme: "dark", // dark, light, hacker, neo, dracula, nordic
  promptStyle: "dashboard", // git, time, dashboard, minimal, cyberpunk
  links: {
    github: "https://github.com/yourusername",
    linkedin: "https://linkedin.com/in/yourusername",
    email: "[email protected]"
  },
  projects: [
    {
      name: "Awesome Project",
      desc: "Description of your project",
      repo: "https://github.com/yourusername/project",
      tags: ["javascript", "react"],
      status: "active" // active, wip, archived
    }
  ],
  skills: {
    languages: [
      { name: "JavaScript", level: 90 }, // with progress bar
      "Python" // or simple string
    ],
    frameworks: ["React", "Node.js"],
    tools: ["Git", "Docker", "VS Code"]
  },
  resume: "https://yourwebsite.com/resume.pdf"
};
  1. Run your portfolio:
npx own-term --config=./termfolio.config.ts

📖 Documentation

Available Commands

| Command | Description | |---------|------------| | about | Learn about the person | | projects | Browse projects (interactive picker) | | skills | See skills with progress bars | | contact | Get contact information | | resume | Open resume (if configured) | | theme [name] | Change theme (or see theme gallery) | | clear | Clear terminal and show welcome screen | | help | Show available commands | | exit | Exit the portfolio | | open [service] | Quick open links (e.g., open github) |

Themes

Built-in themes:

  • dark (default) - Modern dark theme with cyan/purple accents
  • light - Clean light theme
  • hacker - Matrix-style green terminal
  • neo - Neon pink & cyan
  • dracula - Classic Dracula palette
  • nordic - Muted Nordic tones

Change theme in config:

theme: "dracula"

Or interactively:

theme dracula

Prompt Styles

Choose from 5 dynamic prompt styles:

  1. git - Git-style: user@termfolio ~/project (context) ❯
  2. time - Time-based: [14:23] 📧 project:context ▶
  3. dashboard (default) - Full info with time, context, counter
  4. minimal - Zsh-style: ◆ ~/project ➜
  5. cyberpunk - Hacker aesthetic: █ root@project [context] $

Configure in termfolio.config.ts:

promptStyle: "time"

Prompts are context-aware and change based on your current command!

Skills Configuration

Two formats supported:

skills: {
  // With progress bars (0-100)
  languages: [
    { name: "TypeScript", level: 92 },
    { name: "JavaScript", level: 95 }
  ],
  
  // Simple pills
  tools: ["Git", "Docker", "VS Code"]
}

Example Configurations

See templates/ for complete examples:


🔌 Plugin Development

Create custom plugins to extend functionality:

import { createPlugin } from "own-term";

export default createPlugin("my-plugin", "1.0.0", (api) => {
  api.registerCommand("custom", "My custom command", async (args) => {
    api.render.header("Custom Command");
    api.render.text("Hello from my plugin!");
    
    // Access config
    const config = api.getConfig();
    api.render.info(`User: ${config.name}`);
    
    // Use theme colors
    api.render.success("Command executed!");
  });
});

Add plugins to your config:

export default {
  // ... other config
  plugins: ["@username/my-plugin-package"]
};

🛠️ Development

Prerequisites

  • Node.js 18+
  • npm or yarn

Setup

# Clone the repository
git clone https://github.com/Biki-dev/own-term.git
cd own-term

# Install dependencies
npm install

# Run in development mode
npm run dev

# Build
npm run build

# Run tests
npm test

# Lint
npm run lint

# Format code
npm run format

Project Structure

own-term/
├── src/
│   ├── cli.ts              # Entry point
│   ├── config.ts           # Config loader
│   ├── types.ts            # TypeScript definitions
│   ├── shell/
│   │   ├── engine.ts       # Shell engine with 5 prompt styles
│   │   ├── router.ts       # Command router
│   │   └── welcome.ts      # Welcome screen with gradient logo
│   ├── render/
│   │   ├── renderer.ts     # Rendering components
│   │   └── effects.ts      # Typewriter effects
│   ├── commands/
│   │   └── index.ts        # Core commands
│   ├── plugins/
│   │   ├── loader.ts       # Plugin loading system
│   │   └── plugin_api.ts   # Plugin API
│   └── themes/
│       └── default.ts      # 6 theme definitions
├── templates/              # Starter templates
├── tests/                  # Test files
└── bin/                    # Compiled output

🤝 Contributing

We love contributions! Please read our Contributing Guide to get started.

Ways to Contribute

  • 🐛 Report bugs via Issues
  • 💡 Suggest features
  • 📝 Improve documentation
  • 🎨 Create new themes
  • 🔌 Build plugins
  • ✅ Write tests
  • 🌍 Add translations

Development Workflow

  1. Fork the repo
  2. Create a feature branch: git checkout -b feature/my-feature
  3. Make your changes
  4. Run tests: npm test
  5. Run linter: npm run lint
  6. Commit with conventional commits: feat(prompt): add new style
  7. Push and create a Pull Request

📄 License

MIT © Biki-dev

See LICENSE for details.


🌟 Showcase

Using Own-term for your portfolio? Add it here!

  • Submit a PR to add your portfolio to this list

🙏 Acknowledgments


Made for developers

⬆ Back to top