Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
purpleteam-app-scanner — Application scanning component of purpleteam | Kitploit
Tools/GitLabGitLab/purpleteam-labs/purpleteam-app-scanner
Vulnerability ScannersWeb Vulnerability ScannersAPI Security TestingWeb SecurityPenetration TestingCloud SecurityDevSecOpsArchived
GitLab
purpleteam-labs/purpleteam-app-scanner

purpleteam-app-scanner

Application scanning component of purpleteam

View Repository
175 years agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

purpleteam logo

purpleteam application scanner


Application scanning component of purpleteam - Currently in alpha

GNU AGPL pipeline status test coverage known vulnerabilities




Clone this repository.

cd to the repository root directory and run:

root@kitploit:~
npm install

Configuration

Copy the config/config.example.json to config/config.local.json.
Use the config/config.js for documentation and further examples.

Take the Zap API Key that you set-up in the purpleteam-s2-containers project and replace the <zap-api-key-here> value in the config.local.json file.

The following two values should be the same. They should also match the value of the orchestrator outcomes.dir:

slave.report.dir Configure this value. This needs to be a directory of your choosing that both the orchestrator and app-scanner containers use. The directory you choose and configure needs group rwx permissions applied to it becuase the orchestrator and tester containers share the same group, they also read, write and delete outcome files within this directory.

results.dir Configure this value. This needs to be a directory of your choosing that both the orchestrator and app-scanner containers use. The directory you choose and configure needs group rwx permissions applied to it becuase the orchestrator and tester containers share the same group, they also read, write and delete outcome files within this directory.

Download Tool