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:
dependency:log4j
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 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.
Raw
consensys
validator-api
develop
One-liner (summary)
Description
| Status | Completed |
|---|---|
| Checksum (MD5) | 80cf5befd4ae823fe0c472fadfa609e6 |
| Checksum (SHA-1) | 0b78943eff368204edc311a18ac57d921e04de53 |
| Checksum (SHA-256) | c4347b34ad80bda6d8542dfcb8b85197e307d5f0bb4b6c2c1079e1559149cb9e |
| Checksum (SHA-512) | ed6bca7b156a5e05cd7fd3a5882ab8ffff8fb09538247bb862accc48a478ffaa51… |
| GPG Signature | |
| Storage Region | Default Region |
| Type | Binary (contains binaries and binary artifacts) |
| Uploaded At | 9 hours ago |
| Uploaded By |
|
| Slug Id | aTIzzalxk2Zq-1mz |
| Unique Id | qqaHKIPXmSdF |
| Version (Raw) | develop |
| Version (Parsed) |
|
| extended metadata | |
| Artifact Id | validator-api |
| Group Id | tech.pegasys.teku.internal |
| Is Snapshot | |
| Packaging | jar |
| Url | https://github.com/ConsenSys/teku |
| dependencies | |
| Checksum (MD5) | 28f36edc270712ebf7b244db660ab1d2 |
| Runtime | com.google.guava:guava >= 31.1-jre | org.apache.commons:commons-lang3 >= 3.12.0 | org.apache.logging.log4j:log4j-api >= 2.19.0 | org.apache.logging.log4j:log4j-core >= 2.19.0 | org.apache.logging.log4j:log4j-slf4j-impl >= 2.19.0 | tech.pegasys.teku.internal:async >= develop | tech.pegasys.teku.internal:bls >= develop | tech.pegasys.teku.internal:bytes >= develop | tech.pegasys.teku.internal:exceptions >= develop | tech.pegasys.teku.internal:execution-types >= develop | tech.pegasys.teku.internal:infrastructure-events >= develop | tech.pegasys.teku.internal:json-types >= develop | tech.pegasys.teku.internal:serializer >= develop | tech.pegasys.teku.internal:spec >= develop | tech.pegasys.teku.internal:unsigned >= develop |
| Compile | org.apiguardian:apiguardian-api >= None | org.assertj:assertj-core >= None | tech.pegasys.teku.internal:validator-api >= develop |
| pkg | validator-api-develop.module |
0
11.8 KB |
md5 | sha1 | sha256 | sha512 | ||
| pkg | validator-api-develop.jar |
0
43.1 KB |
md5 | sha1 | sha256 | sha512 | ||
| pom | validator-api-develop.pom |
0
21.5 KB |
md5 | sha1 | sha256 | sha512 | ||
| sources | validator-api-develop-sources.j… |
0
30.3 KB |
md5 | sha1 | sha256 | sha512 | ||
| test-fixtures | validator-api-develop-test-fixt… |
0
261 bytes |
md5 | sha1 | sha256 | sha512 |
This package doesn't have any files. It might not be an archive.
Security Scanning:
You can't see this because your subscription doesn't include this feature, sorry!
With Security Scanning, Cloudsmith will scan your artefacts for vulnerabilities when they're uploaded. These are then presented to you via the UI and the API, so that you can build rules into your CI/CD pipelines to decide how to handle low, medium, high and critical software vulnerabilities.
If you'd like to trial or ask about the Security Scanning feature, just ask us. We'll be happy to help!
Last scanned
3 hours ago
Scan result
Vulnerable
Vulnerability count
4
Max. severity
Low| Target: | ||
| LOW |
CVE-5713-54994: library: vulnerability titlePackage Name: package_name Installed Version: 1.1.45 Fixed Version: 2.6.8 References: lindsey.com williams.com acevedo.com |
|
| LOW |
CVE-7427-45016: library: vulnerability titlePackage Name: package_name Installed Version: 1.9.85 Fixed Version: 2.10.63 References: www.glover-davis.com elliott.com www.jenkins-ayers.com |
|
| LOW |
CVE-2421-58670: library: vulnerability titlePackage Name: package_name Installed Version: 1.4.97 Fixed Version: 2.2.45 References: perry.info martinez.com www.parker-wilson.com |
|
| LOW |
CVE-8206-69470: library: vulnerability titlePackage Name: package_name Installed Version: 1.1.76 Fixed Version: 2.4.39 References: payne.com www.garcia-adams.org www.smith.info |
|
These instructions assume you have setup the repository first (or read it).
To install/use validator-api @ version develop ...
Then you can then depend on validator-api @ version develop, via:
Add the following to your project pom.xml file:
<dependency>
<groupId>tech.pegasys.teku.internal</groupId>
<artifactId>validator-api</artifactId>
<version>develop</version>
</dependency>dependencies {
implementation 'tech.pegasys.teku.internal:validator-api:develop'
}Note: These examples use the Groovy-based syntax for Gradle. For the Kotlin syntax, please refer to the official documentation for declaring dependencies.
Add the following to your project build.sbt file:
libraryDependencies += "tech.pegasys.teku.internal" % "validator-api" % "develop"Add the following to your project project.clj file:
:dependencies [[tech.pegasys.teku.internal/validator-api "develop"]]For other build systems, such as grape, please consult your build system documentation for more help.