react-native-quick-crypto 1.1.0 → 1.1.1

package/deps/blake3/.github/workflows/tag.yml

@@ -1,43 +0,0 @@
-name: publish_b3sum_binaries
-
-on:
-  push:
-    tags:
-      - "*"
-
-env:
-  BLAKE3_CI: "1"
-  RUSTFLAGS: "-D warnings"
-
-jobs:
-  cargo_tests:
-    name: ${{ matrix.target.name }}
-    runs-on: ${{ matrix.target.os }}
-    strategy:
-      fail-fast: false
-      matrix:
-        target: [
-          { "os": "ubuntu-latest",  "rust-target": "x86_64-unknown-linux-musl", "name": "Linux" },
-          { "os": "macOS-latest",   "rust-target": "x86_64-apple-darwin",       "name": "macOS" },
-          { "os": "windows-latest", "rust-target": "x86_64-pc-windows-msvc",    "name": "Windows" },
-        ]
-
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-python@v4
-        with:
-          python-version: "3.x"
-      - run: pip install PyGithub
-      - run: sudo apt-get install musl-tools
-        if: matrix.target.os == 'ubuntu-latest'
-      - uses: dtolnay/rust-toolchain@stable
-        with:
-          targets: ${{ matrix.target.rust-target }}
-      - name: build b3sum
-        id: build_b3sum
-        run: python -u .github/workflows/build_b3sum.py ${{ matrix.target.rust-target }}
-      - name: upload release asset
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          GITHUB_TAG: ${{ github.ref }}
-        run: python -u .github/workflows/upload_github_release_asset.py ${{ steps.build_b3sum.outputs.bin_path }}

package/deps/blake3/.github/workflows/upload_github_release_asset.py

@@ -1,73 +0,0 @@
-#! /usr/bin/env python3
-
-import github
-import os
-import sys
-import time
-
-RETRIES = 10
-
-g = github.Github(os.environ["GITHUB_TOKEN"])
-tag_name = os.environ["GITHUB_TAG"]
-tag_prefix = "refs/tags/"
-if tag_name.startswith(tag_prefix):
-    tag_name = tag_name[len(tag_prefix) :]
-assert len(sys.argv) == 2
-asset_path = sys.argv[1]
-asset_name = os.path.basename(asset_path)
-
-repo = g.get_repo(os.environ["GITHUB_REPOSITORY"])
-
-tags = list(repo.get_tags())
-
-for tag in tags:
-    if tag.name == tag_name:
-        break
-else:
-    raise RuntimeError("no tag named " + repr(tag_name))
-
-try:
-    print("Creating GitHub release for tag " + repr(tag_name) + "...")
-    repo.create_git_release(tag_name, tag_name, tag.commit.commit.message)
-except github.GithubException as github_error:
-    if github_error.data["errors"][0]["code"] == "already_exists":
-        print("Release for tag " + repr(tag_name) + " already exists.")
-    else:
-        raise
-
-
-def get_release():
-    for i in range(RETRIES):
-        releases = list(repo.get_releases())
-        for release in releases:
-            if release.tag_name == tag_name:
-                return release
-        print(f"Release for tag {repr(tag_name)} not found. Retrying...")
-        time.sleep(1)
-    raise RuntimeError("no release for tag " + repr(tag_name))
-
-
-release = get_release()
-
-print("Uploading " + repr(asset_path) + "...")
-for i in range(RETRIES):
-    try:
-        print("Upload attempt #{} of {}...".format(i + 1, RETRIES))
-        release.upload_asset(asset_path)
-        break
-    except github.GithubException as github_error:
-        # Unfortunately the asset upload API is flaky. Even worse, it often
-        # partially succeeds, returning an error to the caller but leaving the
-        # release in a state where subsequent uploads of the same asset will
-        # fail with an "already_exists" error. (Though the asset is not visible
-        # on github.com, so we can't just declare victory and move on.) If we
-        # detect this case, explicitly delete the asset and continue retrying.
-        print(github_error)
-        for asset in release.get_assets():
-            if asset.name == asset_name:
-                print("Found uploaded asset after failure. Deleting...")
-                asset.delete_asset()
-else:
-    raise RuntimeError("All upload attempts failed.")
-
-print("Success!")

