perpetuals-trading

No evidence of intentional malware or supply-chain sabotage is present. The code is readable financial-protocol sample code, but it contains significant security and correctness risks if deployed as shown: caller-controlled liquidation prices, incomplete oracle validation, possible reentrancy around transfers, missing zero and sign checks, ineffective final funding-rate cap, and incomplete collateral/open-interest accounting. It requires substantial review and hardening before production use.