Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
@adobe/aio-cli
Advanced tools
Adobe I/O Extensible CLI ******* ******* ****** ****** ***** ***** **** * **** *** *** *** ** ***** ** * ** *
Adobe I/O Extensible CLI
$ npm install
$ npm link
$ npm install -g @adobe/aio-cli
$ aio COMMAND
running command...
$ aio (-v|--version|version)
@adobe/aio-cli/2.0.1 darwin-x64 node-v10.16.0
$ aio --help [COMMAND]
USAGE
$ aio COMMAND
...
aio autocomplete [SHELL]
aio config
aio config:clear
aio config:delete KEYS...
aio config:edit
aio config:get KEY
aio config:list
aio config set key 'a value' # set key to 'a value'
aio console
aio console:integration NAMESPACE
aio console:list-integrations
aio console:reset-integration [INTEGRATION_ID]
aio console:select-integration [INTEGRATION_ID]
aio console:selected-integration
aio help [COMMAND]
aio jwt-auth:access-token
aio plugins
aio plugins:install PLUGIN...
aio plugins:link PLUGIN
aio plugins:uninstall PLUGIN...
aio plugins:update
aio autocomplete [SHELL]
display autocomplete installation instructions
USAGE
$ aio autocomplete [SHELL]
ARGUMENTS
SHELL shell type
OPTIONS
-r, --refresh-cache Refresh cache (ignores displaying instructions)
EXAMPLES
$ aio autocomplete
$ aio autocomplete bash
$ aio autocomplete zsh
$ aio autocomplete --refresh-cache
See code: @oclif/plugin-autocomplete
aio config
list, get, set, delete, and edit persistent configuration data
USAGE
$ aio config
OPTIONS
-e, --env environment variables
-g, --global global config
-j, --json output in json
-l, --local local config
-y, --yaml output in yaml
--verbose show all config values
ALIASES
$ aio config:ls
EXAMPLES
$ aio config:list
$ aio config:get KEY
$ aio config:set KEY VALUE
$ aio config:delete KEY
$ aio config:clear
See code: @adobe/aio-cli-plugin-config
aio config:clear
clears all persistent config values
USAGE
$ aio config:clear
OPTIONS
-f, --force do not prompt for confirmation
-g, --global global config
-l, --local local config
See code: @adobe/aio-cli-plugin-config
aio config:delete KEYS...
deletes persistent config values
USAGE
$ aio config:delete KEYS...
OPTIONS
-g, --global global config
-l, --local local config
ALIASES
$ aio config:del
$ aio config:rm
See code: @adobe/aio-cli-plugin-config
aio config:edit
edit config file
USAGE
$ aio config:edit
OPTIONS
-g, --global global config
-l, --local local config
See code: @adobe/aio-cli-plugin-config
aio config:get KEY
gets a persistent config value
USAGE
$ aio config:get KEY
OPTIONS
-e, --env environment variables
-g, --global global config
-j, --json output in json
-l, --local local config
-y, --yaml output in yaml
See code: @adobe/aio-cli-plugin-config
aio config:list
lists all persistent config values
USAGE
$ aio config:list
OPTIONS
-e, --env environment variables
-g, --global global config
-j, --json output in json
-l, --local local config
-y, --yaml output in yaml
--verbose show all config values
ALIASES
$ aio config:ls
See code: @adobe/aio-cli-plugin-config
aio config set key 'a value' # set key to 'a value'
sets a persistent config value
USAGE
$ aio config set key 'a value' # set key to 'a value'
$ aio config set key -f value.json # set key to the json found in the file value.json
$ aio config set -j key < value.json # set key to the json found in the file value.json
OPTIONS
-f, --file value is a path to a file
-g, --global global config
-i, --interactive prompt for value
-j, --json value is json
-l, --local local config
-y, --yaml value is yaml
See code: @adobe/aio-cli-plugin-config
aio console
List or select console integrations for the Adobe I/O Runtime
USAGE
$ aio console
OPTIONS
-n, --name sort results by name
-p, --passphrase=passphrase the passphrase for the private-key
ALIASES
$ aio console:ls
$ aio console:list
EXAMPLES
$ aio console:list-integrations
$ aio console:ls
$ aio console list-integrations
$ aio console:select-integration INTEGRATION_ID
$ aio console:sel INTEGRATION_ID
$ aio console select-integration INTEGRATION_ID
$ aio console:reset-integration INTEGRATION_ID
$ aio console:reset INTEGRATION_ID
$ aio console reset-integration INTEGRATION_ID
$ aio console:current-integration
$ aio console:current
$ aio console current-integration
See code: @adobe/aio-cli-plugin-console
aio console:integration NAMESPACE
Views an integration for use with Adobe I/O Runtime serverless functions
USAGE
$ aio console:integration NAMESPACE
ARGUMENTS
NAMESPACE namespace of an integration
OPTIONS
-p, --passphrase=passphrase the passphrase for the private-key
ALIASES
$ aio console:get
$ aio console:int
See code: @adobe/aio-cli-plugin-console
aio console:list-integrations
lists integrations for use with Adobe I/O Runtime serverless functions
USAGE
$ aio console:list-integrations
OPTIONS
-n, --name sort results by name
-p, --passphrase=passphrase the passphrase for the private-key
ALIASES
$ aio console:ls
$ aio console:list
See code: @adobe/aio-cli-plugin-console
aio console:reset-integration [INTEGRATION_ID]
resets an integration's .wskprops auth hash.
USAGE
$ aio console:reset-integration [INTEGRATION_ID]
DESCRIPTION
after running this command all clients will need to run `console:select-integration`
to get a new auth hash in their .wskprops file
ALIASES
$ aio console:reset
See code: @adobe/aio-cli-plugin-console
aio console:select-integration [INTEGRATION_ID]
selects an integration and writes the .wskprops file to the local machine
USAGE
$ aio console:select-integration [INTEGRATION_ID]
OPTIONS
-f, --force do not prompt if the .wskprops file exists
-g, --global save selected integration to global config
-l, --local save selected integration to local config
-p, --passphrase=passphrase the passphrase for the private-key
-w, --wskprops save selected integration to .wskprops file (default)
DESCRIPTION
Run 'console:ls' to get a list of integrations to select from.
The .wskprops file will be written to your home folder, and you will be prompted whether you want to overwrite an
existing file.
ALIASES
$ aio console:sel
$ aio console:select
See code: @adobe/aio-cli-plugin-console
aio console:selected-integration
lists the selected integration for use with Adobe I/O Runtime serverless functions
USAGE
$ aio console:selected-integration
OPTIONS
-p, --passphrase=passphrase the passphrase for the private-key
ALIASES
$ aio console:selected
$ aio console:current
See code: @adobe/aio-cli-plugin-console
aio help [COMMAND]
display help for aio
USAGE
$ aio help [COMMAND]
ARGUMENTS
COMMAND command to show help for
OPTIONS
--all see all commands in CLI
See code: @oclif/plugin-help
aio jwt-auth:access-token
get the access token for the Adobe I/O Console
USAGE
$ aio jwt-auth:access-token
OPTIONS
-b, --bare print access token only
-f, --force get a new access token
-p, --passphrase=passphrase the passphrase for the private-key
--no-prompt do not prompt for passphrase
DESCRIPTION
You must have a 'jwt-auth' key in your config, that has all your config data in .json format:
aio config set jwt-auth --json --file path/to/your/config.json
EXAMPLE
jwt_auth:
{
"client_id": "...",
"client_secret": "..."
"jwt_payload": {
"iss": "...",
"sub": "...",
"...": true,
"aud": "..."
},
"jwt_private_key": "/path/to/cert"
}
See code: @adobe/aio-cli-plugin-jwt-auth
aio plugins
list installed plugins
USAGE
$ aio plugins
OPTIONS
--core show core plugins
EXAMPLE
$ aio plugins
See code: @oclif/plugin-plugins
aio plugins:install PLUGIN...
installs a plugin into the CLI
USAGE
$ aio plugins:install PLUGIN...
ARGUMENTS
PLUGIN plugin to install
OPTIONS
-f, --force yarn install with force flag
-h, --help show CLI help
-v, --verbose
DESCRIPTION
Can be installed from npm or a git url.
Installation of a user-installed plugin will override a core plugin.
e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command
will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in
the CLI without the need to patch and update the whole CLI.
ALIASES
$ aio plugins:add
EXAMPLES
$ aio plugins:install myplugin
$ aio plugins:install https://github.com/someuser/someplugin
$ aio plugins:install someuser/someplugin
See code: @oclif/plugin-plugins
aio plugins:link PLUGIN
links a plugin into the CLI for development
USAGE
$ aio plugins:link PLUGIN
ARGUMENTS
PATH [default: .] path to plugin
OPTIONS
-h, --help show CLI help
-v, --verbose
DESCRIPTION
Installation of a linked plugin will override a user-installed or core plugin.
e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello'
command will override the user-installed or core plugin implementation. This is useful for development work.
EXAMPLE
$ aio plugins:link myplugin
See code: @oclif/plugin-plugins
aio plugins:uninstall PLUGIN...
removes a plugin from the CLI
USAGE
$ aio plugins:uninstall PLUGIN...
ARGUMENTS
PLUGIN plugin to uninstall
OPTIONS
-h, --help show CLI help
-v, --verbose
ALIASES
$ aio plugins:unlink
$ aio plugins:remove
See code: @oclif/plugin-plugins
aio plugins:update
update installed plugins
USAGE
$ aio plugins:update
OPTIONS
-h, --help show CLI help
-v, --verbose
See code: @oclif/plugin-plugins
FAQs
Adobe I/O Extensible CLI ******* ******* ****** ****** ***** ***** **** * **** *** *** *** ** ***** ** * ** *
The npm package @adobe/aio-cli receives a total of 3,216 weekly downloads. As such, @adobe/aio-cli popularity was classified as popular.
We found that @adobe/aio-cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.