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.
@avalabs/glacier-sdk
Advanced tools
This package contains typescript api generated from the openAPI file from glacier.
To generate a new version based on the latest changes from glacier dev run:
$ yarn codegen
const glacierApi = new V1("https://glacier-api.avax.network/")
const resp = glacierApi.getNativeBalance(")
After running the codegen
script, you may encounter build errors that look like this:
This is caused by changes to the Glacier API schema, and the GlacierClient
class in src/glacierClient.ts
that wraps auto-generated code from the API schema as this code is not updated automatically during code generation.
Please see PR #371 for an example of the type of update that must be made in order resolve the above error, in particular this commit.
FAQs
sdk for interacting with glacier-api
The npm package @avalabs/glacier-sdk receives a total of 1,393 weekly downloads. As such, @avalabs/glacier-sdk popularity was classified as popular.
We found that @avalabs/glacier-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.