Package Search Help

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.

Start My Free Trial
 Public consensys consensys (ConsenSys) / teku
Teku: Teku is a Java implementation of the Ethereum 2.0 Beacon Chain.

Maven logo beaconchain  develop

One-liner (summary)

tech.pegasys.teku.internal:beaconchain:develop

Description

No description - See summary for more info.

Size

125.3 KB

Downloads

0

Status  Completed
Checksum (MD5) 8fc69a82e5a13c4edb7614836765f238
Checksum (SHA-1) 42830131bdf722e152dce3c2d6c2a841eb5d4a26
Checksum (SHA-256) d3be1a6bb5e831cbd55456c915b4bea864b4d0ddab4b1bd5a11264ef704fc4de
Checksum (SHA-512) e326ef050a9459a3b95c1a1092fe3a97d044de0fbacbc41a5953106b11c009c41a…
GPG Signature
Storage Region Default Region
Type  Binary (contains binaries and binary artifacts)
Uploaded At 9 hours ago
Uploaded By Uploaded by ops-quorum-sa
Slug Id ebMxlzh4JVT8-wgD
Unique Id 4sUoh4aEhpE5
Version (Raw) develop
Version (Parsed)
  • Type: Unknown
  extended metadata
Artifact Id beaconchain
Group Id tech.pegasys.teku.internal
Is Snapshot
Packaging jar
Url https://github.com/ConsenSys/teku
  dependencies
Checksum (MD5) 389d4489503ac5111d7120531f8f4b97
Runtime com.google.guava:guava >= 31.1-jre | io.libp2p:jvm-libp2p-minimal >= 0.10.0-RELEASE | 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:api >= develop | tech.pegasys.teku.internal:async >= develop | tech.pegasys.teku.internal:beaconrestapi >= develop | tech.pegasys.teku.internal:client >= develop | tech.pegasys.teku.internal:eth2 >= develop | tech.pegasys.teku.internal:ethereum-events >= develop | tech.pegasys.teku.internal:exceptions >= develop | tech.pegasys.teku.internal:execution-types >= develop | tech.pegasys.teku.internal:executionclient >= develop | tech.pegasys.teku.internal:executionlayer >= develop | tech.pegasys.teku.internal:http >= develop | tech.pegasys.teku.internal:infrastructure-events >= develop | tech.pegasys.teku.internal:io >= develop | tech.pegasys.teku.internal:logging >= develop | tech.pegasys.teku.internal:metrics >= develop | tech.pegasys.teku.internal:networks >= develop | tech.pegasys.teku.internal:p2p >= develop | tech.pegasys.teku.internal:pow >= develop | tech.pegasys.teku.internal:powchain >= develop | tech.pegasys.teku.internal:provider >= develop | tech.pegasys.teku.internal:serviceutils >= develop | tech.pegasys.teku.internal:spec >= develop | tech.pegasys.teku.internal:ssz >= develop | tech.pegasys.teku.internal:statetransition >= develop | tech.pegasys.teku.internal:storage >= develop | tech.pegasys.teku.internal:storage-api >= develop | tech.pegasys.teku.internal:sync >= develop | tech.pegasys.teku.internal:timer >= develop | tech.pegasys.teku.internal:unsigned >= develop | tech.pegasys.teku.internal:validator >= develop | tech.pegasys.teku.internal:validator-api >= develop | tech.pegasys.teku.internal:version >= develop | tech.pegasys.teku.internal:weaksubjectivity >= develop
Compile org.apiguardian:apiguardian-api >= None | org.assertj:assertj-core >= None | tech.pegasys.teku.internal:beaconchain >= develop
pkg beaconchain-develop.module 0
24.8 KB
md5 sha1 sha256 sha512
pkg beaconchain-develop.jar 0
48.4 KB
md5 sha1 sha256 sha512
pom beaconchain-develop.pom 0
25.9 KB
md5 sha1 sha256 sha512
sources beaconchain-develop-sources.jar 0
26.0 KB
md5 sha1 sha256 sha512
test-fixtures beaconchain-develop-test-fixtur… 0
261 bytes
md5 sha1 sha256 sha512
Package Contents (beaconchain-develop.module)

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

2 days, 20 hours ago

Scan result

Vulnerable

Vulnerability count

2

Max. severity

Medium
Target:
MEDIUM

CVE-6584-22694: library: vulnerability title



Package Name: package_name
Installed Version: 1.4.65
Fixed Version: 2.9.14

References: www.riley.net www.acevedo.info www.nelson-foster.com
LOW

CVE-2533-43704: library: vulnerability title



Package Name: package_name
Installed Version: 1.8.35
Fixed Version: 2.7.82

References: wagner-olsen.info shepard.com potts.com
Loading...

These instructions assume you have setup the repository first (or read it).

To install/use beaconchain @ version develop ...

Then you can then depend on beaconchain @ version develop, via:

Add the following to your project pom.xml file:

<dependency>
  <groupId>tech.pegasys.teku.internal</groupId>
  <artifactId>beaconchain</artifactId>
  <version>develop</version>
</dependency>
dependencies {
  implementation 'tech.pegasys.teku.internal:beaconchain: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" % "beaconchain" % "develop"

Add the following to your project project.clj file:

:dependencies [[tech.pegasys.teku.internal/beaconchain "develop"]]

For other build systems, such as grape, please consult your build system documentation for more help.

Top