Hacker News new | past | comments | ask | show | jobs | submit login

The difference is that you have a single file to audit with npm. With Deno, any file in your codebase might pull in a dependency.





Which isn't really a problem for simple one-file 'shell scripts'. For bigger projects, Deno already suggested to maintain all external imports in a central file.

That assumes someone is actually auditing the npm deps.

It’s trivial to audit your dependencies with https://socket.dev

Disclosure: I’m the founder.


Despite the ease of auditing services, there are notoriously a lot of devs using unaudited deps. Maybe they don't even think about it, unfortunately.



Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: