@evervault/sdk - npm Package Versions

6.3.1

Patch Changes

• 947115b: Correct logic for parsing domains from URLs supplied to the http request function: add fallback support for path alongisde pathname.

  Fix bug in parsing raw strings supplied to request to URLs by correcting object keys.

6.3.0

Minor Changes

• 720476d: Extend Relay outbound/forward proxy support in Node to include the ability to filter requests by path using decryptionDomains.

  Requests can be filtered at the path level by appending an absolute or wildcard path to the decryption domains option, following similar wildcard logic to the domains themselves. For example:

  // Existing behaviour will be observed, proxying requests to the host 'api.com'.
  const ev = new Evervault('app_uuid', 'api_key', {
    decryptionDomains: ['api.com'],
  });
  
  // Will only proxy requests to host 'api.com' which have a path starting with '/users/'.
  const ev = new Evervault('app_uuid', 'api_key', {
    decryptionDomains: ['api.com/users/*'],
  });
  
  // Will only proxy requests to host 'api.com' which have an exact path of '/settings'.
  const ev = new Evervault('app_uuid', 'api_key', {
    decryptionDomains: ['api.com/settings'],
  });
  

  This change is compatible with the existing hostname wildcard behaviour of decryptionDomains.

6.2.3

Patch Changes

• dc32ede: Add axios dependency

6.2.2

Patch Changes

• 945920d: Remove phin as a dependency as it is unmaintained

6.2.1

Patch Changes

• 1538ebe: fix app key header name

6.2.0

Minor Changes

• 1d40263: Encrypt with just app id

6.1.0

Minor Changes

• 14748f9: Replace ASN.1 encoding library
• f3db4d3: Added createEnclaveHttpsAgent to return an EnclaveAgent class which extends https.Agent to manage HTTPS connections. This Agent can be passed into HTTP clients like Axios to attest a connection to an Enclave.

Patch Changes

• ca97124: remove unused code

6.0.0

Major Changes

• 0feef7d: The Evervault Attestation Bindings have been removed as an external dependency including them instead as a plugin at runtime.

  The attestation bindings now require an explicit opt-in. For customers that do not use Evervault Enclaves, there should be no change to how you use the SDK.

  If you use Evervault Enclaves, you'll need to install the Attestation Bindings separately:

  npm i @evervault/attestation-bindings
  

  After installing the attestation bindings, you can use the existing enableEnclaves function using the bindings as the second parameter:

  const Evervault = require('@evervault/sdk');
  const attestationBindings = require('@evervault/attestation-bindings');
  
  const evervault = new Evervault('app_id', 'api_key');
  await evervault.enableEnclaves(
    {
      'my-enclave': {
        // attestation measures...
      },
    },
    attestationBindings
  );
  

5.1.6

Patch Changes

• 5ffb2ba: Declare helper functions in pcrManager as consts.

5.1.5

Patch Changes

• d0c277c: Correct validation of PCR data given to enableEnclaves - allow for functions to be passed as values in the map.
• 73464ab: Make polling jobs scheduled by the SDK headless to allow processes to exit cleanly.