Comment on page
Why should I use listen.dev?
listen.dev is provides a unique solution that provides behavioural insights on dependencies during the development lifecycle. Dev-time observability on open source packages can be used to proactively detect issues that could affect the security and performance of your software.
How do i get started?
How do you protect unknown risks?
Our analysis engine and team constantly monitors the npm registry and flags abnormal behavior (which could potentially indicate malicious activity), and alerts users so they can investigate or block risky dependencies before using them.
What type of attacks do you prevent?
How does listen.dev ensure the privacy of my data? What permissions does it have?
We only read the manifest files (such as package.json) and metadata inside your project’s repository. We do not read any of your code or sensitive data, neither do we run any of your code on your servers. If you want to learn more, check out the detailed docs and our client code which is open source. If you have any specific concerns or feedback, we would love to chat 1:1.
What are the requirements to deploy listen.dev?
Last modified 9mo ago