package/deps/blake3/CONTRIBUTING.md

@@ -1,31 +0,0 @@
-# Contributing
-
-We welcome and encourage third-party contributions to BLAKE3, be it reports of issues encountered while using the software or proposals of patches.
-
-## Bug reports
-
-Bugs and other problems should be reported on [GitHub Issues](https://github.com/BLAKE3/BLAKE3/issues).
-
-If you report a bug, please:
-
-* Check that it's not already reported in the [GitHub Issues](https://github.com/BLAKE3/BLAKE3/issues).
-* Provide information to help us diagnose and ideally reproduce the bug.
-
-## Patches
-
-We encourage you to fix a bug via a [GitHub Pull request](https://github.com/BLAKE3/BLAKE3/pulls), preferably after creating a related issue and referring it in the PR.
-
-If you contribute code and submit a patch, please note the following:
-
-* We use Rust's stable branch for developing BLAKE3.
-* Pull requests should target the `master` branch.
-* Try to follow the established Rust [style guidelines](https://doc.rust-lang.org/1.0.0/style/).
-
-Also please make sure to create new unit tests covering your code additions. You can execute the tests by running:
-
-```bash
-cargo test
-```
-
-All third-party contributions will be recognized in the list of contributors.
-

package/deps/blake3/Cargo.toml

@@ -1,135 +0,0 @@
-[package]
-name = "blake3"
-version = "1.8.2"
-authors = ["Jack O'Connor <oconnor663@gmail.com>", "Samuel Neves"]
-description = "the BLAKE3 hash function"
-repository = "https://github.com/BLAKE3-team/BLAKE3"
-license = "CC0-1.0 OR Apache-2.0 OR Apache-2.0 WITH LLVM-exception"
-documentation = "https://docs.rs/blake3"
-readme = "README.md"
-edition = "2021"
-
-[features]
-default = ["std"]
-
-# The NEON implementation does not participate in dynamic feature detection,
-# which is currently x86-only. If "neon" is on, NEON support is assumed. Note
-# that AArch64 always supports NEON, but support on ARMv7 varies. The NEON
-# implementation uses C intrinsics and requires a C compiler.
-neon = []
-
-# The Wasm SIMD implementation does not participate in dynamic feature detection,
-# which is currently x86-only. If "wasm_simd" is on, Wasm SIMD support is assumed.
-# Note that not all Wasm implementations support the Wasm SIMD specification.
-# This may become the default in the future.
-wasm32_simd = []
-
-# This crate uses libstd for std::io trait implementations, and also for
-# runtime CPU feature detection. This feature is enabled by default. If you use
-# --no-default-features, the only way to use the SIMD implementations in this
-# crate is to enable the corresponding instruction sets statically for the
-# entire build, with e.g. RUSTFLAGS="-C target-cpu=native".
-std = []
-
-# The `rayon` feature (disabled by default, but enabled for docs.rs) adds the
-# `update_rayon` and (in combination with `mmap` below) `update_mmap_rayon`
-# methods, for multithreaded hashing. However, even if this feature is enabled,
-# all other APIs remain single-threaded.
-#
-# Implementation detail: We take a dependency on rayon-core instead of rayon,
-# because it builds faster and still includes all the APIs we need.
-rayon = ["dep:rayon-core"]
-
-# The `mmap` feature (disabled by default, but enabled for docs.rs) adds the
-# `update_mmap` and (in combination with `rayon` above) `update_mmap_rayon`
-# helper methods for memory-mapped IO.
-mmap = ["std", "dep:memmap2"]
-
-# Implement the zeroize::Zeroize trait for types in this crate.
-zeroize = ["dep:zeroize", "arrayvec/zeroize"]
-
-# This crate implements traits from the RustCrypto project, exposed here as the
-# "traits-preview" feature. However, these traits aren't stable, and they're
-# expected to change in incompatible ways before they reach 1.0. For that
-# reason, this crate makes no SemVer guarantees for this feature, and callers
-# who use it should expect breaking changes between patch versions of this
-# crate. (The "*-preview" feature name follows the conventions of the RustCrypto
-# "signature" crate.)
-traits-preview = ["dep:digest"]
-
-# ---------- Features below this line are undocumented and unstable. ----------
-# The following features are mainly intended for testing and benchmarking, and
-# they might change or disappear at any time without a major version bump.
-
-# It wasn't originally intended to expose "digest" as its own feature, but the
-# traits-preview feature above predated the "dep:" syntax in Cargo. Version
-# 1.5.2 of this crate started using "dep:" syntax, but that broke some callers
-# in the wild (https://solana.stackexchange.com/q/17787/29050). This feature
-# unbreaks those callers. When Cargo gains the ability to deprecate features,
-# this feature will be deprecated. Note that the relevant trait implementations
-# are still gated by "traits-preview".
-digest = ["dep:digest"]
-
-# By default on x86_64, this crate uses Samuel Neves' hand-written assembly
-# implementations for SSE4.1, AVX2, and AVX512. (These provide both the best
-# runtime performance, and the fastest build times.) And by default on 32-bit
-# x86, this crate uses Rust intrinsics implementations for SSE4.1 and AVX2, and
-# a C intrinsics implementation for AVX-512. In both cases, if a C compiler is
-# not detected, or if AVX-512 support is missing from the detected compiler,
-# build.rs automatically falls back to a pure Rust build. This feature forces
-# that fallback, for testing purposes. (Note that in CI testing, we set the
-# BLAKE3_CI environment variable, which instructs build.rs to error out rather
-# than doing an automatic fallback.)
-pure = []
-
-# As described above, on x86_64 this crate use assembly implementations by
-# default. Enabling the "prefer_intrinsics" feature makes this crate use
-# intrinsics implementations on both 32-bit and 64-bit x86, again for testing
-# purposes.
-prefer_intrinsics = []
-
-# Disable individual instruction sets. CI testing uses these flags to simulate
-# different levels of hardware SIMD support. Note that code for the
-# corresponding instruction set is still compiled; only detection is disabled.
-#
-# As noted above, these flags are *for testing only* and are not stable. It's
-# possible that some users might find that their particular use case performs
-# better if e.g. AVX-512 is disabled, because of issues like CPU downclocking.
-# If that comes up, and if disabling the instruction set here at the feature
-# level turns out to be the right approach, then we can design a stable
-# feature. Until then, we reserve the right to break these features in a patch
-# release.
-no_sse2 = []
-no_sse41 = []
-no_avx2 = []
-no_avx512 = []
-no_neon = []
-
-[package.metadata.docs.rs]
-# Document the rayon/mmap methods and the Serialize/Deserialize/Zeroize impls on docs.rs.
-features = ["mmap", "rayon", "serde", "zeroize"]
-
-[dependencies]
-arrayref = "0.3.5"
-arrayvec = { version = "0.7.4", default-features = false }
-constant_time_eq = { version = "0.3.1", default-features = false }
-cfg-if = "1.0.0"
-digest = { version = "0.10.1", features = ["mac"], optional = true }
-memmap2 = { version = "0.9", optional = true }
-rayon-core = { version = "1.12.1", optional = true }
-serde = { version = "1.0", default-features = false, features = ["derive"], optional = true }
-zeroize = { version = "1", default-features = false, optional = true }
-
-[dev-dependencies]
-hmac = "0.12.0"
-hex = "0.4.2"
-page_size = "0.6.0"
-rand = "0.9.0"
-rand_chacha = "0.9.0"
-reference_impl = { path = "./reference_impl" }
-tempfile = "3.8.0"
-serde_json = "1.0.107"
-ciborium = "0.2.2"
-
-[build-dependencies]
-cc = "1.1.12"