Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
num-client
Advanced tools
A TypeScript/JavaScript client for the NUM protocol.
See the full Specification at the NUM Protocol Website and the Explainer for more information.
The NUM protocol supports a range of modules that add rich functionality in an extensible way.
The NUM protocol uses the familiar URL format for its URIs and allows modules to interpret data in a variety of ways.
The data stored in a NUM Record is converted to JSON String format that can be parsed into JSON objects for straightforward incorporation into TypeScript and JavaScript programs. Here are some example NUM URIs with module 1
- the Contacts module. The default module is 0
(zero) if no module is specified, which has no module schema.
num://numexample.com:1
num://jo.smith@numexample.com:1
num://jo.smith@numexample.com:1/work
num://jo.smith@numexample.com:1/personal
num://jo.smith@numexample.com:1/hobbies
num://numexample.com:1/support
num://numexample.com:1/support/website
num://numexample.com:1/support/delivery
num://numexample.com:1/enquiries
num://numexample.com:1/sales
As you can see from the examples above, data can be associated with domains and email addresses, and can be organised hierarchically if desired. In future, the protocol will support more than just domains and email addresses.
Additional modules can be referenced in the same way as ports
in other URIs:
num://numexample.com:2
for the Registrant module.num://numexample.com:3
for the Images module.num://numexample.com:4
for the Custodians module.num://numexample.com:5
for the Payments module.num://numexample.com:6
for the Regulatory module.num://numexample.com:7
for the Public Key module.num://numexample.com:8
for the Intellectual Property module.num://numexample.com:9
for the Terms module.num://numexample.com:10
for the Bugs module.num://numexample.com:nn
for your own module?Install using:
npm install -s num-client
Use this import to make the client available for use:
import {
createClient, // required for creating the `NUMClient`
createDnsClient, // optional unless you need to override the default DoH endpoint
parseNumUri, // required for converting the NUM URI string into a valid `NumUri` object
CallbackHandler, // optional unless you need to provide a custom callback handler implementation
DoHResolver, // optional unless you need to override the default DoH endpoint
Location // optional unless you need to provide a custom callback handler implementation
} from 'num-client';
The programming interface is very simple:
const lookup = async () => {
const numUri = parseNumUri('num.uk:1'); // Parse the NUM URI
const client = createClient(); // Create a NumClient
const ctx = client.createContext(numUri); // Set the lookup context
const result = await client.retrieveNumRecord(ctx); // Use the context to retrieve a NUM record
console.log(result); // Handle the result
}
NUMClient
The same NUMClient
can be reused for multiple lookups, as in this example:
const lookup = async () => {
const numUri1 = parseNumUri('num.uk:1');
const numUri2 = parseNumUri('numexample.com:1');
const client = createClient(); // This client is reused for multiple contexts
const ctx1 = client.createContext(numUri1);
const ctx2 = client.createContext(numUri2);
const result1 = client.retrieveNumRecord(ctx1);
const result2 = client.retrieveNumRecord(ctx2);
const result = await Promise.all([result1, result2]);
console.log(result[0]);
console.log(result[1]);
}
By default the NUMClient
uses the Google DoH resolver, although it can be changed if required by providing a DoHResolver
to a service that supports the JSON API for DNS over HTTPS (DoH).:
const lookup = async () => {
// ...
const DEFAULT_RESOLVER = new DoHResolver('Google', 'https://dns.google.com/resolve');
const client = createClient([DEFAULT_RESOLVER]); // Use a custom DoH service
// ...
};
Some modules can be provided with User Variable values to customise the output, as in this example:
const lookup = async () => {
const numUri = parseNumUri('num.uk:1'); // Parse the NUM URI
const client = createClient(); // Create a NumClient
const ctx = client.createContext(numUri); // Set the lookup context
ctx.setUserVariable('_L', 'en'); // Set the user's language
ctx.setUserVariable('_C', 'gb'); // Set the user's country
const result = await client.retrieveNumRecord(ctx); // Use the context to retrieve a NUM record
console.log(result) // Handle the result
}
CallbackHandler
Lookups can take several seconds, so you can provide a CallbackHandler
rather than await
ing the results:
const lookup = async () => {
const numUri = parseNumUri('num.uk:1'); // Parse the NUM URI
const client = createClient(); // Create a NumClient
const ctx = client.createContext(numUri); // Set the lookup context
const handler: CallbackHandler = {
setLocation: (l: NumLocation): void => {
console.log(l); // `l` is the `Location` where the result was found
},
setResult: (r: string): void => {
console.log(r); // `r` is the NUM record as a JSON string
},
setErrorCode: (e: string): void => {
console.log(e); // `e` is the error message
}
};
client.retrieveNumRecord(ctx, handler).then((_r) => {
// Ignore because the callback handler will handle it
}, (err) => console.error(err));
}
This example shows the minimal requirements for using the NUM Client:
const num = require('num-client');
function lookup(uri) {
const numUri = num.parseNumUri(uri);
const client = num.createClient();
const ctx = client.createContext(numUri);
return client.retrieveNumRecord(ctx);
}
lookup('num.uk:1').then((result) => console.log(result));
This example shows how to use all features of the client, including
NUMClient
const num = require('num-client');
function lookup(uri1, uri2) {
const numUri1 = num.parseNumUri(uri1);
const numUri2 = num.parseNumUri(uri2);
const DEFAULT_RESOLVER = new num.DoHResolver('Cloudflare', 'https://cloudflare-dns.com/dns-query');
const client = num.createClient([DEFAULT_RESOLVER]);
const ctx1 = client.createContext(numUri1);
const ctx2 = client.createContext(numUri2);
ctx1.setUserVariable('_L', 'en'); // Set the user's language
ctx1.setUserVariable('_C', 'gb'); // Set the user's country
ctx2.setUserVariable('_L', 'en'); // Set the user's language
ctx2.setUserVariable('_C', 'us'); // Set the user's country
const handler = { // Provide a custom CallbackHandler
setLocation: (l) => {
console.log(l); // `l` is the `Location` where the result was found
},
setResult: (r) => {
console.log(r); // `r` is the NUM record as a JSON string
},
setErrorCode: (e) => {
console.log(JSON.stringify(e));
}
};
const result1 = client.retrieveNumRecord(ctx1, handler);
const result2 = client.retrieveNumRecord(ctx2, handler);
return Promise.all([result1, result2]);
}
lookup('num.uk:1', 'numexample.com:1').then((result) => {
// Ignore because the callback handler will handle the results.
});
This simple example can be modified as necessary by following the previous examples above.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>NUM Protocol Example</title>
</head>
<body>
<script src="../dist/bundle.js"></script>
<h1>NUM Protocol Example</h1>
<div>
NUM URI = <input type="text" value="num.uk:1" id='urivalue' onchange="reloadRecord()">
<input type="button" value="Reload" onclick="reloadRecord()">
</div>
<div style="border: 1px solid blue;width: fit-content;">
<pre id='num'></pre>
</div>
<script>
const CUSTOM_RESOLVERS = [
new NumClient.DoHResolver('Cloudflare', 'https://cloudflare-dns.com/dns-query')
];
const client = NumClient.createClient(CUSTOM_RESOLVERS);
function lookup(uri) {
const numUri = NumClient.parseNumUri(uri);
const ctx = client.createContext(numUri);
return client.retrieveNumRecord(ctx);
}
function reloadRecord() {
const uri = document.getElementById('urivalue').value;
lookup(uri).then((result) => {
const pretty = JSON.stringify(JSON.parse(result), null, 1);
document.getElementById('num').innerHTML = pretty;
});
}
window.addEventListener('load', function () {
reloadRecord();
});
</script>
</body>
</html>
FAQs
A NUM Protocol Client in TypeScript
The npm package num-client receives a total of 3 weekly downloads. As such, num-client popularity was classified as not popular.
We found that num-client demonstrated a not healthy version release cadence and project activity because the last version was released 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.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.