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.
@tryvital/vital-node
Advanced tools
[![npm shield](https://img.shields.io/npm/v/@tryvital/vital-node)](https://www.npmjs.com/package/@tryvital/vital-node) [![fern shield](https://img.shields.io/badge/%F0%9F%8C%BF-SDK%20generated%20by%20Fern-brightgreen)](https://github.com/fern-api/fern)
The Vital Node.js library provides access to the Vital API from JavaScript/TypeScript.
API reference documentation is available here.
npm install --save @tryvital/vital-node
# or
yarn add @tryvital/vital-node
import { VitalClient, VitalEnvironment } from '@tryvital/vital-node';
const vital = new VitalClient({
apiKey: 'YOUR_API_KEY',
});
const labTest = await vital.labTests.get('order-id');
console.log('Received lab test', labTest);
When the API returns a non-success status code (4xx or 5xx response), a subclass of VitalError will be thrown:
try {
await vital.labTests.get('order-id');
} catch (err) {
if (err instanceof VitalError) {
console.log(err.statusCode);
console.log(err.message);
console.log(err.body);
}
}
When you sign up to Vital you get access to two environments, Sandbox and Production.
Environment URLs | |
---|---|
production | api.tryvital.io |
production-eu | api.eu.tryvital.io |
sandbox | api.sandbox.tryvital.io |
sandbox-eu | api.sandbox.eu.tryvital.io |
By default, the SDK uses the production
environment. See the snippet below
for an example on how ot change the environment.
import { VitalClient, VitalEnvironment } from '@tryvital/vital-node';
const vital = new VitalClient({
apiKey: 'YOUR_API_KEY',
environmment: VitalEnvironment.Sandbox,
});
Each method in the SDK accepts an additional optional parameter where you can specify request options such as a timeout.
const labTest = await vital.labTests.get('order-id', {
timeoutInSeconds: 40 // wait 40 seconds for this call
});
This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning the package version to a specific version in your package.json file. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.
While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!
On the other hand, contributions to the README are always very welcome!
FAQs
[![npm shield](https://img.shields.io/npm/v/@tryvital/vital-node)](https://www.npmjs.com/package/@tryvital/vital-node) [![fern shield](https://img.shields.io/badge/%F0%9F%8C%BF-SDK%20generated%20by%20Fern-brightgreen)](https://github.com/fern-api/fern)
We found that @tryvital/vital-node demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 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.