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.
@odit/lfk-client-js
Advanced tools
A lib to interact with https://git.odit.services/lfk/backend. Use this version for native JS applications.
The official library for the LfK backend server. Automagicly™ generated by openapi-typescript-codegen
Get's automagicly™ build by drone for every new backend release.
Basic example: Get all tracks
import {OpenAPI, TrackService} from "@odit/lfk-client-js";
OpenAPI.BASE = "https://localhost:4010";
console.log(await TrackService.trackControllerGetAll());
Via yarn/npm:
yarn add @odit/lfk-client-js
# Or
npm i @odit/lfk-client-js
Or just copy the folder dist
to your prefered lib folder and import everything you need from dist/index.ts
.
FAQs
A lib to interact with https://git.odit.services/lfk/backend. Use this version for native JS applications.
The npm package @odit/lfk-client-js receives a total of 3 weekly downloads. As such, @odit/lfk-client-js popularity was classified as not popular.
We found that @odit/lfk-client-js 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.
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.