2 ms·
I work as a security engineer for a benefits provider. This stuff has been top of mind for me, the rest of my team, and our CSIO. I love the direction you're g
by d4mi3n 5y ago
I work as a security engineer for a benefits provider. This stuff has been top of mind for me, the rest of my team, and our CSIO.
I love the direction you're going with this. Would love to hear more about:
1. Status. Is this a beta product or do you have enough here to sell a service?
2. Roadmap. What are you building out next? What are core capabilities you see being added to Socket?
3. Pricing. How much does it cost? What's your revenue model?
Depending on how you've put this together you may be addressing a serious need in this space that I've only previously seen addressed by stuff like Deno (where you set application capabilities prior to execution) or via virtualization.
Contact details in my profile. If your product does what it says on the tin I'd love to give it a spin.
- bretc 5y ago1. We are in beta right now! We have the data and analysis, and are working hard to make it easy to integrate project specific views into it. 2. https://socket.dev/roadmap https://socket.dev/roadmap See https://socket.dev/npm/issue https://socket.dev/npm/issue for analysis we have developed on a per-package basis. We are working on integrating these with our GitHub App to provide custom tailored project views into this data. More info here https://socket.dev/blog/inside-node-modules https://socket.dev/blog/inside-node-modules 3. It will be a paid product, but is free while it is in beta. We plan on keeping it free for open source. We are looking into providing support for the Deno ecosystem down the road as well. The capabilities stuff they have is super great, but you lose all of that benefit for every dependency as soon as you turn it off, so we think there is probably room for this kind of analysis there. Hopefully Socket can provide a similar signal that --allow-net provides, but for all of npm!