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.
![thinedge](https://users.cloudsmith.media/avatars/KuKpj2Ev2a7T_1d263257ccd9f074f78b6960438042d8a321fa00.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 thinedge/tedge-release is:
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQGNBGPZHCIBDACuCZ2xfB85bn1jJtZz1uouZbojPL9kx8uPfsqIU3f//L1DlVqO
QqYjeNoPyDDR2/+lRAetq5s5SmhkaoDhX2uNeLXaXj6G1DXzjDVJVT6CAEyYuMf8
u8cWfAszWbyjM7ALVP1Eeg0EnwGfRxe1fd+SE9tVKue4FJTcCUpIacLfwPpJQGn+
l5Aq8e4oYsr3s3C2S6k+MaRHsNqhxoslEGP3bSpH7g/jFtXicXTA40nj1T1/Zwae
2cw8Gq5OTfNrA+9KRHalB/4tHNeeqOzPlvHIMH62DrGKkh13iUN0BSg5g/xgH78I
DxjJNTVuNReNSbhihjsRq3wjOOlhHVkP7fxW5JDZccvBeWfxNTiRD5AmG7qFVw3N
ET+jo0T+tdrVnu3EMgIZK0ghc3VusxVgOKsmGAUQgYhpU1X+7HYoTSP0LE/WF6SX
N55E6KqejSnQD8VWUW7W9jxXgZyKtAWr++E+aUat0s5k9E3EDxTt94hydckWc7Fu
hp5OoZeyRnKfkDMAEQEAAbQ7Q2xvdWRzbWl0aCBQYWNrYWdlICh0aGluZWRnZS90
ZWRnZSkgPHN1cHBvcnRAY2xvdWRzbWl0aC5pbz6JAc4EEwEIADgWIQQjtkWoCxRt
HpxdQ4IxWYxU4s1UEAUCY9kcIgIbLwULCQgHAwUVCgkICwUWAgMBAAIeAQIXgAAK
CRAxWYxU4s1UEAbLC/9b5n26I6mX8l+NeZXSgbjX6l2s0wJdUibLvbha+sXoX3ep
n9iE8/H2jkooQJmT7SoVgDst3v/ontFFj8asKnpigXORqu9J0g07IjjoYIGip8Mc
njjm3ImJZUUMo86eRQvM/z+6LBTv4mMGCewhkyH46izn/9xMmbMHhxVKGkxQrzOb
ZcsMIWD+jH4EcbzRPxpkEUu3AdwezF6ysYvne3jWWhiA6n/MFVGLHOST9ZIoImiV
/AfAyReitFplVkVQ+KyvETad1POWGxT611yuWytggOW9Ybn2Vdbvl5HRhmwwGLfJ
nvZKnkz94OfeXtpZJKOYW7wbgK7UBfhBxQsIYeseb02wv5/k5xaqG/HK8bdzpXSY
9X/acFQOS3EyqV8o1iRdnzL2xJ/5EfhaLERFjBI1ll0sP3KunHMgOBapTrUmKQMe
grxRFdROImqoL5u2yBbY/f89qkyViekQmhTITdV0cqvB5LtLjAQEnCeUnj6Szy90
GKX8hKSnbJJ5R48hnWk=
=IMZY
-----END PGP PUBLIC KEY BLOCK-----
It has the following long (20 bytes) and short (8 bytes) fingerprints:
23B645A80B146D1E9C5D438231598C54E2CD5410
31598C54E2CD5410
You can download the GPG key or fetch it via the command-line:
curl -1sLf 'https://dl.cloudsmith.io/public/thinedge/tedge-release/gpg.31598C54E2CD5410.key'
Public RSA Key
RSA-based keys/signatures are used by:
The public RSA key for the thinedge/tedge-release is:
-----BEGIN PUBLIC KEY-----
MIIBojANBgkqhkiG9w0BAQEFAAOCAY8AMIIBigKCAYEAoouCmtOyfY5dPc88w/GE
qs6ir0HaFgrTKkIyV76MkyZTjem4Mykq5C+naKYbkIXSbz4taIhlbfysK0fyAN/1
TmEzQSOkxHERc7ISrPtyTnGn4hCe2ZIubD4yZUkKQ72hEZFnFTLTQHYOv2+514BX
9Eipgg8zQThAUp2KSbiU7krl8s7O/PVpHwEyIQlQP5GTw05MuHOiVaEky9/WgU1W
ROik/wmcp4HtBQ/zGCB5rqTHv/wmRzFG++NiZPNzi1E6TaWHz4EXb3yUFBM0w+UH
oMtju3y2HkFckqB9pEuh8tK/RadhXq+Zz7ekglnLEAjsYYQ9vyTMeILXnANDzVYW
z4e8Qy0iwohxOLYgZ8buIRfP4O9bkTLkVo/Z/WmcBjyLF0A1fdOsr32qRn4n4rXV
HMPS2e7nDLWKEsqT2TmE+LNFdaHSghnrYczIk6wjV88au9PS6bDFStumeY5Fy83c
ry7jt5LqnITP9NBQbCKd2rDbfqCFR2r1oLQZohXqeEaXAgMBAAE=
-----END PUBLIC KEY-----
It has the following long (16 bytes) and short (8 bytes) fingerprints:
56D1F66F92229CBEB040C349649537E6
B040C349649537E6
You can download the RSA key or fetch it via the command-line:
curl -1sLf 'https://dl.cloudsmith.io/public/thinedge/tedge-release/rsa.B040C349649537E6.key'
Public ECDSA Key
ECDSA-based keys/signatures are used by:
The public ECDSA OpenSSH key for the thinedge/tedge-release is:
-----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAERMhHfO8MNIg2+xQwJ8g096h/O45s
dyhxu2UGZUMQh+E1gVy5XruQTsfROEpeKhn6XMbbqbPdCp9b0m7R0XYgrw==
-----END PUBLIC KEY-----
It has the following long (16 bytes) and short (8 bytes) fingerprints:
08768A692BD2176500495DF83A98C7E1
00495DF83A98C7E1
You can download the ECDSA key or fetch it via the command-line:
curl -1sLf 'https://dl.cloudsmith.io/public/thinedge/tedge-release/ecdsa.00495DF83A98C7E1.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 thinedge/tedge-release 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/thinedge/tedge-release/rsa.B040C349649537E6.key' >/etc/apk/keys/tedge-release@thinedge-B040C349649537E6.rsa.pub
Or you can add it directly without curl by executing:
sudo cat >/etc/apk/keys/tedge-release@thinedge-B040C349649537E6.rsa.pub <<EOF
-----BEGIN PUBLIC KEY-----
MIIBojANBgkqhkiG9w0BAQEFAAOCAY8AMIIBigKCAYEAoouCmtOyfY5dPc88w/GE
qs6ir0HaFgrTKkIyV76MkyZTjem4Mykq5C+naKYbkIXSbz4taIhlbfysK0fyAN/1
TmEzQSOkxHERc7ISrPtyTnGn4hCe2ZIubD4yZUkKQ72hEZFnFTLTQHYOv2+514BX
9Eipgg8zQThAUp2KSbiU7krl8s7O/PVpHwEyIQlQP5GTw05MuHOiVaEky9/WgU1W
ROik/wmcp4HtBQ/zGCB5rqTHv/wmRzFG++NiZPNzi1E6TaWHz4EXb3yUFBM0w+UH
oMtju3y2HkFckqB9pEuh8tK/RadhXq+Zz7ekglnLEAjsYYQ9vyTMeILXnANDzVYW
z4e8Qy0iwohxOLYgZ8buIRfP4O9bkTLkVo/Z/WmcBjyLF0A1fdOsr32qRn4n4rXV
HMPS2e7nDLWKEsqT2TmE+LNFdaHSghnrYczIk6wjV88au9PS6bDFStumeY5Fy83c
ry7jt5LqnITP9NBQbCKd2rDbfqCFR2r1oLQZohXqeEaXAgMBAAE=
-----END PUBLIC KEY-----
EOF
Removing Installation / Uninstalling
If you want to remove the public RSA key for the thinedge/tedge-release repository then you can do so by executing the following:
sudo rm -f /etc/apk/keys/tedge-release@thinedge-B040C349649537E6.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.