We're excited to announce that Socket is joining the @openjsf Proud to support the #JavaScript ecosystem alongside so many great projects and contributors.
We're excited to announce that Socket is joining the @openjsf Proud to support the #JavaScript ecosystem alongside so many great projects and contributors.
I made a new thing! like the semver package, but for PURLs: https://www.npmjs.com/package/purl
`npx purl $specifier` or `npx purl $purl` will validate, normalize, and provide parse info.
add `--check` & it'll contact the relevant registry & verify the package and version exist.
(you can import it too)
I made something new: an eslint plugin to validate your npm ecosystem lockfiles! It supports npm, pnpm, yarn, bun, and vlt, and it's already helped find a supply chain security attack vector inside a fortune 500 tech company. https://www.npmjs.com/package/eslint-plugin-lockfile
You can also run the eslint rule as a standalone CLI! `npx lintlock` / https://www.npmjs.com/package/lintlock
(all written in ESM, all with minimal deps, all supporting only modern node, for those that care about that sort of thing)
Exciting news for me and @nodejs today (ノ◕ヮ◕)ノ*:・゚✧
- https://github.com/nodejs/node/issues/55918
- https://github.com/nodejs/node/pull/56132
@nilesh Oof, `funding.json` seems like it assumes there's a project website (most projects don't have one) and for those projects, requires a file checked into the root of repo (messy, not scalable for those with dozens or hundreds of projects)
also `npm fund` already exists for the JS ecosystem and they should be using that format.