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

greenops-scan

v0.1.13

Published

GreenOps CLI Scanner — identify carbon & cost savings in your cloud infrastructure

Readme

greenops-scan

Cloud Carbon & Cost Scanner — identify waste, cut carbon, save money.

Scans your AWS infrastructure using read-only APIs and generates actionable reports with cost and carbon savings estimates.

Quick Start

npx greenops-scan

What It Scans

| Module | What it detects | |--------|----------------| | EC2 | Idle instances, old-gen Intel → Graviton upgrades, unattached EBS volumes | | S3 | Missing lifecycle policies, version accumulation, large un-tiered buckets | | ECS | Empty clusters, over-provisioned Fargate (validated via 30-day CloudWatch metrics) | | EKS | Outdated K8s versions, non-Graviton node groups, no autoscaler | | Lambda | Zombie functions, legacy runtimes, x86→ARM, over-provisioned memory | | RDS | Idle databases, Graviton upgrades, Multi-AZ on non-prod, old snapshots | | ElastiCache | Idle caches, Graviton upgrades | | CloudFront | Unused distributions, missing HTTPS redirect, outdated TLS | | EBS Snapshots | Old snapshots, unused AMIs |

Features

  • Interactive TUI with arrow-key profile and region selection
  • IAM permission checking per module
  • Parallel scanning with live progress display
  • Carbon calculations using Green Software Foundation methodology
  • JSON report export
  • Branded PDF report generation (7 pages)
  • Modular architecture — ready for GCP/Azure providers

CLI Options

npx greenops-scan [options]

  -p, --provider <name>    Cloud provider: aws (skip interactive selection)
      --profile <name>     AWS profile name (skip interactive selection)
  -r, --region <code>      AWS region code, e.g. eu-west-1 (skip interactive selection)
  -s, --severity <levels>  Comma-separated severity filter: critical,high,medium,low
      --endpoint-url <url> Custom AWS endpoint (e.g. http://localhost:4566 for LocalStack)
  -h, --help               Show help

Examples:

# Fully non-interactive scan
npx greenops-scan --provider aws --profile production --region eu-west-1

# Show only high-impact findings
npx greenops-scan --severity high,critical

# Combine options
npx greenops-scan --profile dev --region us-east-1 --severity medium,high,critical

Security

This scanner runs locally and uses read-only AWS APIs. Your cloud credentials never leave your machine.

Requirements

  • Node.js 18+
  • AWS credentials configured in ~/.aws/credentials or via environment variables (or dummy creds for LocalStack)