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/version:
dependency:log4j
dependency:log4j=1.0.0
dependency:log4j>1.0.0
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 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,
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.
consensys
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 consensys/binaries is:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2
mQENBF+SWEwBCADADS22oRMgaNMV++ulVsUzZKmsOBk4XJgCU/UWkwl9F/CBNi5F
0JHVWqVOZkprnJ9CqOL8IDvM3261HmrX2zVhjyB9d7JOISyEVHy9aMBpOxeqExUY
8x1J0cg2z+kFJO4CbdHBY1SsxK2diolV43YM7e/4SvP+MTHppc9NJ9dvsuedfNR/
jhAQHb4P4+wId+Na1XJflXmn1BMzpPtGh7D0ZNfUh+9ofMtFnlPzojjwDYeUNq7i
MvqyLzd7OcNTHVTdpWAUDWhx2QciTDYf4SEGCp47auCZwzCfdeNoxpe6PGTeP0b4
sFVHsqQDqvMn39qp/LFuCeWR9dpUjAe1IbPVABEBAAG0P0Nsb3Vkc21pdGggUGFj
a2FnZSAoY29uc2Vuc3lzL2JpbmFyaWVzKSA8c3VwcG9ydEBjbG91ZHNtaXRoLmlv
PokBNwQTAQgAIQUCX5JYTAIbLwULCQgHAwUVCgkICwUWAgMBAAIeAQIXgAAKCRDx
tQQMmrMe9GpKB/4gBglFf6Ky8cgFM3k+fRvhOAM5HaZE2erVSISU4Giv9E+v7HzD
rNZrkIZY7xiZqV6p9qGVoeKxSQpEt88k/IL1ousEUD0PY/Uk4FSQhXsWDoI/Ojkh
QRh6HleKM2reN1p5uUfixeLkRZdAzPT7WlaTPOmeoLXv4m5EQT0LzchvQfiICHvy
SDrsCx8+kJvF0u2g7W3ORV31bVQ48Scl/xuOIB8Mn6kJSxrvPgG/RNxKhBTMxd/w
aox/WpL4MELeFk83mRwjdlS4MAT60DYoueFghcB/uLw7UT8jwriwMuHCRIl7vNsZ
rEBKHZB+yhme0OX2Ilel/q8FFWoWnBoqUDsB
=le8U
-----END PGP PUBLIC KEY BLOCK-----It has the following long (20 bytes) and short (8 bytes) fingerprints:
498B2AA5C1CA043CC54DD599F1B5040C9AB31EF4F1B5040C9AB31EF4You can download the GPG key or fetch it via the command-line:
curl -sL 'https://artifacts.consensys.net/public/binaries/gpg.F1B5040C9AB31EF4.key'Public RSA Key
RSA-based keys/signatures are used by:
The public RSA key for the consensys/binaries is:
-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA7nXj6OOOvnMeXvmfVrb0
W2k7TZIBdt83MS3c7HRec8dumuc78sG+EzcuiYI4YNNWGtyGi0QasgiV6dgMHjxG
zArBmW7Q+PnMS3NNbdxiWMwn8P7xezIzHqUm33PNvwBQUiGN7bH4Bta6uV+MwKk5
IPHKX3wALozm8v6G+1E4XIjItEtTdRdeR9FxdgQlmtm5AeqCnXFT7haV7suL+ppj
EnW4/oKNyO1rk/iWL0Iu2EQD0zuw+gOAtJkEC/VXh0gXfGzpdFdbY5pl1KRTac1N
2cbzyIf2zegaWtD2bC30MMWYXxPRkj3loyqor3ofPJ0t85ykSkuDQoKjKM6VXFC2
wQIDAQAB
-----END PUBLIC KEY-----It has the following long (16 bytes) and short (8 bytes) fingerprints:
C50D4C2A5C6CAE68DF897FF94E80B553DF897FF94E80B553You can download the RSA key or fetch it via the command-line:
curl -sL 'https://artifacts.consensys.net/public/binaries/rsa.DF897FF94E80B553.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.