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.
getstream-cli
Advanced tools
The Stream CLI makes managing Stream applications directly from the command line easy.
Note: The Stream CLI is currently in beta and may contain bugs. This should not be used against a production environment at this time. To report bugs, please follow the instructions below. Thank you for your support!
Stream's Command Line Interface (CLI) makes it easy to create and manage your Stream apps directly from the terminal. Currently, only Chat is supported; however, the ability to manage Feeds will be coming soon.
If you're experiencing problems directly related to the CLI, please add an issue on GitHub.
For other issues, submit a support ticket.
As with any project, things are always changing. If you're interested in seeing what's changed in the Stream CLI, the changelog for this project can be found here.
The Stream CLI is easy to install and available via npm.
$ npm install -g getstream-cli
OR
$ yarn global add getstream-cli
In order to initialize the CLI, please have your Stream API key and secret ready. Run the following command:
$ stream config:set
You will then be prompted to enter your API key and secret.
$ ? What's your API key? 🔒
$ ? What's your API secret? 🔒
Now, you're good to go!
$ Your config has been generated! 🚀
Note: Your API key and secret can be found on the Stream Dashboard and is specific to your application.
Basic commands use the following syntax:
$ stream command:COMMAND --arg1 "foo" --arg2 "bar"
Whereas commands for specific products use subcommands:
$ stream command:COMMAND:SUBCOMMAND --arg1 "foo" --arg2 "bar"
Interested in using the calling the CLI from a script? Or maybe you simply want raw response data? You can do that! Many of the commands accept a json
argument as a boolean
. Just pass the following along to the CLI and you'll get back a full representation of the response (in a raw data format):
$ stream command:COMMAND --arg1 "foo" --arg2 "bar" --json
Need to copy the output to your clipboard? Not a problem. Just pipe the information to pbcopy
(on macOS) along with the --json
flag:
$ stream debug:token --token "foo.bar.baz" --json | pbcopy
$ npm install -g getstream-cli
$ stream COMMAND
running command...
$ stream (-v|--version|version)
getstream-cli/0.0.1-beta.24 darwin-x64 node-v10.15.1
$ stream --help [COMMAND]
USAGE
$ stream COMMAND
...
stream autocomplete
- display autocomplete installation instructionsstream chat
- configure and manage all things related to chatstream commands
- list all the commandsstream config
- manage configuration variablesstream debug
- debugging toolsstream help
- display help for streamIf you have any suggestions or just want to let us know what you think of the Stream CLI, please send us a message at support@getstream.io or create a GitHub Issue.
FAQs
Configure & manage Stream applications from the command line. 🚀
We found that getstream-cli demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 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.