Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
cqlsh is a Python-based command-line client for running CQL commands on a cassandra cluster.
cqlsh
cqlsh
is a Python-based command-line client for running CQL
commands on a cassandra
cluster.
Normally it's packaged as part of the full Apache Cassandra™ installation. This repo repackages it into a standalone Python package for lighter-weight installs.
Install and update using pip
:
$ pip install -U cqlsh
$ cqlsh --help
Documentation is available as part of the official Apache Cassandra™ documentation.
Because this is a repackaging of cqlsh
from the official Cassandra repo, only issues / PRs related to PyPI packaging should be opened against this repo. If you would like to contribute to cqlsh
itself, find out more information here.
Steps to sanity check that the packaging works as expected:
cqlsh
locally (probably in a virtualenv
):$ pip install -e . # run from within the cqlsh directory
$ docker pull cassandra
$ docker run -it --rm -p 9042:9042 cassandra
cqlsh
successfully connects to the server:$ cqlsh
Connected to Test Cluster at 127.0.0.1:9042
[cqlsh 6.1.0 | Cassandra 4.1.0 | CQL spec 3.4.5 | Native protocol v5]
Use HELP for help.
cqlsh>
This PyPI package is maintained by Jeff Widman and Brad Schoening. Previous maintainers: Spiro and Andrew Mussey.
Unfortunately the Cassandra project does not always increment the cqlsh
version number, so for every
release we need to document not only the cqlsh
version but also the cassandra
version in which it
shipped.
This packages cqlsh
6.2.0
from Cassandra 5.0.0:
This packages cqlsh
6.1.0
from Cassandra 4.1.4:
This packages cqlsh
6.1.0
from Cassandra 4.1.1:
4.x
release, it is protocol compatible with Cassandra 3.x
clusters, with the exception of DESCRIBE
keywords which require a 4.x cluster.This packages cqlsh
6.1.0
from Cassandra 4.1:
4.x
release, it is protocol compatible with Cassandra 3.x
clusters, with the exception of DESCRIBE
keywords which require a 4.x cluster.The actual source code is identical to the cqlsh
6.0.0
release, except it's now packaged as
a module. This allows it to be used as a library, not just an executable script. It also provides
better Windows support. Details in https://github.com/jeffwidman/cqlsh/pull/7 by @bschoening.
Note: This release was yanked from PyPI because it broke Python 2 compatibility.
This packages cqlsh
6.0.0
from Cassandra 4.0:
4.x
release, it should generally work against Cassandra 3.x
clusters without needing to set any flags.This packages cqlsh
5.0.1
from Cassandra 4.0-beta4:
4.x
release, it should generally work against Cassandra 3.x
clusters without needing to set any flags.This packages cqlsh
5.0.1
from Cassandra 3.11.10.
This packages cqlsh
5.0.1
from Cassandra 3.4.0.
This packages cqlsh
5.0.1
from Cassandra 2.2.0.
This packages cqlsh
4.1.1
from Cassandra 2.0.5.
This packages cqlsh
4.1.0
from Cassandra 2.0.3.
This packages cqlsh
4.0.1
from Cassandra 2.0.1.
FAQs
cqlsh is a Python-based command-line client for running CQL commands on a cassandra cluster.
We found that cqlsh demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 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.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.