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

@20i/aws-profile-scripts

v0.2.0

Published

DEPRECATED: use the native AWS CLI sign-in flow (`aws configure sso` + `aws login`/`aws logout`) instead. Both aws-mfa and add-aws-profile now only print deprecation notices.

Readme

aws-profile-scripts

⚠️ This package is deprecated. Both commands it provided — aws-mfa and add-aws-profile — have been superseded by the native AWS CLI sign-in flow (aws configure ssoaws login / aws logout), which auto-refreshes temporary credentials and removes the need for long-lived or pasted secrets. The commands now print deprecation notices instead of performing their old behavior. See the per-command sections below, and the AWS docs: https://docs.aws.amazon.com/signin/latest/userguide/command-line-sign-in.html

Installation

npm i --location=global @20i/aws-profile-scripts

Usage

Scenario 1: MFA device — aws-mfa is DEPRECATED

⚠️ aws-mfa is deprecated. It previously fetched temporary STS session-token credentials using your MFA device and stored them in an AWS profile. The modern AWS CLI now provides a built-in browser sign-in flow (aws login / aws logout) that removes the need for this script — and for long-lived IAM access keys.

Running aws-mfa no longer performs the old MFA flow. It now prints a deprecation notice that detects your AWS CLI version and tells you how to switch.

Recommended workflow:

  1. Make sure you have a recent AWS CLI installed (run aws --version). If aws login is unavailable, install or upgrade the AWS CLI per the docs: https://docs.aws.amazon.com/signin/latest/userguide/command-line-sign-in.html
  2. Sign in with aws login and sign out with aws logout.
  3. Because the new flow does not need permanent IAM access keys, remove your now-unused long-lived credentials:
    • Delete your IAM user's access keys in the AWS console (IAM → Users → your user → Security credentials → Access keys), or via aws iam delete-access-key --access-key-id <KEY_ID>.
    • Remove the stale access keys / *-mfa profiles from ~/.aws/credentials.

See the AWS docs for full details: https://docs.aws.amazon.com/signin/latest/userguide/command-line-sign-in.html

Scenario 2: SSO credentials — add-aws-profile is DEPRECATED

⚠️ add-aws-profile is deprecated. It was a paste helper: you copied the temporary credentials block from the AWS SSO start page ("Option 2: Add a profile to your AWS credentials file") and it pasted them into ~/.aws/credentials. Because those credentials expire, you had to re-paste them constantly.

Running add-aws-profile no longer performs the paste flow. It now prints a deprecation notice pointing you at the native AWS CLI SSO sign-in.

Recommended workflow:

  1. Register your SSO profile once:
    aws configure sso
    (Use your SSO start URL, e.g. https://twentyideas.awsapps.com/start/, and pick the account/role when prompted.)
  2. Sign in whenever you need credentials — this opens a browser and automatically refreshes temporary credentials, with no copy-paste:
    aws login        # or the equivalent: aws sso login
  3. Remove the now-unused pasted profiles and access keys from ~/.aws/credentials.

See the AWS docs for full details: https://docs.aws.amazon.com/signin/latest/userguide/command-line-sign-in.html