PAGES
← all tools
◆ Web Application Security

wstg

v4.2 open-source

Free plan: not checked yet · Open source: yes (from the repository)

Comprehensive guide and framework of best practices for testing the security of web applications and web services.

What you can do now

Checking Plays…

Summary

wstg is an open-source web application security testing guide under the Creative Commons Attribution-ShareAlike 4.0 license, read online from its GitHub repository rather than run as software. It is intended for penetration testers, bug bounty researchers, and organizations that need a repeatable framework for assessing web applications, web services, and APIs. Its documentation places it in the OWASPOWASPA nonprofit foundation that publishes open standards, guides, and ranked vulnerability lists—most famously the OWASP Top 10—giving cyber tools a vendor-neutral benchmark to test or report against. web security testing space, organizing checks from information gathering and authentication through injection, client-side, WebAssemblyWebAssemblyA binary instruction format that runs in browsers and server runtimes at near-native speed, letting developers compile C, Rust, or other languages into a portable, sandboxed module any compliant host can execute., and reporting, with stable WSTG test identifiers across versions. The project has had six tracked releases, with the last 71 days ago.

Comprehensive guide and framework of best practices for testing the security of web applications and web services.

How wstg helps

Which security weaknesses are present in my web application or web service?

applies structured testing scenarios across areas such as authentication, authorization, session management, input validation, cryptography, and business logic, but the findings depend on the scenarios selected and the assessment performed

How should I plan a penetration test of my web application?

provides a framework of best-practice testing scenarios that organizes an assessment from information gathering through application-security checks, rather than executing the tests itself

Which web-service security risks should my assessment cover?

includes testing guidance for web services alongside web applications, with scenarios identified by category and number so the coverage can be selected and referenced consistently

Can I identify the exact security test behind a finding in my report?

uses versioned scenario identifiers that link a result to a specific test, while unversioned identifiers may change between guide versions

Which application-security checks are missing from my current review?

lets a tester compare the review against its structured coverage areas, including configuration, authentication, authorization, sessions, input handling, error handling, cryptography, and business logic

How can my security team use the same testing practices across assessments?

supplies a shared framework of documented best practices and versioned scenarios that penetration testers and reviewing teams can use as a common reference

all 9 features, with the evidence for each →

Languages

Not documented

Features

9 capabilities

Built from wstg's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • wstg covers 1 of the 8 vulnerability assessment methods capabilities we track.

What wstg offers you

  • JSON data export1

All capabilities 9 capabilities
Web application testing guide A structured, scenario-based guide covering how to test web applications across a wide range of vulnerability classes, organised into numbered test cases (WSTG-*). 20 releases · 1 other source · first seen Apr 2020

Shared capability: Web vulnerability scanning

Appendices and reference material Supplementary appendices providing supporting reference material such as fuzz vectors, developer tools guidance, and encoded injection strings. 2 releases · first seen Dec 2020
Automated PDF generation Automatically builds and publishes a PDF version of the guide as part of the repository workflow. 2 releases · first seen Apr 2020
Repository content quality checks Automated linting and validation of markdown formatting, hyperlinks, and terminology within the repository. 2 releases · first seen Apr 2020
Community translation support Provides a facility via GitLocalize for community contributors to translate the guide into other languages. 1 release · first seen Dec 2020
Contributor development environment support Supports contributors working directly in the repository via GitHub Codespaces. 1 release · first seen Dec 2020
JSON test checklist artifact Automatically generates a machine-readable JSON checklist derived from the guide's test catalogue. 1 release · first seen Dec 2020

Also counts toward: JSON data export

Automated website publishing Automatically deploys versioned, stable, and latest builds of the guide content to the owasp.org website. 1 release · first seen Apr 2020
Contributor and style guidelines Documented standards for contributing to the project, including a contributor guide, style guide, and content templates. 1 release · first seen Apr 2020

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for wstg, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail wstg puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

2 entries

  1. December 20201
  2. April 20201

    2 entries

    Project health

    Issue, contributor and maintainer activity in owasp/wstg, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors not measured distinct committers, last 12 months
    2. Maintainers not measured core set, last 12 months
    3. Bus factor not measured committers behind half the commits
    4. Community-filed 90% of issues opened, last 12 months
    5. Median time to close 2 years first maintainer reply 2.4 hours
    6. Open backlog 21 of 396 issues ever filed
    1. Issues opened / month 3 · 0 communitymaintainers
    2. Open backlog 21
    3. Contributors / month not measured
    4. Commits / month not measured
    5. Stars not measured
    Issue themes, last 12 months
    • features 14%
    • other 86%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.