Package Search Help

You can use boolean logic (e.g. AND/OR/NOT) for complex search queries. For more help and examples, see the search documentation.

Search by package name:
my-package (implicit)
name:my-package (explicit)

Search by package filename:
my-package.ext (implicit)
filename:my-package.ext (explicit)

Search by package tag:
latest (implicit)
tag:latest (explicit)

Search by package version:
1.0.0 (implicit)
version:1.0.0 (explicit)
prerelease:true (prereleases)
prerelease:false (no prereleases)

Search by package architecture:
architecture:x86_64 

Search by package distribution:
distribution:el 

Search by package license:
license:MIT 

Search by package format:
format:deb 

Search by package status:
status:in_progress 

Search by package file checksum:
checksum:5afba 

Search by package security status:
severity:critical 

Search by package vulnerabilities:
vulnerabilities:>1 
vulnerabilities:<1000 

Search by package downloads:
downloads:>8 
downloads:<100 

Search by package type:
type:binary 
type:source 

Search by package size (bytes):
size:>50000 
size:<10000 

Search by dependency name:
dependency:log4j 

Search by uploaded date:
uploaded:>"1 day ago" 
uploaded:<"August 14, 2018 EST" 

Search by entitlement token (identifier):
entitlement:3lKPVJPosCsY 

Search queries for all Maven-specific (and related) package types

Search by group ID:
maven_group_id:org.apache 

Field type modifiers (depending on the type, you can influence behaviour)

For all queries, you can use:
~foo for negation

For string queries, you can use:
^foo to anchor to start of term
foo$ to anchor to end of term
foo*bar for fuzzy matching

For number/date queries, you can use:
>foo for values greater than
>=foo for values greater / equal
<foo for values less than
<=foo for values less / equal

Need a secure and centralised artifact repository to deliver Alpine, Cargo, CocoaPods, Composer, Conan, Conda, CRAN, Dart, Debian, Docker, Go, Helm, LuaRocks, Maven, npm, NuGet, P2, Python, RedHat, Ruby, Terraform, Vagrant, Raw & More packages?

Cloudsmith is the new standard in Package / Artifact Management and Software Distribution.

With support for all major package formats, you can trust us to manage your software supply chain.

Start My Free Trial

Tool-Specific Instructions

Although we use GPG (and RSA) keys across each repository and package format, client-side tools might have specific instructions that differ (or require manual steps). To add or use the signing key for these tools, please click on the package format specific tabs above.

Public GPG Key

GPG-based key signing is used by:   Cargo logo CocoaPods logo Composer logo Conan logo Conda logo CRAN logo Dart logo Debian logo Docker logo Go logo Helm logo LuaRocks logo Maven logo npm logo NuGet logo Python logo RedHat logo Ruby logo Terraform logo Vagrant logo Raw logo

The public GPG key for the consensys/teku is:

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2
mQENBGATaU8BCACVnthYLXik+G/xVhNQSBjfh1jBVzmbFf//uNLnFQQyqQorlBXW
nVdkizAT6Wej4xgiYfy9NaEVXIkZEiJGPsmtW+/bBx62sfdhNeJDUydEO11E4Pj/
2el3tm2M3OGvLA8RhyMBdyNErJf01CezDnutwTwekR562yJ+YLhfzDbLgO6CtCFW
TwcCLsfXyOwQ3/yjI/v3Cliax4HbYHE68UmyBZD91S/kzXWKiugkcPy9VEMK+/Hc
p2McHOBUxOZoXlnvmaR+jgRUovixyiexgg+iDXcz+5mSpr3BqOCCvN47uOJXMfKV
wbioCGLCdWbfXqkucCRrXlDwjJ2IVo0K/4x1ABEBAAG0O0Nsb3Vkc21pdGggUGFj
a2FnZSAoY29uc2Vuc3lzL3Rla3UpIDxzdXBwb3J0QGNsb3Vkc21pdGguaW8+iQE3
BBMBCAAhBQJgE2lPAhsvBQsJCAcDBRUKCQgLBRYCAwEAAh4BAheAAAoJEDk03evJ
nt4CTUUH/1bK7jRfSruY8fZYvUMP0JW5z7l02xEKmRdG0CmJfYAfwdJqJ48+3Hg7
u32n76LM+o5t9HcBBqEHHXG0UKCn9mqpbQ0b+LJ1VSCiB0V8uRGxSzV6tjYOnS9L
QQvN2XSOuiqzbQe5xljVsu041EFgW0nQPofeUg0daq2hnyKb7au8D358HQTsyG6P
Vs+EaakkwYbeZ88xShq25GAbQCOWuY4WZ2eLbRTa546l5IEgfXCPDg9LsPrOTdbl
xY2KQAY55ao2VUGOItVXIJsP61a/6E4Jjj6E6SeUFGof1GmkSHrrdMwjESq9+WTs
CA6O61FXhz00q1TtTaI5Bb+fsFmH+Hk=
=dmft
-----END PGP PUBLIC KEY BLOCK-----

