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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@aws-cdk/cli-plugin-contract

v2.181.1

Published

Contract between the CLI and authentication plugins, for the exchange of AWS credentials

Downloads

362,027

Readme

AWS CDK CLI Library


cdk-constructs: Stable


Overview

As any piece of software that interacts with an AWS account, the CDK CLI needs AWS credentials for authentication and authorization. When it comes to choose which sources to get credentials from, it has the same behavior as the AWS CLI. But this basic behavior may result in some failure scenarios:

  • The initial set of credentials to work with cannot be obtained.
  • The account to which the initial credentials belong to cannot be obtained.
  • The account associated to the credentials is different from the account on which the CLI is trying to operate on.

Since these failures may happen for valid use case reasons, the CDK CLI offers an alternative mechanism for users to provide AWS credentials: credential provider plugins.

This package defines the types and the contract between the CLI and the plugins, which plugin authors are expected to adhere to.

The entrypoint is communicated to the CLI via the --plugin command line argument. The value of this argument should be a JavaScript file that, when require'd, will return an instance of the Plugin interface.

Once the CLI gets an instance of a plugin, it first initializes plugin by calling the Plugin.init() method, if one is defined. The CLI uses this method to pass an instance of IPluginHost to the plugin. The plugin, in turn, can use the repository to register one or more instances of CredentialProviderSource, which is where the actual logic for providing credentials is located.

If, in the authentication process, the CLI decides to use plugins, it will try each credential provider source in the order in which they were registered. For each source, the first thing the CLI will check is whether the source is ready to interact at all, by calling the isAvailable() method. If it is available, the next check is whether it can provide credentials for the specific account the CLI is targeting at that moment. This is the canProvideCredentials() method.

If both checks pass, the CLI asks the source for credentials by calling getProvider(). In addition to the account ID, this method also receives the Mode of operation, which can be ForReading or ForWriting. This information may be useful to tailor the credentials for the use case. For example, if the CLI needs the credentials only for reading, the plugin may return credentials with more restricted permissions.