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
license_policy_violated:true
vulnerability_policy_violated:true
Search by repository:
repository:repo-name
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 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 isc/stork is:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2
mQENBF5x71cBCADHT7pQjUSMrms4NkrZFjPmfAZIkKReKlVvhDn/3/h8NBlWPcNS
4YtGp9Wiag9GqGT2jNWLtzlKX2pB3epBwpDH0tJhZjLWNZJVDukynFlzvU5Y40zx
yVagV+HU4I+TkT2KeOkGRaWyq2JY+BGXPI+zGy04c6y/oFYyvonkzJlArZa+Wf9l
10hGkAqlPxDk/oe5QPrFcY2Mj2Sj8hAdKN7XiIc2enJPW4Bkzu+E9NjMekd6w7M+
XXuwsn8JDbee/BafeoJJzCe9kyI7Ve5Iibf6PbTXffASrXE3ikJPfU9SvAeiRW3c
BoTlzwIbhzgVDwAfNB3eGckGNdJsANUPV/M/ABEBAAG0NkNsb3Vkc21pdGggUGFj
a2FnZSAoaXNjL3N0b3JrKSA8c3VwcG9ydEBjbG91ZHNtaXRoLmlvPokBNwQTAQgA
IQUCXnHvVwIbLwULCQgHAwUVCgkICwUWAgMBAAIeAQIXgAAKCRB39k7CgFPR+3cu
CAChG4ZkRJrSVr75edBE7Vu4S/6t3s10mhwr1a2eTY2oIx7/s+zgvFCBcxEYQU41
D36qpDPj1AS71mwV4ONj5AkB2Zk3/9DkdW2wOLgatcCo6xTDbmqSeHYBJEnX0oga
0JOdSq53T6YvxCQ/3D2MLEo+2BC+GBbyoSqNs/hIblbW1afhHWQa7Vzd9pHXWcwY
PAFaBNSwcGyB3CslbzAdY0dwJbstvcbGFzqGTygJqSXciVjvgEg//ZHjMr7eCeX+
0klPIqtJuW6STVJGmrrLdjNQn1IYCzqXKLzw0rBKapnxZLSmJqFfbVjKi3Z7aPGP
XAkZm+OW46kACs+xc6WOoQ5D
=hq/q
-----END PGP PUBLIC KEY BLOCK-----
It has the following long (20 bytes) and short (8 bytes) fingerprints:
7AB5064B08F069A1A5CC500C77F64EC28053D1FB
77F64EC28053D1FB
You can download the GPG key or fetch it via the command-line:
curl -sL ''
Public RSA Key
RSA-based keys/signatures are used by:
The public RSA key for the isc/stork is:
-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA+WaGlu6jR48PBk1/dnLq
J3VfouZWTuhsiekNfGSuxbEnVxWCtWQhisYUdaik1sQrFiILpNRTmuFWM4Bwsj1k
rLkCPZBpNhZQvG7PRdD1tl1rJ729tXZTyXWv1RPg8BgH2oo+UPhyRSCL6O2gZFzo
GSuzIQUnGZ9gTjEG8d0DiEoCe6cwbsWkv9v0yhInPnY77zx8MYT2bfkAIqEjiISs
Rd75Air7kLLK76CnVW9ZCcFtYdx6JsgDpK8UlCvbswMI3GO3EhokoSJMOipL4lbr
I0fVhSID7WZs7w7ueapefWZE/Su+I2vWWb+cjmIidHx9JSkTab0t8m2Vj7FkkPZZ
KwIDAQAB
-----END PUBLIC KEY-----
It has the following long (16 bytes) and short (8 bytes) fingerprints:
419873F0338CB0F16914F776A579B428
6914F776A579B428
You can download the RSA key or fetch it via the command-line:
curl -sL 'https://dl.cloudsmith.io/public/isc/stork/rsa.6914F776A579B428.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.
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.