
Security News
Node.js Considers Public Workflow for Security Reports Amid AI-Driven Surge
Node.js is debating whether AI-driven security report volume warrants moving more vulnerability reports into public workflows.
@sovrahq/kms-client
Advanced tools
KMS comes from the English key management system and is the component in charge of creating key pairs, encrypting, decrypting and signing content. The current Extrimian KMS implementation supports the ES256k, DIDComm, and BBSBLS2020 algorithms.
KMS comes from the English key management system and is the component in charge of creating key pairs, encrypting, decrypting and signing content. The current Extrimian KMS implementation supports the ES256k, DIDComm, and BBSBLS2020 algorithms.
constructor(
config: {
lang: LANG;
storage: KMSStorage;
didResolver ?: (did: string) => Promise<DIDDocument>;
mobile ?: boolean
}
)
KMS applies dependency inversion concepts so it requires send a KMSStorage by its constructor.
interface KMSStorage {
add(key: string, data: any): Promise<void>;
get(key: string): Promise<any>;
getAll(): Promise<Map<string, any>>;
update(key: string, data: any);
remove(key: string);
}
This is a mock implementation example
import { KMSStorage } from "@quarkid/kms-core";
export class SecureStorage implements KMSStorage {
map = new Map<string, any>();
async add(key: string, data: any): Promise<void> {
this.map.set(key, data);
}
async get(key: string): Promise<any> {
return this.map.get(key);
}
async getAll(): Promise<Map<string, any>> {
return this.map;
}
async update(key: string, data: any) {
this.map.set(key, data);
}
async remove(key: string) {
this.map.delete(key);
}
}
const updateKey = await kms.create(Suite.ES256k);
const recoveryKey = await kms.create(Suite.ES256k);
const didComm = await kms.create(Suite.DIDComm);
const bbsbls = await kms.create(Suite.Bbsbls2020);
sign(
suite: Suite,
publicKeyJWK: IJWK,
content: any
): Promise<string>
return await kms.sign(Suite.ES256k, updateKey, content)
It is used to sign a verifiable credential.
signVC(
suite: Suite,
publicKeyJWK: IJWK,
vc: any,
did: string,
verificationMethodId: string,
purpose: Purpose
): Promise<VerifiableCredential>
pack(
publicKeyJWK: IJWK,
toHexPublicKeys: string[],
contentToSign: string
): Promise<string>
unpack(
publicKeyJWK: IJWK,
packedContent: string
): Promise<string>
export(
publicKeyJWK: IJWK
): Promise<any>
getPublicKeysBySuiteType(
suite: Suite
): Promise<IJWK[]>
getAllPublicKeys(): Promise<IJWK[]>
FAQs
KMS comes from the English key management system and is the component in charge of creating key pairs, encrypting, decrypting and signing content. The current Extrimian KMS implementation supports the ES256k, DIDComm, and BBSBLS2020 algorithms.
We found that @sovrahq/kms-client demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Node.js is debating whether AI-driven security report volume warrants moving more vulnerability reports into public workflows.

Security News
PolinRider expands across npm, Packagist, Go modules, and Chrome extensions, using hidden loaders to target developer environments.

Security News
Open source attacks are accelerating as AI coding agents pull in dependencies faster, with less human review.