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

dynamodb-dashboard

v1.25.6

Published

GUI Dashboard for local or remote DynamoDB

Readme

DynamoDB Dashboard

A Web GUI Dashboard for local or remote DynamoDB.

npm npm NPM

Docker Pulls Docker Image Size (tag)

dynamodb-dashboard Builder

Installation:

Install application globally:

npm install --global dynamodb-dashboard

Start dynamodb-dashboard instance:

dynamodb-dashboard start
Options
  • -d, --debug : show log output of running application (default: false)
  • -p, --port <port> : port to run app (default: 4567)
  • -h, --host <host> : host to run app (default: 127.0.0.1)

Setting Environment variables

Currently, following environment variables are supported:

  • AWS_REGION
  • AWS_ENDPOINT
  • AWS_ACCESS_KEY_ID
  • AWS_SECRET_ACCESS_KEY
  • AWS_SESSION_TOKEN

To configure, set the AWS environment variables in the terminal session before launching dynamodb-dashboard, example in .bashrc file.

AWS Credentials Resolution

The application uses the AWS SDK for JavaScript (v2), which supports multiple ways to load credentials automatically through the default credential provider chain.

  • Explicit environment variables
    • AWS_ACCESS_KEY_ID
    • AWS_SECRET_ACCESS_KEY
    • AWS_SESSION_TOKEN (optional)

    These take highest priority if provided.

  • ~/.aws/credentials
  • AWS SSO sessions
  • EC2/ECS instance metadata
  • Other AWS SDK-supported sources

Set environment variables and start dynamodb-dashboard instance:

export AWS_REGION=us-west-2
export AWS_ENDPOINT=http://localhost:8000
export AWS_ACCESS_KEY_ID=fakeAccessKeyId
export AWS_SECRET_ACCESS_KEY=fakeSecretAccessKey

dynamodb-dashboard start

Development Setup

  1. Setup Vue.js App
  2. Setup Node Express Server

OR

  1. git clone https://github.com/kritish-dhaubanjar/dynamodb-dashboard.git
  2. cd dynamodb-dashboard
  3. make watch

Docker

Run a container (from Docker Hub)

  1. docker pull kritishdhaubanjar/dynamodb-dashboard:latest
  2. docker run \
    --name dynamodb-dashboard \
     -p 8080:4567 \
     -e AWS_REGION=us-west-2 \
     -e AWS_ENDPOINT=http://host.docker.internal:8000 \
     -e AWS_ACCESS_KEY_ID=fakeAccessKeyId \
     -e AWS_SECRET_ACCESS_KEY=fakeSecretAccessKey \
     kritishdhaubanjar/dynamodb-dashboard:latest

NGINX Config

To configure Nginx to serve dynamodb-dashboard with (EventSource (Server-Sent Events or SSE) event stream), you need to ensure Nginx is correctly set up to handle long-lived HTTP connections and provide appropriate headers. Here's a basic example configuration:

server
{
    listen 80;
    listen [::]:80;

    server_name _;

    proxy_read_timeout 1d;
    proxy_send_timeout 1d;
    proxy_connect_timeout 1d;

    location /
    {
        proxy_pass http://localhost:4567;
    }

    location /dynamodb/api/database/stream/
    {
        proxy_buffering off;
        proxy_cache off;
        chunked_transfer_encoding off;

        add_header Content-Type text/event-stream;
        add_header Cache-Control no-cache;
        add_header Connection keep-alive;

        proxy_pass http://localhost:4567;
    }
}

Preview:

dynamodb-dashboard

image

Demo:

https://user-images.githubusercontent.com/25634165/192109458-a621bc06-788d-4d54-9dc2-9064380ee837.mp4

Buy Me a Coffee

Contributors ✨

Thanks goes to these wonderful people:

License

Distributed under the MIT License. See LICENSE for more information.