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.
Format-Specific Setup
To find out how to get setup locally so you can easily install packages, please select one of the formats from the tabs above.
Please note that the term repository here is Cloudsmith's concept of a package or artifact collection, and should not be confused with other package format specific meanings (such as the term as it is used by Docker, to mean a tagged image).
Note: Only help for package formats that exist in this repository is shown. You can also see the help for all package formats.
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 Repository Setup
Alpine is the package manager of choice for Alpine Linux distributions.
The following instructions are for Alpine or compatible packages only.
Distribution Setup
To install packages, you can quickly setup the repository automatically (recommended):
sudo apk add --no-cache bash
curl -1sLf \
'https://dl.cloudsmith.io/public/isc/stork/setup.alpine.sh' \
| sudo -E bash
If you need to force a specific distribution, release/version, or architecture, you can also do that (e.g. if your system is compatible but not identical):
sudo apk add --no-cache bash
curl -1sLf \
'https://dl.cloudsmith.io/public/isc/stork/setup.alpine.sh' \
| sudo -E distro=DISTRO codename=CODENAME arch=ARCH bash
or ... you can manually configure it yourself before installing packages:
curl -1sLf 'https://dl.cloudsmith.io/public/isc/stork/rsa.6914F776A579B428.key' > /etc/apk/keys/stork@isc-6914F776A579B428.rsa.pub
curl -1sLf 'https://dl.cloudsmith.io/public/isc/stork/config.alpine.txt?distro=alpine&codename=v3.8' >> /etc/apk/repositories
apk update
Note: Please replace v3.8 above with your actual distribution version.
Removing Setup
If you no longer want to install packages from the repository, you can remove it with:
$EDITOR /etc/apk/repositories
Remove /alpine/v3.8/main
line, save then execute:
rm -f /etc/apk/keys/stork@isc-6914F776A579B428.rsa.pub
apk update
Note: Please replace v3.8 above with your actual distribution version.
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.
Debian Repository Setup
Apt/Dpkg is the package manager of choice for Debian-like systems (such as Ubuntu, Linux Mint, Raspbian, etc.)
The following instructions are for Debian or compatible packages only.
Distribution Setup
To install packages, you can quickly setup the repository automatically (recommended):
curl -1sLf \
'https://dl.cloudsmith.io/public/isc/stork/setup.deb.sh' \
| sudo -E bash
If you need to force a specific distribution, release/version, architecture, or component (if supported), you can also do that (e.g. if your system is compatible but not identical):
curl -1sLf \
'https://dl.cloudsmith.io/public/isc/stork/setup.deb.sh' \
| sudo -E distro=DISTRO codename=CODENAME arch=ARCH component=COMPONENT bash
or ... you can manually configure it yourself before installing packages:
apt-get install -y debian-keyring # debian only
apt-get install -y debian-archive-keyring # debian only
apt-get install -y apt-transport-https
# For Debian Stretch, Ubuntu 16.04 and later
keyring_location=/usr/share/keyrings/isc-stork-archive-keyring.gpg
# For Debian Jessie, Ubuntu 15.10 and earlier
keyring_location=/etc/apt/trusted.gpg.d/isc-stork.gpg
curl -1sLf 'https://dl.cloudsmith.io/public/isc/stork/gpg.77F64EC28053D1FB.key' | gpg --dearmor >> ${keyring_location}
curl -1sLf 'https://dl.cloudsmith.io/public/isc/stork/config.deb.txt?distro=ubuntu&codename=xenial&component=main' > /etc/apt/sources.list.d/isc-stork.list
sudo chmod 644 ${keyring_location}
sudo chmod 644 /etc/apt/sources.list.d/isc-stork.list
apt-get update
Note: Please replace ubuntu, xenial and main above with your actual operating system (distribution and distribution release/version) and components (based on what's in this repository).
Removing Setup
If you no longer want to install packages from the repository, you can remove it with:
rm /etc/apt/sources.list.d/isc-stork.list
apt-get clean
rm -rf /var/lib/apt/lists/*
apt-get update
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.
RedHat Repository Setup
A repository for RedHat-like systems (such as RHEL, CentOS, SUSE, Fedora, etc.), compatible with yum, dnf, zypper, etc.
The following instructions are for RedHat or compatible packages only.
Distribution Setup
To install packages you'll need to setup your repository, which is specific to your distribution:
To install packages, you can quickly setup the repository automatically (recommended):
curl -1sLf \
'https://dl.cloudsmith.io/public/isc/stork/setup.rpm.sh' \
| sudo -E bash
If you need to force a specific distribution, release/version, or architecture, you can also do that (e.g. if your system is compatible but not identical):
curl -1sLf \
'https://dl.cloudsmith.io/public/isc/stork/setup.rpm.sh' \
| sudo -E distro=DISTRO codename=CODENAME arch=ARCH bash
or ... you can manually configure it yourself before installing packages:
yum install yum-utils pygpgme
rpm --import 'https://dl.cloudsmith.io/public/isc/stork/gpg.77F64EC28053D1FB.key'
curl -1sLf 'https://dl.cloudsmith.io/public/isc/stork/config.rpm.txt?distro=el&codename=7' > /tmp/isc-stork.repo
yum-config-manager --add-repo '/tmp/isc-stork.repo'
yum -q makecache -y --disablerepo='*' --enablerepo='isc-stork'
Note: Please replace el and 7 above with your actual distribution/version and use Wildcards when enabling multiple repos.
To install packages, you can quickly setup the repository automatically (recommended):
curl -1sLf \
'https://dl.cloudsmith.io/public/isc/stork/setup.rpm.sh' \
| sudo -E bash
If you need to force a specific distribution, release/version, or architecture, you can also do that (e.g. if your system is compatible but not identical):
curl -1sLf \
'https://dl.cloudsmith.io/public/isc/stork/setup.rpm.sh' \
| sudo -E distro=DISTRO codename=CODENAME arch=ARCH bash
or ... you can manually configure it yourself before installing packages:
dnf install yum-utils pygpgme
rpm --import 'https://dl.cloudsmith.io/public/isc/stork/gpg.77F64EC28053D1FB.key'
curl -1sLf 'https://dl.cloudsmith.io/public/isc/stork/config.rpm.txt?distro=fedora&codename=29' > /tmp/isc-stork.repo
dnf config-manager --add-repo '/tmp/isc-stork.repo'
dnf -q makecache -y --disablerepo='*' --enablerepo='isc-stork' --enablerepo='isc-stork-source'
Note: Please replace fedora and 29 above with your actual distribution/version.
To install packages, you can quickly setup the repository automatically (recommended):
curl -1sLf \
'https://dl.cloudsmith.io/public/isc/stork/setup.rpm.sh' \
| sudo -E bash
If you need to force a specific distribution, release/version, or architecture, you can also do that (e.g. if your system is compatible but not identical):
curl -1sLf \
'https://dl.cloudsmith.io/public/isc/stork/setup.rpm.sh' \
| sudo -E distro=DISTRO codename=CODENAME arch=ARCH bash
or ... you can manually configure it yourself before installing packages:
microdnf upgrade microdnf # v3.8+ required to use makecache
rpm --import 'https://dl.cloudsmith.io/public/isc/stork/gpg.77F64EC28053D1FB.key'
curl -1sLf 'https://dl.cloudsmith.io/public/isc/stork/config.rpm.txt?distro=almalinux&codename=8.4' > /etc/yum.repos.d/isc-stork.repo
microdnf makecache -y --disablerepo='*' --enablerepo='isc-stork*'
Note: Please replace almalinux and 8.4 above with your actual distribution/version.
To install packages, you can quickly setup the repository automatically (recommended):
curl -1sLf \
'https://dl.cloudsmith.io/public/isc/stork/setup.rpm.sh' \
| sudo -E bash
If you need to force a specific distribution, release/version, or architecture, you can also do that (e.g. if your system is compatible but not identical):
curl -1sLf \
'https://dl.cloudsmith.io/public/isc/stork/setup.rpm.sh' \
| sudo -E distro=DISTRO codename=CODENAME arch=ARCH bash
or ... you can manually configure it yourself before installing packages:
curl -1sLf 'https://dl.cloudsmith.io/public/isc/stork/config.rpm.txt?distro=opensuse&codename=42.2' > /tmp/isc-stork.repo
zypper ar -f '/tmp/isc-stork.repo'
zypper --gpg-auto-import-keys refresh isc-stork isc-stork-source
Note: Please replace opensuse and 42.2 above with your actual distribution/version.
Removing Setup
If you no longer want to install packages from the repository, you can remove it with:
rm /etc/yum.repos.d/isc-stork.repo
rm /etc/yum.repos.d/isc-stork-source.repo
rm /etc/yum.repos.d/isc-stork.repo
rm /etc/yum.repos.d/isc-stork-source.repo
rm /etc/yum.repos.d/isc-stork.repo
zypper rr isc-stork
zypper rr isc-stork-source
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? You can always download packages from Cloudsmith manually, but native package manager setup allows you to simplify and automate downloads. A native package manager has intelligence built-in that allows it to understand concepts like metadata, versioning, duplication, convergence, etc. As such, we will always recommend that you install natively where possible. Learn more in the setup documentation.