wstg
v4.2 open-sourceFree plan: not checked yet · Open source: yes (from the repository)
The section your link pointed to isn't on wstg's page any more, so we've brought you to the top.
Comprehensive guide and framework of best practices for testing the security of web applications and web services.
What you can do now
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
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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…
Releases
2 entries
No entries match these filters.
- December 20201
- April 20201
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.
- Contributors not measured distinct committers, last 12 months
- Maintainers not measured core set, last 12 months
- Bus factor not measured committers behind half the commits
- Community-filed 90% of issues opened, last 12 months
- Median time to close 2 years first maintainer reply 2.4 hours
- Open backlog 21 of 396 issues ever filed
- Issues opened / month 3 · 0 communitymaintainers
- Open backlog 21
- Contributors / month not measured
- Commits / month not measured
- Stars not measured
- 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.