https://pentestkit.co.uk/ · Developer Tools
1 item
OWASP Penetration Testing Kit Automation PTK Auto is the browser automation companion for OWASP Penetration Testing Kit. It provides the browser-side security runtime used by PTK Agent, automated tests, CI/CD pipelines and supported browser-testing platforms. PTK Auto is controlled programmatically. It allows security checks to run inside the same browser session and user workflow created by Playwright, Puppeteer, Selenium, Cypress or another supported automation client. Use PTK Auto to: Add OWASP PTK security checks to existing browser automation. Test authenticated workflows using the browser state created by the automated scenario. Capture browser-generated requests and responses during a test. Run configured DAST checks against selected requests and parameters. Analyse loaded client-side code with PTK SAST. Observe security-relevant runtime behaviour with PTK IAST. Identify vulnerable client-side dependencies with PTK SCA. Return structured findings and evidence to the controlling automation client. Run security tests locally, in CI/CD or through supported hosted-browser platforms. PTK Auto works with PTK Agent, published as @ptklabs/agent. PTK Agent controls the browser and scan lifecycle, applies the selected security policy, collects results and produces reports. PTK Auto performs the browser-side inspection and testing inside the automated session. PTK Auto is not the interactive version of OWASP PTK and does not provide the complete manual testing interface. Install the full OWASP PTK extension if you want to inspect traffic, launch scans, modify requests or test JWTs manually. During an authorised scan, PTK Auto may inspect application traffic, page resources and browser behaviour required by the selected checks. Use a dedicated browser profile and test environment whenever possible. Use PTK Auto only against applications where you have explicit authorisation. Active security testing can generate additional traffic, modify application data and trigger security monitoring.
Aug 5, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.