This notebook installs RequestSeal 0.5.2 from Hex and checks that your runtime can use it: the pinned Elixir and OTP versions, Ed25519 support in OTP's crypto, the public entry points, and the supported HTTP signature algorithms. No key, secret, or provider account is required. Use the pinned Elixir/OTP runtime below.
Mix.install([{:request_seal, "~> 0.5.2"}])Inspect actual capabilities
Code.ensure_loaded!(RequestSeal)
"1.20.4" = System.version()
"29" = System.otp_release()
true = :eddsa in Keyword.fetch!(:crypto.supports(), :public_keys)
true = :ed25519 in Keyword.fetch!(:crypto.supports(), :curves)
{:docs_v1, _, :elixir, _, %{"en" => module_docs}, _, _} = Code.fetch_docs(RequestSeal)
true = is_binary(module_docs)
[sign: 3, sign: 4, verify: 3, verify_quorum: 3] = RequestSeal.__info__(:functions)
[
"rsa-pss-sha512",
"rsa-v1_5-sha256",
"hmac-sha256",
"ecdsa-p256-sha256",
"ecdsa-p384-sha384",
"ed25519"
] = RequestSeal.Crypto.algorithms()
IO.puts("RequestSeal module loaded; pinned runtime, Ed25519, and six HTTP algorithms available")The result proves installation and prerequisites only. The other notebooks exercise signing and verification; see testing and evidence for how these checks differ from protocol conformance. No filesystem path, secret, private key, request body, or token is printed.