Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@neosync/sdk
Advanced tools
This SDK contains the generated types for Neosync API. This SDK is dogfooded by the main Neosync webapp to ensure its durability.
npm install @neosync/sdk
For a prime example of how to us this SDK, view the withNeosyncContext method in the Neosync app's BFF layer.
Based on your usage, you'll have to install a different version of connect
to provide the correct Transport based on your environment.
Install whichever one makes sense for you
npm install @connectrpc/connect-node
npm install @connectrpc/connect-web
Neosync API serves up Connect
, which can listen using Connect, gRPC, or Web protocols.
Each of the libraries above provides all three of those protocols, but it's recommended to use createConnectTransport
for the most efficient setup.
import { getNeosyncClient } from '@neosync/sdk';
import { createConnectTransport } from '@connectrpc/connect-node';
const neosyncClient = getNeosyncClient({
getTransport(interceptors) {
return createConnectTransport({
baseUrl: '<url>',
httpVersion: '2',
interceptors: interceptors,
});
},
});
To authenticate the TS Neosync Client, a function may be provided to the configuration that will be invoked prior to every request. This gives flexability in how the access token may be retrieved and supports either a Neosync API Key or a standard user JWT token.
When the getAccessToken
function is provided, the Neosync Client is configured with an auth interceptor that attaches the Authorization
header to every outgoingn request with the access token returned from the function.
This is why the getTransport
method receives a list of interceptors, and why it's important to hook them up to pass them through to the relevant transport being used.
import { getNeosyncClient } from '@neosync/sdk';
import { createConnectTransport } from '@connectrpc/connect-node';
const neosyncClient = getNeosyncClient({
getAccessToken: () => process.env.NEOSYNC_API_KEY,
getTransport(interceptors) {
return createConnectTransport({
baseUrl: process.env.NEOSYNC_API_URL,
httpVersion: '2',
interceptors: interceptors,
});
},
});
In the Neosync dashboard app, we pull the user access token off of the incoming request (auth is configured using next-auth
.).
This way we can ensure that all requests are using the user's access token and are passed through to Neosync API.
FAQs
Neosync SDK
We found that @neosync/sdk demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.