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
beaconnode
develop
One-liner (summary)
Description
| Status | Completed |
|---|---|
| Checksum (MD5) | 35cd510312929e7a1f1666728f4c8496 |
| Checksum (SHA-1) | 40fddfe9a3d8c91ef18493704c44f790b401e9c4 |
| Checksum (SHA-256) | 745b0796c9d85dda26ffdd85810a0836f1762fc74d1b1805845f3503608cf2bf |
| Checksum (SHA-512) | 67569ceafe46b238e2399b4acd494a499b781c32d900bbce1e2038d838fc34573b… |
| GPG Signature | |
| Storage Region | Default Region |
| Type | Binary (contains binaries and binary artifacts) |
| Uploaded At | 3 hours ago |
| Uploaded By |
|
| Slug Id | qrRd9TumyRnI-hab |
| Unique Id | Lgr7CNCcJKW3 |
| Version (Raw) | develop |
| Version (Parsed) |
|
| extended metadata | |
| Artifact Id | beaconnode |
| Group Id | tech.pegasys.teku.internal |
| Is Snapshot | |
| Packaging | jar |
| Url | https://github.com/ConsenSys/teku |
| dependencies | |
| Checksum (MD5) | ed86f08628ba65932ebfe84e62a54d2f |
| 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 | org.apache.tuweni:tuweni-bytes >= 2.3.1 | tech.pegasys.teku.internal:async >= develop | tech.pegasys.teku.internal:infrastructure-events >= develop | tech.pegasys.teku.internal:json-types >= develop | tech.pegasys.teku.internal:metrics >= develop | tech.pegasys.teku.internal:serializer >= develop | tech.pegasys.teku.internal:spec >= develop | tech.pegasys.teku.internal:time >= develop | tech.pegasys.teku.internal:unsigned >= develop | tech.pegasys.teku.internal:validator-api >= develop |
| Compile | org.apiguardian:apiguardian-api >= None | org.assertj:assertj-core >= None | tech.pegasys.teku.internal:beaconnode >= develop |
| pkg | beaconnode-develop-test-fixture… |
0
261 bytes |
md5 | sha1 | sha256 | sha512 | ||
| pkg | beaconnode-develop.jar |
0
16.6 KB |
md5 | sha1 | sha256 | sha512 | ||
| module | beaconnode-develop.module |
0
10.4 KB |
md5 | sha1 | sha256 | sha512 | ||
| pom | beaconnode-develop.pom |
0
21.3 KB |
md5 | sha1 | sha256 | sha512 | ||
| sources | beaconnode-develop-sources.jar |
0
10.7 KB |
md5 | sha1 | sha256 | sha512 |
This package has 3 files/directories.
|
|
beaconnode |
7 |
|
||
|
|
beaconnode |
0 |
|
||
|
|
beaconnode |
7 |
|
||
|
|
beaconnode |
0 |
|
||
|
|
beaconnode |
0 |
|
||
|
|
beaconnode |
0 |
|
||
|
|
beaconnode |
7 |
|
||
|
|
beaconnode |
0 |
|
||
|
|
beaconnode |
0 |
|
||
|
|
beaconnode |
0 |
|
||
|
|
beaconnode |
0 |
|
||
|
|
beaconnode |
0 |
|
||
|
|
beaconnode |
1 |
|
||
|
|
beaconnode |
2 |
|
||
|
|
beaconnode |
2 |
|
||
|
|
beaconnode |
3 |
|
||
|
|
beaconnode |
3 |
|
||
|
|
beaconnode |
3 |
|
||
|
|
beaconnode |
11 |
|
||
|
|
beaconnode |
7 |
|
Last scanned
3 hours ago
Scan result
Clean
Vulnerability count
0
Max. severity
UnknownThese instructions assume you have setup the repository first (or read it).
To install/use beaconnode @ version develop ...
Then you can then depend on beaconnode @ version develop, via:
Add the following to your project pom.xml file:
<dependency>
<groupId>tech.pegasys.teku.internal</groupId>
<artifactId>beaconnode</artifactId>
<version>develop</version>
</dependency>dependencies {
implementation 'tech.pegasys.teku.internal:beaconnode: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" % "beaconnode" % "develop"Add the following to your project project.clj file:
:dependencies [[tech.pegasys.teku.internal/beaconnode "develop"]]For other build systems, such as grape, please consult your build system documentation for more help.