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

@cumulus/tf-inventory

v22.2.5

Published

Package to help keep track of what resources are managed by Terraform in the AWS account

Readme

@cumulus/tf-inventory

@cumulus/tf-inventory provides utilities for monitoring Terraform deployments and resources across an AWS account.

About Cumulus

Cumulus is a cloud-based data ingest, archive, distribution and management prototype for NASA's future Earth science data streams.

Cumulus Documentation

Installation

npm install @cumulus/tf-inventory

Command Line Interface

The following utilities are provided via the CLI. For help run tf-inventory --help

Usage: tf-inventory TYPE COMMAND [options]

Options:
  -V, --version                output the version number
  -h, --help                   output usage information

Commands:
  list-deployments [options]   List Terraform Cumulus deployments in the account
  deployment-report [options]  List each Cumulus deployment with files, number of resources, and last update date
  list-orphaned-resources      List resources not associated with a Terraform deployment, currently supports ECS, EC2, and Elasticsearch

list-deployments and deployment-report take an optional --regex parameter to specify the regular expression used to extract the deployment name. For example, if state files are stored in the format bucket/deployment-name/terraform.tfstate, the regular expression '.*\/(.*)\/terraform.tfstate' could be specified to extract the deployment name. Or the regular expression '(.*)' could be specified to view all state files as their own deployment.

Assumptions

  • Terraform state files are configured for remote state storage in S3 using DynamoDB for locks. Follow the instructions in the deployment documentation for proper setup.

  • State files keys are in the format: .*/data-persistence.*/terraform.tfstate or .*/cumulus.*/terraform.tfstate or an extraction regex is specified for the list-deployments and deployment-report commands.

Errors

Error extracting deployment name from file ...

An Error extracting deployment name will be printed to the console if a Terraform state file is detected that does not match the specified deployment regular expression, or the default regular expression if none is specified.

Error reading <filename>: The specified key does not exist.

This indicates that there is a Terraform state entry in your DynamoDB locks table pointing to a state file that does not exist. terraform destroy empties your state file of resources, but does not remove the file from S3 nor the entry from DynamoDB. It's possible that the state file was manually deleted, but not the DynamoDB entry.

Contributing

To make a contribution, please see our contributing guidelines.