I’ve been working successfully with my extensions and widgets experiments for the past few weeks.
So I thought I share it with you and get new ideas and suggestions to improve it.
👉 Say hello to Xtended!
https://t.co/E3lo448yPM
🚨 How the TanStack npm attack actually happened:
1. Attacker opened a normal-looking pull request (#7378) on the TanStack repo.
2. GitHub automatically ran CI tests on that PR.
3. Code inside the PR stole the workflow's GitHub Actions Cache write token during the test run.
4. The attacker used that token to plant poisoned files in the shared build cache. The PR could be closed afterwards. The poisoned cache stays.
5. The official release workflow later pulled from the cache, baked the malicious files into the build, and signed and published 84 malicious package versions to npm.
Drizzle v1.0.0-rc.1 is out 🚀
▪︎ Effect v4 native support
▪︎ JIT row mappers to reduce ORM overhead to ~0
▪︎ Reworked casing API (breaking change)
▪︎ Drizzle for LLM agents (preview)
Drizzle is now as fast as using raw driver and mapping(or not mapping) results by hand 🙃
We’ve identified a security incident that involved unauthorized access to certain internal Vercel systems, impacting a limited subset of customers. Please see our security bulletin:
https://t.co/0S939n3qHC
🛡️ React Native Security Rule #6 :
AsyncStorage is NOT secure storage.
If you save tokens, passwords, or credentials there, you’re storing them in plaintext. On rooted/jailbroken devices, attackers can dump it in seconds.
AsyncStorage is fully readable.
Treat it as public, not private.
Never store:
• auth tokens
• passwords
• API secrets
Use instead:
• expo-secure-store
• react-native-keychain
• native Keychain / Keystore
@ThomasBurkhartB Same, this is one of the heavy aloy knobs, they feel super satisfying. Is the condensator thing causing noise? I get that from time to time
@ThomasBurkhartB@pedromassangom I understand, it’s a crowded room with too little incentive to do well, especially financial one. Glad you could find a way to make it work