Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Nice write up. It would be great if the authors could follow up with a detailed technical walk through of how to use the various tooling to figure out what an extension is really doing.

Could one just feed the extension and a good prompt to claude to do this? Seems like automation CAN sniff this kind of stuff out pretty easily.





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

Search: