open-index/open-npm huggingface dataset:
npm package: @sphereon/rn-did-auth-op-authenticator
Description: - yarn install - yarn build - yarn publish (in case you want to publish the project to a private registry.)
Author: Sphereon
Latest version: 0.0.8

<h1 align="center">
  <br>
  <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>
  <br>DID SIOP auth component library for react-native 
  <br>
</h1>

This library contains an OP Authenticator implementation that can be used in React Native projects.

Demo project [rn-did-siop-example-app}(https://github.com/Sphereon-OpenSource/rn-did-siop-example-app) implements this library.

### To build

- yarn install
- yarn build
- yarn publish (in case you want to publish the project to a private registry.)
npm package: @sphereon/rn-ecdsa-secp256k1-signature-2019
Description: EcdsaSecp256k1Signature2019 Linked Data Proof suite for use with jsonld-signatures.
Author: Bloom Team
Latest version: 0.1.2

# EcdsaSecp256k1Signature2019 suite

> EcdsaSecp256k1Signature2019 Linked Data Proof suite for use with jsonld-signatures.

## Background

For use with:
- [`jsonld-signatures`](https://github.com/digitalbazaar/jsonld-signatures) `^9.0.0`.
- [`@bloomprotocol/vc`](https://github.com/hellobloom/ssi-sdk/tree/main/packages/vc) `^0.1.0`.
- [`@digitalbazaar/vc`](https://github.com/digitalbazaar/vc-js) `^1.0.0`.

See also related specs:

- [EcdsaSecp256k1Signature2019 Crypto Suite](https://w3c-ccg.github.io/lds-ecdsa-secp256k1-2019/)

## Install

```
npm i @bloomprotocol/ecdsa-secp256k1-signature-2019
```

OR

```
yarn add @bloomprotocol/ecdsa-secp256k1-signature-2019
```
npm package: @sphereon/rn-ecdsa-secp256k1-verification-key-2019
Description: TypeScript library for generating and working with EcdsaSecp256k1VerificationKey2019 key pairs, for use with crypto-ld.
Author: Bloom Team
Latest version: 0.1.2

# EcdsaSecp256k1VerificationKey2019 suite

> TypeScript library for generating and working with EcdsaSecp256k1VerificationKey2019 key pairs, for use with crypto-ld.

## Background

For use with:
- [`crypto-ld`](https://github.com/digitalbazaar/crypto-ld) `^6.0.0`
- [`@bloomprotocol/ecdsa-secp256k1-signature-2019`](https://github.com/hellobloom/ssi-sdk/tree/main/packages/ecdsa-secp256k1-signature-2019) `^0.1.0`
- [`@bloomprotocol/vc`](https://github.com/hellobloom/ssi-sdk/tree/main/packages/vc) `^0.1.0`.
- [`@digitalbazaar/vc`](https://github.com/digitalbazaar/vc-js) `^1.0.0`.

See also related specs:

- [EcdsaSecp256k1VerificationKey2019](https://w3c-ccg.github.io/lds-ecdsa-secp256k1-2019/#dfn-ecdsasecp256k1verificationkey2019)

## Install

```
npm i @bloomprotocol/ecdsa-secp256k1-verification-key-2019
```

OR

```
yarn add @bloomprotocol/ecdsa-secp256k1-verification-key-2019
```
npm package: @sphereon/ssi-sdk-agent-config
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>Agent Configuration    <br> </h1>
Author: Sphereon
Latest version: 0.11.0

<!--suppress HtmlDeprecatedAttribute -->
<h1 align="center">
  <br>
  <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>
  <br>Agent Configuration 
  <br>
</h1>

This plugin allows you to run/start an Agent from a yaml configuration. Best used in a NodeJS environment, but should work with React-Native in case path/fs are browserified or polyfilled

## Installation

```shell
yarn add @sphereon/ssi-sdk-agent-config
```

## Build

```shell
yarn build
```
npm package: @sphereon/ssi-sdk-connection-manager
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>Connection Manager (Typescript)    <
Author: Sphereon
Latest version: 0.9.0
npm package: @sphereon/ssi-sdk-core
Description: SSI SDK Core & Interfaces
Author: Sphereon
Latest version: 0.11.0

<!--suppress HtmlDeprecatedAttribute -->
<h1 align="center">
  <br>
  <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>
  <br>SSI SDK Core (Typescript) 
  <br>
</h1>

---

**Warning: This package still is in every early development. Breaking changes without notice will happen at this point!**

---

# ssi-sdk-core

A Veramo plugin whit types/interfaces and utility functions shared by multiple plugins

### Installation

```shell
yarn add @sphereon/ssi-sdk-core
```

### Build

```shell
yarn build
```

### Test

The test command runs:

- `prettier`
- `jest`
- `coverage`

You can also run only a single section of these tests, using for example `yarn test:unit`.

```shell
yarn test
```

### Utility scripts

There are other utility scripts that help with development.

- `yarn fix` - runs `eslint --fix` as well as `prettier` to fix code style.
npm package: @sphereon/ssi-sdk-data-store
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>Data Store (Typescript)    <br> </h1
Author: Sphereon
Latest version: 0.11.0

<!--suppress HtmlDeprecatedAttribute -->
<h1 align="center">
  <br>
  <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>
  <br>Data Store (Typescript) 
  <br>
</h1>

---

**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**

---

SSI-SDK data storage based on TypeORM. This package provides several plugins that relate to data storage.

## Available stores

- Contact Store

### Contact Store

A store that exposes simple store/get methods for contacts and identities.

## Installation

```shell
yarn add @sphereon/ssi-sdk-data-store
```

## Build

```shell
yarn build
```

## Module developers

We use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete
information from entities, ensure that migration files are being created to reflect the updates.

Currently, we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to
that we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.

### Create a migration file

- Ensure you have an existing sqlite/postgres database at hand with the old situation
- Make a copy of that database, so you can always easily go back
- Run the respective commands for postgres and/or sqlite:
  - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`
  - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`
- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _
  NameOfYourMigration_
- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their
  migrations entrypoint from their TypeORM config.
- If you wish to check whether applying the migration works you can execute the respective

### Applying migrations

There is an example sqlite file in the root called migration.sqlite.
We use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer
changing an entity,

This file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`
The same can be done for a local Postgres database using the command `typeorm-postgres:migration:run`

You can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)
npm package: @sphereon/ssi-sdk-data-store-common
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>Data Store Common (Typescript)    <b
Author: Sphereon
Latest version: 0.9.0
npm package: @sphereon/ssi-sdk-did-utils
Description: DID Utils
Author: Sphereon
Latest version: 0.11.0

<!--suppress HtmlDeprecatedAttribute -->
<h1 align="center">
  <br>
  <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>
  <br>SSI SDK DID Utils 
  <br>
</h1>

---

**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**

---

# ssi-sdk-core

A plugin with different DID functions

### Installation

```shell
yarn add @sphereon/ssi-sdk-did-utils
```

### Build

```shell
yarn build
```

### Test

The test command runs:

- `prettier`
- `jest`
- `coverage`

You can also run only a single section of these tests, using for example `yarn test:unit`.

```shell
yarn test
```

### Utility scripts

There are other utility scripts that help with development.

- `yarn fix` - runs `eslint --fix` as well as `prettier` to fix code style.
npm package: @sphereon/ssi-sdk-factom-did-provider
Description: Veramo Factom DID provider
Author: Sphereon
Latest version: 0.11.0

<!--suppress HtmlDeprecatedAttribute -->
<h1 align="center">
  <br>
  <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>
  <br>Ssi-sdk-factom-did-provider (Typescript) 
  <br>
</h1>

Lto-factom-provider is a Veramo plugin to create DIDs on Factom Protocol.

### Constructor

During construction of the Factom DID provider you can set the defaultNetwork, universal registrar URL and the Veramo default Key Management System (KMS)

```typescript
import { FactomDIDProvider } from '@sphereon/veramo-factom-did-provider'

const factomDIDProvider = new FactomDIDProvider({
  defaultKms: 'local',
  defaultNetwork: 'testnet',
  registrarUrl: 'https://your.universal.registrar.here',
})
```

### createIdentifier

Creating a DID means you have to create public/private keypairs first both for the DID fragment itself as well as the management keys. The Factom DID Provider will store these keys using Veramo's Keymanager, so that you can use them later

```typescript
const managementKeys = [
  { priority: 0, privateKeyMultibase: 'z08a58bad89...' },
  { priority: 1, privateKeyMultibase: 'z18a58bad89...' },
]
const didKeys = [{ priorityRequirement: 1, privateKeyMultibase: 'z234a...', purpose: [] }]
const tags = ['my', 'did', 'chain', 'name', 'here'] // Used to populate Factoms external Id values
const nonce = 'random value' // If left out, will be automatically created to make the DID chain unique

const identifier = await factomDIDProvider.createIdentifier(
  {
    options: {
      managementKeys,
      didKeys,
      tags,
      nonce,
    },
  },
  context
)
```

### Installation

```shell
yarn add @sphereon/ssi-sdk-factom-did-provider
```

### Build

```shell
yarn build
```
npm package: @sphereon/ssi-sdk-jwk-did-provider
Description: Veramo jwk-did based identity controller plugin.
Author: Sphereon
Latest version: 0.11.0

<!--suppress HtmlDeprecatedAttribute -->
<h1 align="center">
  <br>
  <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>
  <br>Ssi-sdk-jwk-did-provider 
  <br>(Typescript) 
  <br>
</h1>

This package contains an implementation of the `AbstractIdentifierProvider` for the `did:jwk` method.
Enabling creating and resolving of `did:jwk` entities, conforming to the [spec for DID-JWK](https://github.com/quartzjer/did-jwk/blob/main/spec.md)

## Available functions

- createIdentifier
- deleteIdentifier
- resolveDidJwk

## Usage

### Creating an identifier

When creating a new Veramo Identifier you can choose to import your own keys or have them generated for you. You can
also choose to use specific Key IDs for your key, regardless of generation or import.
The options object when creating an identifier is as follows:

```typescript
export interface KeyOpts {
  key?: MinimalImportableKey // Optional key to import. If not specified a key with random kid will be created
  type?: Key // The key type. Defaults to Secp256k1
  use?: KeyUse // The key use
}
```

### Creating an Identifier using auto-generated keys

The example below generates a JWK DID with auto-generated keys.

```typescript
const identifier: IIdentifier = await agent.didManagerCreate()
```

### Creating an Identifier using imported keys

The example below generates a JWK DID using imported keys.

```typescript
const identifier: IIdentifier = await agent.didManagerCreate({
  key: {
    privateKeyHex: '06eb9e64569203679b36f834a4d9725c989d32a7fb52c341eae3517b3aff8ee6',
  },
})
```

### Removing the Identifier and DID

Deleting an identifier is straightforward:

```typescript
const deleted: boolean = await agent.didManagerDelete({ did: identifier.did })
```

### Resolving a DID

The example below resolves a did:jwk to DIDResolutionResult.

```typescript
const didResolutionResult: DIDResolutionResult = await agent.resolveDid({ didUrl: 'did:jwk:ey....' })
```

## Installation

```shell
yarn add @sphereon/ssi-sdk-jwk-did-provider
```

## Build

```shell
yarn build
```
npm package: @sphereon/ssi-sdk-lto-did-provider
Description: Veramo LTO Network DID provider
Author: Sphereon
Latest version: 0.11.0

<!--suppress HtmlDeprecatedAttribute -->
<h1 align="center">
  <br>
  <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>
  <br>Ssi-sdk-lto-did-provider (Typescript) 
  <br>
</h1>

Lto-did-provider is a Veramo plugin to create and delete DIDs and to add and manage verification methods on LTO Network.

### createIdentifier

Creating a DID means you have to create a public/private keypair first. You can do this using lto-api package or any other means to create a ed25519 keypair. We are accepting an optional ed25519 private key to keep it flexible for everyone.

```js
const privateKeyHex = '18a58bad89...'

const identifier = await ltoDIDProvider.createIdentifier(
  {
    options: {
      privateKeyHex,
    },
  },
  context
)
```

### addKey

You can add one or more verification methods to an existing DID, or you can add them during DID creation. Internally this is accomplished using LTO Networks, associations. This means new private/public keypairs are needed. Again you can use your own ed25519 private key.

```js
 import { LtoVerificationMethod } from '@sphereon/lto-did-ts'

 const key = {
  kid: 'did:lto:1234567890abc',
  kms: 'local',
  type: 'Ed25519' as const,
  privateKeyHex,
  publicKeyHex: '27f3h29f3h7...',
}

 const did = await ltoDIDProvider.addKey({
    identifier,
    key,
    options: {
      verificationMethod: LtoVerificationMethod.VerificationMethod,
    },
  }, context)
```

### Installation

```shell
yarn add @sphereon/ssi-sdk-lto-did-provider
```

### Build

```shell
yarn build
```
npm package: @sphereon/ssi-sdk-mnemonic-info-generator
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>Mnemonic Info Generator (Typescript)
Author: Sphereon
Latest version: 0.2.0
npm package: @sphereon/ssi-sdk-mnemonic-seed-manager
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>Mnemonic Seed Manager (Typescript)  
Author: Sphereon
Latest version: 0.11.0

<!--suppress HtmlDeprecatedAttribute -->
<h1 align="center">
  <br>
  <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>
  <br>Mnemonic Seed Manager (Typescript) 
  <br>
</h1>

# mnemonic-seed-manager

A plugin to generate and store mnemonic pass phrases and seeds

### Installation

```shell
yarn add @sphereon/ssi-sdk-mnemonic-seed-manager
```

### Build

```shell
yarn build
```

### Test

The test command runs:

- `prettier`
- `jest`
- `coverage`

You can also run only a single section of these tests, using for example `yarn test:unit`.

```shell
yarn test
```

### Utility scripts

There are other utility scripts that help with development.

- `yarn fix` - runs `eslint --fix` as well as `prettier` to fix code style.

## Module developers

We use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete
information from entities, ensure that migration files are being created to reflect the updates.

Currently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to
that we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.

### Create a migration file

- Ensure you have an existing sqlite/postgres database at hand with the old situation
- Make a copy of that database so you can always easily go back
- Run the respective commands for postgresl and/or sqlite:
  - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`
  - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`
- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _
  NameOfYourMigration_
- Update the index.ts file in the respective directory to include the migration. Users will import that file as their
  migrations entrypoint from their TypeORM config.
- If you wish to check whether applying the migration works you can execute the respective

### Applying migrations

There is an example sqlite file in the root called migration.sqlite.
We use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer
changing an entity,

This file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`
The same can be done for a local Postgres database using the command `"typeorm-postgres:migration:run"`

You can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)
npm package: @sphereon/ssi-sdk-ms-vc-api-issuer
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>Microsoft Azure Active Directory VC 
Author: Sphereon
Latest version: 0.5.2-unstable.73

<!--suppress HtmlDeprecatedAttribute -->
<h1 align="center">
  <br>
  <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>
  <br>Microsoft Azure Active Directory VC API Issuer (Typescript) 
  <br>
</h1>

---

**Warning: This package still is in every early development. Breaking changes without notice will happen at this point!**

---

# ms-vc-api-verifier

A Veramo plugin to issue credentials using the Microsoft Azure Active Directory. 

### Installation

```shell
yarn add @sphereon/ssi-sdk-ms-vc-api-issuer
```

### Build

```shell
yarn build
```
npm package: @sphereon/ssi-sdk-presentation-exchange
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>Presentation Exchange     <br> </h1>
Author: Sphereon
Latest version: 0.9.1-unstable.109
npm package: @sphereon/ssi-sdk-siopv2-oid4vp-op-auth
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>DID Auth SIOP OP Authenticator (Type
Author: Sphereon
Latest version: 0.9.1-unstable.109
npm package: @sphereon/ssi-sdk-siopv2-oid4vp-rp-auth
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>SIOPv2 and OpenID4VP Relying Party  
Author: Sphereon
Latest version: 0.9.1-unstable.109
npm package: @sphereon/ssi-sdk-siopv2-oid4vp-rp-rest-api
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>SIOPv2 and OpenID4VP Relying Party R
Author: Sphereon
Latest version: 0.9.1-unstable.109
npm package: @sphereon/ssi-sdk-vc-api-issuer
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>VC API Issuer (Typescript)    <br> <
Author: Sphereon
Latest version: 0.9.0
npm package: @sphereon/ssi-sdk-vc-api-verifier
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>VC API Verifier (Typescript)    <br>
Author: Sphereon
Latest version: 0.9.0
npm package: @sphereon/ssi-sdk.ebsi-authorization-client
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>EBSI Authorization Client (Typescrip
Author: Sphereon
Latest version: 0.26.1-unstable.69
npm package: @sphereon/ssi-sdk.express-support
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>Express Support    <br> </h1>
Author: Sphereon
Latest version: 0.14.1
npm package: @sphereon/ssi-sdk.siopv2-holder
Description: <!--suppress HtmlDeprecatedAttribute --> <h1 align="center">   <br>   <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>   <br>SIOP - Holder (SIOPV2)   <br> </h1>
Author: Sphereon
Latest version: 0.25.1-unstable.36

<!--suppress HtmlDeprecatedAttribute -->
<h1 align="center">
  <br>
  <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>
  <br>SIOP - Holder (SIOPV2)
  <br>
</h1>

---

**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**

---

TODO

## Installation

```shell
yarn add @sphereon/ssi-sdk.siopv2-holder
```

## Build

```shell
yarn build
```
npm package: @sphereon/ui-components.credential-representation
Description: SSI UI components credential representation
Author: Sphereon
Latest version: 0.2.1-unstable.40

<!--suppress HtmlDeprecatedAttribute -->
<h1 align="center">
  <br>
  <a href="https://www.sphereon.com"><img src="https://sphereon.com/content/themes/sphereon/assets/img/logo.svg" alt="Sphereon" width="400"></a>
  <br>UI Components Credential Mapper (Typescript) 
  <br>
</h1>

A UI Core package for shared logic / styling and localization between components related to Credential Branding

### Build

```shell
pnpm build
```

### Installation

```shell
pnpm install @sphereon/ui-components.credential-mapper
```
npm package: @sphereon/url-handler
Description: Veramo message handler plugin to decode URL messages.
Author: Simonas Karuzas
Latest version: 3.1.1-unstable.52

# Veramo URL handler

This is an implementation of `AbstractMessageHandler` that can interpret messages presented as a URL.

This is done either by attempting to extract a `c_i` param from the URL query string or by fetching the given URL. This also looks for a URL redirect and attempts to extract the parameter from the redirected URL.