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

@cicube/ci-cleaner

v1.0.1

Published

A powerful CI/CD cleanup tool that automatically removes temporary files, logs, and artifacts with intelligent pattern matching

Readme

CI Cleaner 🧹

A powerful CI/CD cleanup tool maintained by CICube

Keep your CI/CD pipelines clean and efficient! Automatically remove temporary files, logs, and artifacts with intelligent pattern matching.

Maintained by CICube NPM Version License: MIT

About CICube

CICube's AI agents monitor your GitHub Actions workflows, detect anomalies, and provide actionable fixes - saving you hours of debugging time.

Visit cicube.io to learn more about our other developer tools and solutions.

Features

  • 🎯 Smart Pattern Matching: Advanced glob pattern support for precise file targeting
  • 🚫 Selective Exclusion: Protect important files with exclude patterns
  • 🔍 Safe Dry-Run Mode: Preview changes before execution
  • 🤖 CI Platform Detection: Automatic detection and optimization for:
    • GitHub Actions
    • GitLab CI
    • CircleCI
    • Generic CI environments
  • ⚙️ Flexible Configuration: Support for both JSON and YAML config files
  • 🎨 Beautiful Output: Clear, colorized console output for better visibility

Installation

# Global installation
npm install -g ci-cleaner

# Or use directly with npx
npx ci-cleaner

Quick Start

# Basic cleanup with default patterns
ci-cleaner

# Specify custom patterns
ci-cleaner --patterns="dist/ *.log build/"

# Exclude specific patterns
ci-cleaner --exclude="important.log critical-data/"

# Preview changes with dry-run
ci-cleaner --dry-run

Configuration

Via Config File

Create a .cicleanerrc.json or .cicleanerrc.yaml in your project root:

{
  "patterns": [
    "dist/",
    "*.log",
    ".cache",
    "node_modules/",
    "coverage/",
    "build/",
    "tmp/"
  ],
  "exclude": [
    "important.log",
    "critical-data/"
  ]
}

Or in YAML format:

patterns:
  - dist/
  - "*.log"
  - .cache
  - node_modules/
  - coverage/
  - build/
  - tmp/
exclude:
  - important.log
  - critical-data/

CI Integration Examples

GitHub Actions

- name: Cleanup Build Artifacts
  run: npx ci-cleaner --patterns="dist/ coverage/"

GitLab CI

cleanup:
  stage: cleanup
  script:
    - npx ci-cleaner --patterns="dist/ *.tmp"

CircleCI

- run:
    name: Cleanup Workspace
    command: npx ci-cleaner

Command Line Options

| Option | Description | Default | | ------------------ | ------------------------ | -------------------------- | | --patterns, -p | File patterns to clean | **/tmp, **/*.log, .cache | | --exclude, -e | Patterns to exclude | [] | | --dry-run, -d | Preview without deleting | false | | --config, -c | Path to config file | - | | --help, -h | Show help | - | | --version | Show version | - |

Best Practices

  1. Always use dry-run first: Preview changes with --dry-run before actual cleanup
  2. Be specific with patterns: Use precise patterns to avoid accidental deletions
  3. Exclude critical files: Always exclude important files using the --exclude option
  4. Use config files: Store your cleanup patterns in a config file for consistency

Support

Contributing

We welcome contributions! Please see our Contributing Guide for details.

License

MIT © CICube