npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@proofmeid/webrtc-node

v0.0.197

Published

WebRTC + Signaling Server

Downloads

41

Readme

Proofme.ID - WebRTC

This package allows easy usage of the WebRTC part as of a lot of utilty functions to check credentials and validity of those

Node version

Step 1: Importing the package

import { ICredentialObject, IRequestedCredentials, IValidatedCredentials, ProofmeUtils } from "@proofmeid/webrtc-node";

Step 2: Using the library to validate credentials

Below an example of how to pass the credentials and validate them.

const credentialObject: ICredentialObject = req.body.credentials;
if (credentialObject) {
    const requestedData: IRequestedCredentials = {
        by: "Proofme",
        description: "full identification",
        credentials: [
            { key: "PHOTO", provider: "EPASS", required: true },
            { key: "FIRST_NAME", provider: "EPASS", required: true },
            { key: "LAST_NAME", provider: "EPASS", required: true },
            { key: "BIRTH_DATE", provider: "EPASS", required: true },
            { key: "GENDER", provider: "EPASS", required: true },
            { key: "NATIONALITY", provider: "EPASS", required: true },
            { key: "DOCUMENT_NUMBER", provider: "EPASS", required: true },
            { key: "DOCUMENT_EXPIRY_DATE", provider: "EPASS", required: true },
            { key: "DOCUMENT_TYPE", provider: "EPASS", required: true }
        ]
    };
    const proofmeUtils = new ProofmeUtils();
    const validatedCredentials = await proofmeUtils.validCredentialsTrustedPartiesFunc(credentialObject, config.web3Url, requestedData, config.trustedDids as string[], true, true) as IValidatedCredentials;
    if (validatedCredentials.valid) {
        // Do stuff with the credentials as you like
        res.status(200).send({ message: "SUCCESS.VALID_CREDENTIALS", success: true });
    } else {
        res.status(200).send({ message: "ERROR.INVALID_CREDENTIALS", success: false });
    }
} else {
    res.status(400).send({ error: "ERROR.MISSING_CREDENTIAL_OBJECT" });
}

Please note that the 'requestedData' object has to match the 'requestedData' in the frontend. We should check the exact same thing that has been asked to the customer.

The 'ProofmeUtils' class contains a function to validate the credentials, which will return a valid 'true' or valid 'false'.

  • Config web3Url (to which blockchain URL to check the issuers), Proofme's: 'https://api.didux.network/'
  • Config trustedDids (which issuers are valid), Proofme's: '["0xa6De718CF5031363B40d2756f496E47abBab1515"]'