Client Side Passive Scan rule - wappalyzer checks
Open
Nobody has claimed this yet.
add-on
enhancement
- Dominant language
- Java
- Stars
- 15.8k
- Forks
- 2.6k
- Avg merge
- 13h 16m
- Merged PRs (30d)
- 17
Description
Add a rule which checks for the ‘Global JavaScript variables’ - these are not checked in https://www.zaproxy.org/docs/desktop/addons/technology-detection/ as you need a real browser :)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the technology-detection documentation linked in the issue and inspect the existing client-side passive scan rules and their entry points. Determine how browser-based checks are represented, then verify that the new rule detects the requested Global JavaScript variables without duplicating existing technology checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, javascript
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100