It has the following long (20 bytes) and short (8 bytes) fingerprints:

7663008F7251163434C9E8E53934DDEBC99EDE02
3934DDEBC99EDE02

You can download the GPG key or fetch it via the command-line:

curl -sL 'https://artifacts.consensys.net/public/teku/gpg.3934DDEBC99EDE02.key'

Public RSA Key

RSA-based key signing is used by:   Alpine logo

The public RSA key for the consensys/teku is:

-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvyzBpMyLNaiTbkdANnwy
8Ss+SqRk2WYQ9Rs5NQ8rmpw4Xh6c4oTFLx6jSMJZHr+CJE2aff+00NnHcj2QZdDj
8tnAeTOwAqK77NJafvKUJcny7865mNjWy+T6/ZPR7XUNMuaC/xBpbpqhm7HX+Dmz
1GSMxily9NrXz1IbQMqQp/W0PDy7vu4tfRKsUmN+3KQRTgHBcpqUPztN8dC4naqp
Rcp6UQF9mdtqp46LVnBprvgwGvoqrtZSRIWTAQYvsspd4YI96P3JLrPVqe8+4RTr
lUX5APWlLzBOLb84iGYmS23pLGKfLE4UKkNqGn+i2t+t6CL/bK2aHO2y4O3VPBsK
CQIDAQAB
-----END PUBLIC KEY-----

It has the following long (16 bytes) and short (8 bytes) fingerprints:

3F08C0D6EDD59559BF48D1D07E699D69
BF48D1D07E699D69

You can download the RSA key or fetch it via the command-line:

curl -sL 'https://artifacts.consensys.net/public/teku/rsa.BF48D1D07E699D69.key'

Need Help?

If you couldn't find what you needed in our documentation, then you can always chat to a member of our team instead. It's our mission to be your dedicated off-site team for package management, and we mean it. Come and chat with us, anytime.

Alpine logo

Alpine Signing Key Installation

The following instructions are for Alpine (e.g. apk) packages or compatible.

Automated Installation (Bash)

If you installed the consensys/teku repository by following one of the repository installation instructions then you don't need take any further action. The RSA key should already have been installed alongside the repository.

Manual Installation

If you'd like to manually install the RSA key, you can utilise curl to retrieve the RSA key and install it by executing:

curl -sL 'https://artifacts.consensys.net/public/teku/rsa.BF48D1D07E699D69.key' >/etc/apk/keys/teku@consensys-BF48D1D07E699D69.rsa.pub

Or you can add it directly without curl by executing:

sudo cat >/etc/apk/keys/teku@consensys-BF48D1D07E699D69.rsa.pub <<EOF
    -----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvyzBpMyLNaiTbkdANnwy
8Ss+SqRk2WYQ9Rs5NQ8rmpw4Xh6c4oTFLx6jSMJZHr+CJE2aff+00NnHcj2QZdDj
8tnAeTOwAqK77NJafvKUJcny7865mNjWy+T6/ZPR7XUNMuaC/xBpbpqhm7HX+Dmz
1GSMxily9NrXz1IbQMqQp/W0PDy7vu4tfRKsUmN+3KQRTgHBcpqUPztN8dC4naqp
Rcp6UQF9mdtqp46LVnBprvgwGvoqrtZSRIWTAQYvsspd4YI96P3JLrPVqe8+4RTr
lUX5APWlLzBOLb84iGYmS23pLGKfLE4UKkNqGn+i2t+t6CL/bK2aHO2y4O3VPBsK
CQIDAQAB
-----END PUBLIC KEY-----
    EOF

Removing Installation / Uninstalling

If you want to remove the public RSA key for the consensys/teku repository then you can do so by executing the following:

sudo rm -f /etc/apk/keys/teku@consensys-BF48D1D07E699D69.rsa.pub

Note: Don't do this if you currently have the repository installed and wish to continue using it. If you remove the key the next fetch will fail.

Viewing Installed Keys

If you want to verify that a RSA public key has been installed or removed, you can view the list of all installed keys by executing:

ls -la /etc/apk/keys/
Debian logo

Debian Signing Key Installation

The following instructions are for Debian (e.g. apt, deb, dpkg) packages or compatible.

Automated Installation (Bash)

If you installed the consensys/teku repository by following one of the repository installation instructions then you don't need take any further action. The GPG key should already have been installed alongside the repository.

Manual Installation

If you'd like to manually install the GPG key, you can utilise curl to retrieve the GPG key and install it by executing:

curl -sL 'https://artifacts.consensys.net/public/teku/gpg.3934DDEBC99EDE02.key' | sudo apt-key add -

Or you can add it directly without curl by executing:

sudo apt-key add - <<EOF
    -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2
mQENBGATaU8BCACVnthYLXik+G/xVhNQSBjfh1jBVzmbFf//uNLnFQQyqQorlBXW
nVdkizAT6Wej4xgiYfy9NaEVXIkZEiJGPsmtW+/bBx62sfdhNeJDUydEO11E4Pj/
2el3tm2M3OGvLA8RhyMBdyNErJf01CezDnutwTwekR562yJ+YLhfzDbLgO6CtCFW
TwcCLsfXyOwQ3/yjI/v3Cliax4HbYHE68UmyBZD91S/kzXWKiugkcPy9VEMK+/Hc
p2McHOBUxOZoXlnvmaR+jgRUovixyiexgg+iDXcz+5mSpr3BqOCCvN47uOJXMfKV
wbioCGLCdWbfXqkucCRrXlDwjJ2IVo0K/4x1ABEBAAG0O0Nsb3Vkc21pdGggUGFj
a2FnZSAoY29uc2Vuc3lzL3Rla3UpIDxzdXBwb3J0QGNsb3Vkc21pdGguaW8+iQE3
BBMBCAAhBQJgE2lPAhsvBQsJCAcDBRUKCQgLBRYCAwEAAh4BAheAAAoJEDk03evJ
nt4CTUUH/1bK7jRfSruY8fZYvUMP0JW5z7l02xEKmRdG0CmJfYAfwdJqJ48+3Hg7
u32n76LM+o5t9HcBBqEHHXG0UKCn9mqpbQ0b+LJ1VSCiB0V8uRGxSzV6tjYOnS9L
QQvN2XSOuiqzbQe5xljVsu041EFgW0nQPofeUg0daq2hnyKb7au8D358HQTsyG6P
Vs+EaakkwYbeZ88xShq25GAbQCOWuY4WZ2eLbRTa546l5IEgfXCPDg9LsPrOTdbl
xY2KQAY55ao2VUGOItVXIJsP61a/6E4Jjj6E6SeUFGof1GmkSHrrdMwjESq9+WTs
CA6O61FXhz00q1TtTaI5Bb+fsFmH+Hk=
=dmft
-----END PGP PUBLIC KEY BLOCK-----
    EOF

Removing Installation / Uninstalling

If you want to remove the public GPG key for the consensys/teku repository then you can do so by executing the following:

sudo apt-key remove 7663008F7251163434C9E8E53934DDEBC99EDE02

Note: Don't do this if you currently have the repository installed and wish to continue using it. If you remove the key the next fetch will fail.

Viewing Installed Keys

