Skip to content

Conversation

@uowwnui
Copy link

@uowwnui uowwnui commented Sep 20, 2025

Spin.Fun – The Fair Crypto Lucky Draw 🎰

Spin.Fun is a gamified crypto platform where players pay 1 USDT to spin for a random token from a pool of 100 boxes filled with top coins like BTC, ETH, SOL, and DOGE.

Each box always equals about $1 of crypto. After every spin, 0.99 USDT is used to buy back the token on-chain to refill the pool, while 0.01 USDT goes to the team.

With only a 1% house edge, Spin.Fun is fair, transparent, and fun — turning crypto into a lucky draw arcade where everyone can play, win, and share the excitement.

@socket-security
Copy link

@socket-security
Copy link

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
[email protected] has Obfuscated code.

Confidence: 0.94

Location: Package overview

From: ?npm/[email protected]npm/[email protected]

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant