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.
@flair-sdk/react
Advanced tools
Ready-made React components and hooks for working with ERC721 and ERC1155 NFTs in a web3 dApp. This SDK also supports interacting with Flair smart contracts and extensions.
@flair-sdk/react
Ready-made React components and hooks for working with ERC721 and ERC1155 NFTs in a web3 dApp. This SDK also supports interacting with Flair smart contracts and extensions.
Install the package:
npm install @flair-sdk/react
Install peer dependencies if not installed yet:
npm install ethers wagmi
Visit docs.flair.dev for the full SDK documentation.
FAQs
Ready-made React components and hooks for working with ERC721 and ERC1155 NFTs in a web3 dApp. This SDK also supports interacting with Flair smart contracts and extensions.
The npm package @flair-sdk/react receives a total of 0 weekly downloads. As such, @flair-sdk/react popularity was classified as not popular.
We found that @flair-sdk/react demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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.