If you want to verify that a GPG public key has been installed or removed, you can view the list of all installed keys by executing:

apt-key list
RedHat logo

RedHat Signing Key Installation

The following instructions are for RedHat (e.g. dnf, rpm, yum, zypper) packages or compatible.

Automated Installation (Bash)

If you installed the consensys/teku repository by following one of the repository installation instructions then you don't need take any further action. The GPG key should already have been installed alongside the repository.

Manual Installation

If you'd like to manually install the GPG key, you can utilise curl to retrieve the GPG key and install it by executing:

rpm --import 'https://artifacts.consensys.net/public/teku/gpg.3934DDEBC99EDE02.key'

Or you can add it directly without curl by executing:

cat > /tmp/consensys-teku.key <<EOF
    -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2
mQENBGATaU8BCACVnthYLXik+G/xVhNQSBjfh1jBVzmbFf//uNLnFQQyqQorlBXW
nVdkizAT6Wej4xgiYfy9NaEVXIkZEiJGPsmtW+/bBx62sfdhNeJDUydEO11E4Pj/
2el3tm2M3OGvLA8RhyMBdyNErJf01CezDnutwTwekR562yJ+YLhfzDbLgO6CtCFW
TwcCLsfXyOwQ3/yjI/v3Cliax4HbYHE68UmyBZD91S/kzXWKiugkcPy9VEMK+/Hc
p2McHOBUxOZoXlnvmaR+jgRUovixyiexgg+iDXcz+5mSpr3BqOCCvN47uOJXMfKV
wbioCGLCdWbfXqkucCRrXlDwjJ2IVo0K/4x1ABEBAAG0O0Nsb3Vkc21pdGggUGFj
a2FnZSAoY29uc2Vuc3lzL3Rla3UpIDxzdXBwb3J0QGNsb3Vkc21pdGguaW8+iQE3
BBMBCAAhBQJgE2lPAhsvBQsJCAcDBRUKCQgLBRYCAwEAAh4BAheAAAoJEDk03evJ
nt4CTUUH/1bK7jRfSruY8fZYvUMP0JW5z7l02xEKmRdG0CmJfYAfwdJqJ48+3Hg7
u32n76LM+o5t9HcBBqEHHXG0UKCn9mqpbQ0b+LJ1VSCiB0V8uRGxSzV6tjYOnS9L
QQvN2XSOuiqzbQe5xljVsu041EFgW0nQPofeUg0daq2hnyKb7au8D358HQTsyG6P
Vs+EaakkwYbeZ88xShq25GAbQCOWuY4WZ2eLbRTa546l5IEgfXCPDg9LsPrOTdbl
xY2KQAY55ao2VUGOItVXIJsP61a/6E4Jjj6E6SeUFGof1GmkSHrrdMwjESq9+WTs
CA6O61FXhz00q1TtTaI5Bb+fsFmH+Hk=
=dmft
-----END PGP PUBLIC KEY BLOCK-----
    EOF
    rpm --import /tmp/consensys-teku.key
    rm -f /tmp/consensys-teku.key

Removing Installation / Uninstalling

If you want to remove the public GPG key for the consensys/teku repository then you can do so by executing the following:

gpgkey=$(rpm -q gpg-pubkey --qf '%{name}-%{version}-%{release} %{summary}\n' | grep "(consensys/teku)" | awk '{ print $1 }')
test ! -z "$gpgkey" && sudo rpm -e --allmatches "$gpgkey"

Note: Don't do this if you currently have the repository installed and wish to continue using it. If you remove the key the next fetch will fail.

Viewing Installed Keys

If you want to verify that a GPG public key has been installed or removed, you can view the list of all installed keys by executing:

rpm -q gpg-pubkey --qf '%{name}-%{version}-%{release} --> %{summary}\n'

What's this page? All Cloudsmith repositories and packages are signed using GPG (or RSA) keys where supported. GPG (or RSA) signatures and checksums provide reliable mechanisms to ensure that the packages that you download/install are neither corrupt nor modified. GPG is generally preferred, but RSA is used for some package formats (such as Alpine). Learn more in the signing keys documentation.

Top