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.
snyk7.4 9.9 L3 is-website-vulnerable VS snykSnyk CLI scans and monitors your projects for security vulnerabilities. [Moved to: https://github.com/snyk/cli]
rate-limiter-flexibleCount and limit requests by key with atomic increments in single process or distributed environment.
nsp6.0 0.0 L5 is-website-vulnerable VS nspNode Security Project command-line tool
Themis by Cossack LabsEasy to use cryptographic framework for data protection: secure messaging with forward secrecy and secure data storage. Has unified APIs across 14 platforms.
Auto SNI🔐 Free, automated HTTPS for NodeJS made easy.
crypto-hashTiny hashing module that uses the native crypto API in Node.js and the browser
credential-plus🔒Unified API for password hashing algorithms
RegEx-DoS:cop: :punch: RegEx Denial of Service (ReDos) Scanner
unix-permissionsSwiss Army knife for Unix permissions
jose-simpleJose-Simple allows the encryption and decryption of data using the JOSE (JSON Object Signing and Encryption) standard.
💀 SimpleDDoS💀 Multi-threaded DDoS script
GuardRailsGitHub app that provides security feedback in pull requests.
Appwrite - The Open Source Firebase alternative introduces iOS support
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
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.
If you wish to provide command line arguments to
is-website-vulnerable and customize the run, such as providing
--json or other supported arguments, you should omit the environment variable and provide the full command. Here is an example:
docker run --rm lirantal/is-website-vulnerable:latest https://www.google.com --json
: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.