the bottom row of a child’s teeth, but the front two teeth have two teeth behind them
🦈 my 6 year old’s “shark teeth”
31.07.2025 20:58 — 👍 6 🔁 0 💬 0 📌 0@jordan.har.band
https://github.com/ljharb software engineer/nerd/teacher/will try anything once; surgeon with git rebase. @TC39 ex @Coinbase/@Airbnb/@Twitter/@MobBase. Fav punctuation ⸮, scent petrichor
the bottom row of a child’s teeth, but the front two teeth have two teeth behind them
🦈 my 6 year old’s “shark teeth”
31.07.2025 20:58 — 👍 6 🔁 0 💬 0 📌 0I’m sure someone does; i don’t
24.07.2025 19:32 — 👍 1 🔁 0 💬 0 📌 0“Are you any good at troubleshooting CSS?” with misaligned answer options
postit found at our team offsite
24.07.2025 19:14 — 👍 66 🔁 9 💬 2 📌 0Big news: HeroDevs just raised $125M from PSG + Album 🎉
We’re doubling down on Never-Ending Support for EOL OSS.
✅ Securing deprecated frameworks
✅ $20M OSS Sustainability Fund now open
Let’s secure the future of open source.
#OSS #DevSecOps #CyberSecurity #EOL #HeroDevs
I’m confused, i still have DMs and don’t see anywhere to age-verify
24.07.2025 06:29 — 👍 0 🔁 0 💬 1 📌 0*recalls* ok yeah this is funny
23.07.2025 23:18 — 👍 1 🔁 0 💬 0 📌 0can you provide some context? i have no idea what Clinton signifies here
23.07.2025 23:08 — 👍 1 🔁 0 💬 1 📌 0not me, a co-maintainer in a package.
the malware never existed in the repo, and no longer exists on npm.
🚨 Attackers have hijacked the npm 'is' package (~2.8M weekly downloads), adding a malicious JS loader. This compromise is linked to the recent npm phishing campaign. Read our update on this ongoing supply chain attack: socket.dev/blog/npm-is-... #NodeJS #JavaScript
22.07.2025 20:09 — 👍 11 🔁 7 💬 1 📌 0to complement my hither-thither staff, a hen-then staff?
23.07.2025 03:41 — 👍 2 🔁 0 💬 1 📌 0oh hey look, it’s the actual solution for the thing that provenance will always fail to achieve that I’ve been telling folks to do for years and getting scoffed at security.googleblog.com/2025/07/intr...
22.07.2025 16:19 — 👍 5 🔁 2 💬 0 📌 0The two bad versions have now been taken down entirely by @npmjs.bsky.social, thankfully.
21.07.2025 05:17 — 👍 9 🔁 1 💬 1 📌 0I want to reiterate my deeply held belief. One of the biggest mistakes we are making with this tech is anthropomorphizing it and treating it like it is actually "reasoning". It's not doing that. And it cannot be held accountable. It's a machine.
20.07.2025 20:34 — 👍 380 🔁 82 💬 6 📌 6ask a silly question ¯\_(ツ)_/¯
20.07.2025 01:57 — 👍 0 🔁 0 💬 0 📌 0Mostly because it’s been around while - the modern approach is to use a single-purpose package instead of a grab bag. Just like lodash.
19.07.2025 22:00 — 👍 0 🔁 0 💬 1 📌 0npm does require that now, and the package itself can’t be published without 2FA. an email takeover tho is sort of always the master key
19.07.2025 22:00 — 👍 0 🔁 0 💬 0 📌 0true. but my assumption is that the hijacking caused it to get removed, but i wasn’t notified, so when he asked to be re-added it seemed normal.
19.07.2025 21:03 — 👍 2 🔁 0 💬 1 📌 0lol k so basically all of them, got it
19.07.2025 19:54 — 👍 4 🔁 0 💬 0 📌 0What they claimed was that their account did not have 2FA set up, and that’s why it was removed. Which seemed plausible, but made me irritated at npm. I am pretty confident that a username, once deleted, is burned forever.
19.07.2025 18:55 — 👍 1 🔁 0 💬 0 📌 0also, v5.0.0, which got the same treatment. I assume this was from a pre-existing session and one of npm’s publish servers hadn’t caught up yet - tokens are disallowed (on virtually all my packages)
19.07.2025 18:50 — 👍 3 🔁 0 💬 0 📌 0huh? No. I mean the account was removed from the package, not removed from npm
19.07.2025 18:49 — 👍 0 🔁 0 💬 1 📌 0multiple people noticed and notified me through various channels. I was volunteering at my kid’s swim meet, so I didn’t get the messages until it was over.
19.07.2025 18:36 — 👍 3 🔁 0 💬 0 📌 0Unfortunately, this took 6! hours before it was noticed. It would’ve been 1-2, but I was volunteering at my kids’ swim meet.
19.07.2025 18:34 — 👍 10 🔁 0 💬 0 📌 0It’s entirely possible. The old owner was somehow removed from the npm package, and emailed me to be re-added. Everything seemed normal, so I obliged (irritated the npm would remove an owner without notifying the other owners) and the next morning this was published.
19.07.2025 18:33 — 👍 4 🔁 0 💬 2 📌 1show me something that isn’t shit in this way, lol. get better takes.
19.07.2025 18:31 — 👍 6 🔁 0 💬 1 📌 0Heads up that v3.3.1 of npmjs.com/is has malware in it, due to another maintainer’s account being hijacked. They’re removed for now, v3.3.0 is set at latest, v3.3.1 is deprecated, and a v3.3.2 will be published once I’m not on my phone (thx @github.com codespaces)
19.07.2025 18:21 — 👍 43 🔁 21 💬 7 📌 4Harborist has published a new CVE:
www.cve.org/cverecord?id...
This is on all versions of the npmjs.com/form-data package, on all node versions. Please note: node 18+ and all modern browsers (caniuse.com?search=formd...) have FormData built in - please consider migrating to it!
I made a quiz about the JS Date parser is. It's very easy and you will score very high.
jsdate.wtf
congrats!
08.07.2025 16:50 — 👍 2 🔁 0 💬 1 📌 0sounds, taps, and/or pictures?
02.07.2025 21:02 — 👍 1 🔁 0 💬 1 📌 0