3 ms·
We look at the behavior of packages, what APIs they use, and how that changes over time. The list of issues we currently look for is here: https://socket.dev/np
by feross 5y ago
We look at the behavior of packages, what APIs they use, and how that changes over time. The list of issues we currently look for is here: https://socket.dev/npm/issue https://socket.dev/npm/issue
Socket’s not open source at this time, but we’re releasing a CLI in the coming week if the GitHub App doesn’t suit your purposes.
- huynhhacnguyen 5y agoThat's actually interesting, I will look into more details to see if we can integrate this into our systems. Do you have any avaiable technical documents so we can get a glimpse of how Socket is working, or is your Blog the best place to start?
- pabs3 5y agoRe the typosquat issue, maybe also add bitsquatting https://www.youtube.com/watch?v=lZ8s1JwtNas https://www.youtube.com/watch?v=lZ8s1JwtNas https://github.com/artemdinaburg/bitsquat-script/ https://github.com/artemdinaburg/bitsquat-script/
- pabs3 5y agoI absolutely love that you added a telemetry issue! I'm linking your page about it from the Debian privacy issues page. https://socket.dev/npm/issue/telemetry https://socket.dev/npm/issue/telemetry https://wiki.debian.org/PrivacyIssues https://wiki.debian.org/PrivacyIssues