Download JAR files tagged by https with all dependencies

# heatshrink-java Java library used to encode/decode [heatshrink](https://github.com/atomicobject/heatshrink) compressed data. ## Building ```bash ./gradlew build ``` ## Gradle dependency See https://search.maven.org/artifact/io.github.markrileybot/heatshrink-java/ ## Usage ### Java library ```java int windowSize = 9; int lookaheadSize = 8; ByteArrayOutputStream baos = new ByteArrayOutputStream(); try(HsOutputStream out = new HsOutputStream(baos, windowSize, lookaheadSize)) { out.write("ABCABCABCABCABCABC".getBytes()); } try(HsInputStream hsi = new HsInputStream(new ByteArrayInutStream(baos.toByteArray()), windowSize, lookaheadSize)) { byte[] res = new byte[512]; int len = hsi.read(res); System.out.println(new String(res, 0, len)); } ``` ### CLI ```bash $ java -jar heatshrink-java-exe.jar [-h] [-e|-d] [-v] [-w SIZE] [-l BITS] [IN_FILE] [OUT_FILE] ``` ## Status [](https://github.com/markrileybot/heatshrink-java/actions/workflows/gradle-publish.yml) [](https://coveralls.io/github/markrileybot/heatshrink-java?branch=master) [](https://maven-badges.herokuapp.com/maven-central/io.github.markrileybot/geokey)

The Attribution Maven Plugin is a tool for producing information about a project's dependencies, in a way that can be consumed by external reporting tools. It currently leverages the Maven Project Info Reports Plugin (https://maven.apache.org/components/plugins/maven-project-info-reports-plugin/) to obtain all of a project's data, and then output the information to an XML file, such as: target/attribution.xml. This plugin came from the need to get some of the same information produced by the Maven Project Info Reports Plugin, and have it ready to be consumed by tools which may require input in a certain format, such as a CSV. By producing an attribution XML file, scripts can be created to translate the data into these other consumable formats.

Provide interactive issue reporting in your Android application. Application users can take record the screen and speak their issues, take screenshots, making it easier to submit issues. Issues are created in your Jira or Azure Boards. The created issues are actionable as it has all the context required to understand and fix them. E.g. screenshot, screen recording, device diagnostics (logs, OS version, device manufacturer and so on. Visit https://support.redpen.ai/hc/en-us/articles/5579906622093-How-to-integrate-Redpen-Android-SDK-into-your-application for the instructions on how to integrate Redpen Capture Widget into your Android application.

The AppOptics Java instrumentation agent jar file. This artifact provides a convenient way to download the agent jar from public Maven repository. Please take note that this should NOT be included as a part of the project dependencies. Rather, this artifact should be integrated into the build process by using extra step such as the "copy" goal of "maven-dependency-plugin". For more information, please refer to https://docs.appoptics.com/kb/apm_tracing/java/install/#getting-the-agent-jar

Azure Video Analyzer provides a platform to build intelligent video applications that span the edge and the cloud. The platform offers the capability to capture, record, and analyze live videos along with publishing the results, video, and video analytics, to Azure services in the cloud or the edge. It is designed to be an extensible platform, enabling you to connect different video analysis edge modules such as Cognitive services containers, custom edge modules built by you with open-source machine learning models or custom models trained with your own data. You can then use them to analyze live video without worrying about the complexity of building and running a live video pipeline. Use the client library for Video Analyzer Edge to simplify interactions with the Microsoft Azure IoT SDKs (https://github.com/azure/azure-iot-sdks) and programmatically construct pipeline topologies and live pipelines.

A Java component which displays bytes in Hex- and ASCII-format. The component is designed as a standalone lib. A complete interface which provides the function of an HexEditor based on this lib exisits under the Fork of this project. \r\n This library is simply taken directly from sourceforge at https://sourceforge.net/projects/hexlib/ and made it available in maven central repository. No other changes have been made (including keeping the same license).

This is client side library for forker, and the one you most likely want to use in your own applications. It provides the ProcessBuilder replacement, ForkerBuilder, as well the helpers in OSCommand. ForkerBuilder is capable of launching processes using non-blocking I/O or attached to a PTY. It has many additional features not available in the standard process builder including permission elevation, daemonize, processor affinity and more. Parts of the non-blocking API are based on NuProcess (https://github.com/brettwooldridge/NuProcess)

This library allows your Java program to interface very easily with the Python world. It uses the Pyro protocol to call methods on remote objects. (See https://pyro5.readthedocs.io/). Pyrolite only implements part of the client side Pyro library, hence its name 'lite'... So if you don't need Pyro's full feature set, Pyrolite may be a good choice to connect java or .NET and python. Version 5.0 changes: support Pyro5 wire protocol. Dropped support of Pyro4 (stick to version 4.xx for that).

Virgil Security is presenting an implementation of the [Double Ratchet](https://signal.org/docs/specifications/doubleratchet/) algorithm, which is used by parties to exchange encrypted messages based on a shared secret key. The implementation includes: - **Virgil Perfect Forward Secrecy (PFS) service** – a standalone web-service that is dedicated to managing one-time keys and long-time keys that are based on their Identity Public Keys (public keys that are contained in user cards published on Virgil Cards service); - **Ratchet SDK** – interacts with PFS service for publishing and managing one-time keys and long-time keys and interacts with Virgil Cards service for retrieving user's indentity cards which the OTK and LTK are based on. The parties derive new keys for every Double Ratchet message so that previous private keys cannot be calculated from new ones. The parties that participate in the communication also send Diffie-Hellman public values attached to their messages. The results of Diffie-Hellman calculations are mixed into the derived keys so that the new private keys cannot be calculated from the previous ones.

Virgil Security is presenting an implementation of the [Double Ratchet](https://signal.org/docs/specifications/doubleratchet/) algorithm, which is used by parties to exchange encrypted messages based on a shared secret key. The implementation includes: - **Virgil Perfect Forward Secrecy (PFS) service** – a standalone web-service that is dedicated to managing one-time keys and long-time keys that are based on their Identity Public Keys (public keys that are contained in user cards published on Virgil Cards service); - **Ratchet SDK** – interacts with PFS service for publishing and managing one-time keys and long-time keys and interacts with Virgil Cards service for retrieving user's indentity cards which the OTK and LTK are based on. The parties derive new keys for every Double Ratchet message so that previous private keys cannot be calculated from new ones. The parties that participate in the communication also send Diffie-Hellman public values attached to their messages. The results of Diffie-Hellman calculations are mixed into the derived keys so that the new private keys cannot be calculated from the previous ones.