Kevin Deng

@sxzz.dev

https://github.com/sxzz • 🏳️‍🌈 Gen Z • indie OSS developer sponsored by @voidzero.dev @vuejs.org @vite.dev @vue-macros.dev @vueuse.org @unjs.io @rolldown.rs elk.zone More at https://sxzz.dev/

Glad to help move the ecosystem toward: - ESM-only - TypeScript - OIDC + staged publishing - Runtime-agnostic design wherever possible - No bundled deps unless needed - Like-minded dependencies I’ve replaced `debug` and `semver` with `obug` and `verkit`. What’s next? 🤔

James@43081j.com · 2w ago

good timeline. this is magic-string, 140M dls/week. a week ago i asked if it could go ESM only - @sxzz.dev dropped a PR <1 day later 🎉 later, I removed sourcemaps and did 2 big CPU perf speed ups 🚀 love seeing a high impact package like this shrink and speed up

magic-string package dropping by 56% (304.9KB), then later by another 36% (86.8KB). Also changed to ESM only and enabled trusted publishing/provenance.

The tsdown ecosystem, visualized ✨ Each circle = a project owner using tsdown, sized by GitHub stars. 873 projects over 100 stars and counting. Grateful to everyone shipping with it.

Bild

⚡ After `rolldown-plugin-dts` migrated Babel toolchain to yuku, tsdown has cut ~5 MB from its install size and is now smaller than tsup. ❤️ Huge thanks to arshad-yaseen for the help!

We've started by verifying npmx maintainers. Log in to mu.social to see the verified badges! We'd like to discuss the best strategy for our communities with OSS maintainers. Should all large enough OSS projects be verifiers? Or would it be better for a few orgs/foundations to take on the task?

Eurosky Social@eurosky.social · 2mo ago

We're delighted to launch with multiple trusted verifiers: @france-atmosphe.re @npmx.dev and @medsky.network. Trusted organizations, businesses and professional networks can become verifiers and verify their people and accounts - reach out at verification@mu.social

Hello friends and welcome to another “how’s ESM vs CJS doing?!” A big win this time, at a year of `require(esm)` available! 38.0% of the popular npm packages now have ESM, up from 33.4% half a year ago. ESM-only is up from 12.6% to 16.0%. Particularly this non-dual, “vanilla” growth is very big!

Graph showing the status, in raw CSV:

```csv
date,total,esm,dual,faux,cjs
2021-08-24,5617,341,95,832,4349
2021-11-09,5647,411,119,809,4308
2022-08-01,5734,496,207,791,4240
2022-11-04,5747,518,216,785,4228
2023-05-29,6240,630,417,783,4410
2023-11-22,6818,734,510,881,4693
2024-05-27,7042,819,736,826,4661
2024-11-27,8087,942,1152,843,5150
2025-06-05,8677,995,1573,859,5250
2025-12-04,14159,1779,2947,1522,7911
2026-06-08,16231,2590,3574,1689,8378
```

📦 @pnpm.io 11.5 adds support for recognizing npm staged publishes after staged approval metadata triggered a false downgrade signal. As npm adds more release paths, registry metadata needs to make it clear how each package version was published. socket.dev/blog/pnpm-11...

pnpm 11.5 Adds Support for Recognizing npm Staged Publishes ...

pnpm 11.5 now recognizes npm staged publish approvals in release metadata, preventing those releases from being mistaken for lower-trust package publi...

socket.dev

npm increasingly feels like a zombie org under GitHub. As someone who's been around the JS ecosystem and part of multiple OSS orgs for years, what I'm seeing isn't just "big co moves slow." It's quiet neglect of critical infrastructure the entire JS world runs on. A short thread 🧵

PSA: the safest way to publish an npm package today is staged publish + OIDC + provenance. "But it can't stop every attack." Sure, and seatbelts don't prevent every injury either. We still wear them. Security is layers, not silver bullets.

Tracking npm provenance adoption across the top ~15k high-impact packages. Now with daily trend data 📈 Since Aug 2025: • Trusted Publisher: 0.55% → 16.69% • Provenance: 6.96% → 3.14% • Untrusted: 92.49% → 80.17% Trusted Publisher adoption is climbing fast! github.com/sxzz/npm-top...

Bild

The actions-cool/issues-helper compromise showed a nasty edge case: Even pinned SHAs can still break if the action repo gets disabled. I built actionspack to inline actions/workflows where possible, pin what remains, and make dependency updates visible in git diff.

Kevin Deng@sxzz.dev · 3mo ago

Recent supply-chain poisoning incidents made one thing obvious: CI should not blindly trust floating @main refs. actionspack brings a pnpm-like lockfile to GitHub Actions: author in .github/workflows/src, inline safe workflows/actions, pin the rest to SHAs, and review updates with git diff.

Recent supply-chain poisoning incidents made one thing obvious: CI should not blindly trust floating @main refs. actionspack brings a pnpm-like lockfile to GitHub Actions: author in .github/workflows/src, inline safe workflows/actions, pin the rest to SHAs, and review updates with git diff.

GitHub - sxzz/actionspack: Lockfile-first GitHub Actions workflow packer

Lockfile-first GitHub Actions workflow packer. Contribute to sxzz/actionspack development by creating an account on GitHub.

github.com