KASLCred : KERI and ACDC Schema Linker for Credentials
Computes self addressing identifiers (SAIDs) for KERI and ACDC schema parts and links them together by SAID.
Usage
python -m kaslcred [schema_dir] [output_dir] [schema_map_file.json]
# Example:
# Requires having pre-written and pre-copied all of the schema files into ${KASL_HOME}/schemas
export KASL_HOME=${HOME}/.kasl
python -m kaslcred ${KASL_HOME}/schemas ${KASL_HOME}/results ${KASL_HOME}/schemas/schema_map.json
Installation
Docker
Manual Local Installation
- Install Python
- Install the Rust Toolchain: https://www.rust-lang.org/tools/install\ This is for the Blake3 crypto library built when installing KERI.
- Install KERI:
pip install keri==0.6.8 - Install KASLcred
Dependencies
KASLCred depends on the following libraries being installed:
Rust toolchain (for Blake3 dependency)
Libsodium
The Homebrew installation of Libsodium is not sufficient, or did not work for me. I had to do the following instructions like stated in Libsodium's Gitbook Installation documentation
Download a tarball of libsodium, preferably the latest stable version, then follow the ritual:
./configure
make && make check
sudo make install
KERIpy version 1.0.0
python -m pip install keri=1.0.0
KERIpy further depends on the following set of dependencies being installed:
Rust v1.60+
This is required for Blake3 dependency in KERI to be able to build.
# the "-s -- -y" options are for a silent, unattended install. Omit them if you want to configure the install.
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y
# Remember to set the PATH variable to include the Cargo binary directory like so: PATH="$HOME/.cargo/bin:$PATH
Development
Make sure to create a local environment with Pipenv.
Then install the Python build tool with pip install build and the release tool with pip install twine.
Installing from the root repo directory:
python3 -m pip install -e ./
Metadata
Release files for kaslcred 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| kaslcred-0.1.4.tar.gz | 37.7 kB | Without provenance | Details for kaslcred-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| kaslcred-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for kaslcred-0.1.4-py3-none-any.whl |
Total release size: 48.0 kB
Release files / kaslcred-0.1.4.tar.gz
| Download URL | kaslcred-0.1.4.tar.gz |
|---|---|
| Size | 37.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b7aae83b1c6993d48cda12d0fa8ed30a9f73e9ba1668c65eb644be0ecf63668
|
|
BLAKE2b-256 checksum How to use checksums |
37233439ee0e1f9fa69a662fb69a4916b0308a216a8b30863807966629ba0e29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.8
|
Release files / kaslcred-0.1.4-py3-none-any.whl
| Download URL | kaslcred-0.1.4-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
118882a40eefac04277833d8dc6d3d8ec5955e537479ac0a844de45a48501801
|
|
BLAKE2b-256 checksum How to use checksums |
1b9fa4d980af93918a9799ab6ca27cc4404caf8e75547c8925f0762d95ef2fa7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.8
|
Security for kaslcred 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.