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.
![isc](https://users.cloudsmith.media/avatars/ieCOH3gWZ3uk_ac9d58beb6a3992a5e6cdfe7c4ac30491b7f1530.png)
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/keama is:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2
mQENBF7/AZMBCADE16PM1/OqB0O7gAye2OggIR8Ctj4GlxQzAEWYHb6+XqOp8ox2
WkV6PURCj+FFNM7/UqnhYnqMVKobxl/8OsZ374MJAz5xFr+mSfLecFdiVm2C74yQ
4ETdqRHHBJn7xYC9eDOigDRHh9b5ljUyXtzK1zUj9W8H5iOgAFPasoOOyvfOQPml
hpbfniIf6PKl5ALUZeKzCRK51Up89FNLOPnZTL1uMRlyMxh1Nld/AkGPcejRoFhN
ClA21ZgpK85Ei2YPJWInsyXJnDlara1S+w2bUWdFMxUxmeOdizPb70ono/mcMopg
hYc/d4Tk5LKdOnHrPzZOpPsF7y19SMJpnO7rABEBAAG0NkNsb3Vkc21pdGggUGFj
a2FnZSAoaXNjL2tlYW1hKSA8c3VwcG9ydEBjbG91ZHNtaXRoLmlvPokBNwQTAQgA
IQUCXv8BkwIbLwULCQgHAwUVCgkICwUWAgMBAAIeAQIXgAAKCRAMIXTk6TU1h/Bl
B/4+hueyedP6sy87Adfpbd93xOZ9J3wIW4rv7zr42sKPBqZEP7VbWm8Ecjut3uAp
6sY9yjNQc61UvVN5gu6IFYDz6IfsXFoJ3YgtBBXemcj+uUqEkBifn9YjsZjHTuw6
08hAgabfefF3yzfUgOqeBrdYhzky/T0orceiW7Uan5xfW2tfWJFlPo7ZWJ1c7IND
KwJupgfyUZuTn12deudE/MqDaE+RF3tkMhIxCqGe05L5Fd2O9I8V4d1h8dqdOm5e
LMR4RiyR54jMgPfk7OpV3XeUrb/XfzCBwK2Cp/Oa6uy1KYOfD1qEoLItUDO6Gw71
JWy3asVhGx1WvDsLo69+GR36
=Dawt
-----END PGP PUBLIC KEY BLOCK-----
It has the following long (20 bytes) and short (8 bytes) fingerprints:
97C267507EE814338E7AC0220C2174E4E9353587
0C2174E4E9353587
You can download the GPG key or fetch it via the command-line:
curl -1sLf 'https://dl.cloudsmith.io/public/isc/keama/gpg.0C2174E4E9353587.key'
Public RSA Key
RSA-based keys/signatures are used by:
The public RSA key for the isc/keama is:
-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvlQTA0Xr2hgPX72gM9oC
hP3AaDEwb3yf6TBtxBG1SVadWE6ayZuxHgQGbZxA9ANmgJNdG8gHH2AbZsJWV5s2
FdPp4EFc9Sn9b5BcMIbIrQSDgIsaq2OSnJhG5y3c5qe0CJqTC3QNwrUlyaPSYH95
O94RRxNW5JibbDRFiMPhxQHLl6Jmu3qIhi3DPZ8nFiF4jWtw0hlZkk/5VbKkaObs
4c98KtUP+KefqOJRXN/4zvFqUHY1F/U8vxfw+W/mK2RUtphGXG73ktz9Bhq4hRgW
yjcI+Q/EZCcesbB7srggewW868WNZW+ByxBXTGqzbc+6Clrxwno++Jw3BYEMGMqy
dwIDAQAB
-----END PUBLIC KEY-----
It has the following long (16 bytes) and short (8 bytes) fingerprints:
C5F28DE1F72BE358CAA10F89013460F6
CAA10F89013460F6
You can download the RSA key or fetch it via the command-line:
curl -1sLf 'https://dl.cloudsmith.io/public/isc/keama/rsa.CAA10F89013460F6.key'
Public ECDSA Key
ECDSA-based keys/signatures are used by:
The public ECDSA OpenSSH key for the isc/keama is:
-----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEUW7SHk+caINCBKUryZYU+NfBuNFN
MA5bWRu2GHQ2kRCadcbMfwrRh01YeNHpDWI6YqPhMPVRf1IFHsg32tMAQA==
-----END PUBLIC KEY-----
It has the following long (16 bytes) and short (8 bytes) fingerprints:
E0C20DBC64568B584489436AF6CC5DD9
4489436AF6CC5DD9
You can download the ECDSA key or fetch it via the command-line:
curl -1sLf 'https://dl.cloudsmith.io/public/isc/keama/ecdsa.4489436AF6CC5DD9.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.
![Alpine logo](https://assets.cloudsmith.media/package/images/backends/alpine/large.974a497e9765.png)
Alpine Public Key Installation
The following instructions are for Alpine (e.g. apk) packages or compatible.
Automated Installation (Bash)
If you installed the isc/keama 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 -1sLf 'https://dl.cloudsmith.io/public/isc/keama/rsa.CAA10F89013460F6.key' >/etc/apk/keys/keama@isc-CAA10F89013460F6.rsa.pub
Or you can add it directly without curl by executing:
sudo cat >/etc/apk/keys/keama@isc-CAA10F89013460F6.rsa.pub <<EOF
-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvlQTA0Xr2hgPX72gM9oC
hP3AaDEwb3yf6TBtxBG1SVadWE6ayZuxHgQGbZxA9ANmgJNdG8gHH2AbZsJWV5s2
FdPp4EFc9Sn9b5BcMIbIrQSDgIsaq2OSnJhG5y3c5qe0CJqTC3QNwrUlyaPSYH95
O94RRxNW5JibbDRFiMPhxQHLl6Jmu3qIhi3DPZ8nFiF4jWtw0hlZkk/5VbKkaObs
4c98KtUP+KefqOJRXN/4zvFqUHY1F/U8vxfw+W/mK2RUtphGXG73ktz9Bhq4hRgW
yjcI+Q/EZCcesbB7srggewW868WNZW+ByxBXTGqzbc+6Clrxwno++Jw3BYEMGMqy
dwIDAQAB
-----END PUBLIC KEY-----
EOF
Removing Installation / Uninstalling
If you want to remove the public RSA key for the isc/keama repository then you can do so by executing the following:
sudo rm -f /etc/apk/keys/keama@isc-CAA10F89013460F6.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/
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.