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 # of 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/version:
dependency:log4j
dependency:log4j=1.0.0
dependency:log4j>1.0.0
Search by uploaded date:
uploaded:>"1 day ago"
uploaded:<"August 14, 2022 EST"
Search by entitlement token (identifier):
entitlement:3lKPVJPosCsY
Search by policy violation:
policy_violated:true
deny_policy_violated:true
license_policy_violated:true
vulnerability_policy_violated:true
Search by repository:
repository:repo-name
Search queries for all Debian-specific (and related) package types
Search by component:
deb_component:unstable
Search queries for all Maven-specific (and related) package types
Search by group ID:
maven_group_id:org.apache
Search queries for all Docker-specific (and related) package types
Search by image digest:
docker_image_digest:sha256:7c5..6d4
(full hashref only)
Search by layer digest:
docker_layer_digest:sha256:4c4..ae4
(full hashref only)
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 or version 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,
Hex,
LuaRocks,
Maven,
npm,
NuGet,
P2,
Python,
RedHat,
Ruby,
Swift,
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.

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 keys/signatures are used by:
The public GPG key for the kong/kuma-binaries-release is:
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQGNBGSTcdcBDAC6d0Dzai5V6bae6UyHco4iQHCfgAg8mcn4QrmOxSwjBcVWDUqN
YePusdJILcMP65uNVtz+mq6EGomozeIytOxUnowmGqYrlYrZFJ80NScUKZh56Y0C
c/FbtU4kSX6Y1vZqOytmoArB1Ro64JsTJMalBODT6foTE2rtB4Ghwx5DePI+RxQA
RY7FixTocWVZTkEZZ0nHJueZPxURQOkl0AVHPPykM6u1Jo1sK5Xhgmg8HaNpqhju
e4NQ9ASyg2NnYtEe6IVRhi6ReQyUpIEwoJNhbCOcoUxA5ZldH3zUnq1Bqu1zNU2V
kd1yFbLHrKO2lEUOEkXFYhlNICFU5vAT01d9nnUE94KS0AoCvY6UurHC5qkipTsh
j+N4zJM8Zg+Pgm2AWmcOZule36ThczdSxe0+1QLMM3B14CSTuS2tTtI2H89ln2il
6AnUZYIBPCwSRW5xGKmG/Xn3sJy921xl/gNC9ecPn7Y0PNHYgiodESr/dztRW97v
TsDcQguXdssoS5MAEQEAAbRHQ2xvdWRzbWl0aCBQYWNrYWdlIChrb25nL2t1bWEt
YmluYXJpZXMtcmVsZWFzZSkgPHN1cHBvcnRAY2xvdWRzbWl0aC5pbz6JAc4EEwEI
ADgWIQRzMtYnp3Cq7P+vcI2lo4pe6XBojwUCZJNx1wIbLwULCQgHAwUVCgkICwUW
AgMBAAIeAQIXgAAKCRClo4pe6XBojwpdC/0UEaU8cHPf1MBoUzua9bWWUuny/8gV
8njIzT3PffYiVRDO9Cdsr3mu8vwt/bDSSq1f/IWZ1pbdADhDAf37XSMvx0sYnCw9
0rwU743spClbdgdoYacStOYXp5cKrgifchye0tFfDrqKPS46xKxtINXKa6YdI0Ew
/RRCTVxAtHZ6IrvDXcnawi8xODvzK5a9OcEKJAdTqrDnpDmxCRMvauEXv06XXGGa
wv4eO3PIhHx7cVOH13bW2CGH0TVoIcCNad24JvCTEcjTr0CeAIDFLmZETT38pjfq
upYBwZLwlx5WvTUSdwDwFNbwa6d6+wb7spVMy2ajEK8bj7jWqQoFhrJxHSsGUsfM
lk/x8WvLuON1PJgQ1jdbeskMLUTkhDlJMxb1TAxkcCp2/L8QgjQvc9m4OC52VUCZ
Jc8QphQ/Zw92gqiV6DhBYkDWbHEDy/h/RdQJg7km6VOKKn1KCrdr9PtSctPDMxGu
T+KTQqgjcUe9vCGzW8oHLa1d9m9bieilWjs=
=ZM6N
-----END PGP PUBLIC KEY BLOCK-----
It has the following long (20 bytes) and short (8 bytes) fingerprints:
7332D627A770AAECFFAF708DA5A38A5EE970688F
A5A38A5EE970688F
You can download the GPG key or fetch it via the command-line:
curl -1sLf 'https://packages.konghq.com/public/kuma-binaries-release/gpg.A5A38A5EE970688F.key'
Public RSA Key
RSA-based keys/signatures are used by:
The public RSA key for the kong/kuma-binaries-release is:
-----BEGIN PUBLIC KEY-----
MIIBojANBgkqhkiG9w0BAQEFAAOCAY8AMIIBigKCAYEAhtHoew7DQQBz3SUcY3uk
XcyGr0AZtVhDlVXdN5kgLhNMWXCrn1qSZ8i1DjhDA6U9et77JHYlG0OaK/8ic/N/
fmcrtEN3cFABZbcg54GZxs4C/QuH2t9qmVuqrGYUJUfJT1QHEAGfyOBdzP8w0qkZ
M8oV82IeoZcmSgh1NJtU8JOtqsWZsYNkmctD52tIJRSX4fKfyR4dHc2uTpACzjOY
GjBTcg5sm3BmvbdxSQfATgOcIvSfhb+qUqqhHGCM0hi2h+JDCADCb7A4tz6pqtAx
GJo7zl7muVb/s0lx+0OGY7PtowUI+FuWyv4o8UMoTYX2V03ViUsKUehxQmhe7ZXA
sL/bA5yyXAfrOAI9+fEdGS151HYw5TI4neJm5yRdsygSSzz+QrBef0XfFMqNgmyL
WOvJrlg0ClnH9+I8iFjUNfPnlNoVI5Er4Vb1t0PpoLv4IVFjWO8xOWD0Za2ltX5n
XQOjQPDfrNQasqhqeSCMlDpK340tTVz+jSLOF6nod1zhAgMBAAE=
-----END PUBLIC KEY-----
It has the following long (16 bytes) and short (8 bytes) fingerprints:
AC1D5B445C47BA3B6883629A44D2375E
6883629A44D2375E
You can download the RSA key or fetch it via the command-line:
curl -1sLf 'https://packages.konghq.com/public/kuma-binaries-release/rsa.6883629A44D2375E.key'
Public ECDSA Key
ECDSA-based keys/signatures are used by:
The public ECDSA OpenSSH key for the kong/kuma-binaries-release is:
-----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEwXfRRvyJPS4Cti4KsRXfMUCUodx9
+nLPCBISEMyU21HazcOme4CNmbyt4MuLlsI3neYipLnXamkx/+4ZHj65kg==
-----END PUBLIC KEY-----
It has the following long (16 bytes) and short (8 bytes) fingerprints:
F5E66D92922EA433CEEF8F12C9204A9D
CEEF8F12C9204A9D
You can download the ECDSA key or fetch it via the command-line:
curl -1sLf 'https://packages.konghq.com/public/kuma-binaries-release/ecdsa.CEEF8F12C9204A9D.key'
Please note however that the NPM client does not require this key to be installed system-wide in order to allow for package verification - NPM tooling will handle keys automatically.
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.
What's this page? All Cloudsmith repositories and packages are signed using GPG, RSA or ECDSA keys where supported. 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 or ECDSA is used for some package formats (such as Alpine or NPM). Learn more in the signing keys documentation.