Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Idea: provide the tool with an authorization token or cookie to test deep pages of a website #49
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
I mean, with an Auth cookie, you poke a hole in a firewall to let someone else in, doesn't you?
I mean, yeah, you could say you trust Google to not be evil, but…
Information like your infrastructure. I imagine even use cases for staging environment here.
Could also be checks for logged in users. But there, you normally have some kind of personalisation. Can you even cover everything?
What if you could run the check „offline“ or without connecting to the Internet?
I'm thinking out loud here :-)
Happy we're having this conversation so definitely thanks for chiming in.
Maybe I'm missing something but I'm not sure this statement's relevancy to the project here.
I think there's some misunderstanding in perhaps how this tool works. It doesn't send anything to Google, nor to Snyk, not any other way that I know of. It doesn't collect any vulnerabilities from remotely or anything like that. See here https://github.com/GoogleChrome/lighthouse#are-results-sent-to-a-remote-server