is-website-vulnerable alternatives and similar modules
Based on the "Security" category.
Alternatively, view is-website-vulnerable alternatives based on common mentions on social networks and blogs.
6.9 9.7 L3 is-website-vulnerable VS snykCLI and build-time tool to find & fix vulnerable npm dependencies.
Crypto library for storage and messaging
CLI tool to identify possible regex denial of service (ReDos) vulnerabilities in your project.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of is-website-vulnerable or a related project?
Many thanks to for supporting open source security
npx to run a one-off scan of a website:
npx is-website-vulnerable https://example.com [--json] [--js-lib] [--mobile|--desktop] [--chromePath] [--cookie] [--token]
The CLI will gracefully handle cases where the URL to scan is missing by prompting you to enter it:
$ npx is-website-vulnerable Woops! You forgot to provide a URL of a website to scan. ? Please provide a URL to scan: › https://example.com ...
If the CLI detects an error, it will terminate with an exit code different from 0.
Exit Code 0: Everything is fine. No vulnerabilities found.
Exit Code 1: An error happened during the execution. Check the logs for details.
Exit Code 2: Vulnerabilities were found. Check the logs for details.
To build and run the container locally:
# Clone Repo: git clone https://github.com/lirantal/is-website-vulnerable.git # Change to repo's cloned directory: cd is-website-vulnerable # Build Image locally: docker build --no-cache -t lirantal/is-website-vulnerable:latest . # Run container: docker run --rm -e SCAN_URL="https://www.google.com/" lirantal/is-website-vulnerable:latest
SCAN_URL is an environment variable and its value must be replaced with the desired URL during Docker run. Docker container will exit once the scan has been completed.
:warning: A modern version of Chrome is assumed to be available when using
is-website-vulnerable. It may not be safe to assume that this is satisfied automatically on some CI services. For example, additional configuration is necessary for Travis CI.
Create .github/workflows/is-website-vulnerable.yml with the url that you want scanned:
You can install globally via:
npm install -g is-website-vulnerable
Please consult [CONTRIBUTING](./CONTRIBUTING.md) for guidelines on contributing to this project.
is-website-vulnerable © Liran Tal, Released under the [Apache-2.0](./LICENSE) License.
*Note that all licence references and agreements mentioned in the is-website-vulnerable README section above are relevant to that project's source code only.