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.
@vonage/vetch
Advanced tools
Vonage's type and enum definitions module for server-side HTTP interactions.
This is the Vonage Vetch
er SDK for Node.js used to wrap a request using node-fetch
to call Vonage APIs. To use it you will need a Vonage account. Sign up for free at vonage.com.
For full API documentation refer to developer.vonage.com.
npm install @vonage/vetch
yarn add @vonage/vetch
Vetch will return a VetchResponse
const { request } = require('@vonage/vetch');
const response = await request({
url: 'https://rest.nexmo.com/account/numbers'
})
console.log(response.data);
// Will output the json data from the API response
options
are a superset from the request package. See VetchOptions
for more detail
Run:
npm run test
FAQs
Vonage's type and enum definitions module for server-side HTTP interactions.
The npm package @vonage/vetch receives a total of 45,740 weekly downloads. As such, @vonage/vetch popularity was classified as popular.
We found that @vonage/vetch demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 43 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.