The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

secretbase: Cryptographic Hash, Extendable-Output and Binary Encoding Functions

Fast and memory-efficient streaming hash functions, binary encoding and serialization. Hashes strings and raw vectors directly. Stream hashes files which can be larger than memory, as well as in-memory objects through R's serialization mechanism. Implements the SHA-256, SHA-3 and 'Keccak' cryptographic hash functions, SHAKE256 extendable-output function (XOF), 'SipHash' pseudo-random function, base64 and base58 encoding, and 'CBOR' serialization.

Version: 1.1.0
Depends: R (≥ 3.5)
Published: 2026-01-08
DOI: 10.32614/CRAN.package.secretbase
Author: Charlie Gao ORCID iD [aut, cre], Posit Software, PBC ROR ID [cph, fnd], Hibiki AI Limited [cph]
Maintainer: Charlie Gao <charlie.gao at posit.co>
BugReports: https://github.com/shikokuchuo/secretbase/issues
License: MIT + file LICENSE
URL: https://shikokuchuo.net/secretbase/, https://github.com/shikokuchuo/secretbase/
NeedsCompilation: yes
Materials: README, NEWS
CRAN checks: secretbase results

Documentation:

Reference manual: secretbase.html , secretbase.pdf

Downloads:

Package source: secretbase_1.1.0.tar.gz
Windows binaries: r-devel: secretbase_1.1.0.zip, r-release: secretbase_1.1.0.zip, r-oldrel: secretbase_1.1.0.zip
macOS binaries: r-release (arm64): secretbase_1.1.0.tgz, r-oldrel (arm64): secretbase_1.1.0.tgz, r-release (x86_64): secretbase_1.1.0.tgz, r-oldrel (x86_64): secretbase_1.1.0.tgz
Old sources: secretbase archive

Reverse dependencies:

Reverse imports: jagstargets, tarchetypes, targets

Linking:

Please use the canonical form https://CRAN.R-project.org/package=secretbase to link to this page.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.