Extend API to cover all of the ZAP functionality
Open
Nobody has claimed this yet.
Component-API
enhancement
project
tracker
- Dominant language
- Java
- Stars
- 15.8k
- Forks
- 2.6k
- Avg merge
- 13h 16m
- Merged PRs (30d)
- 17
Description
Extend Web API to cover all of the ZAP functionality
Original issue reported on code.google.com by marcinmalawski on 2011-09-30 12:12:55
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
The issue only requests extending the Web API to cover all ZAP functionality and names no files or tests. Start by surveying the existing Web API entry points and comparing them with ZAP's available functionality. Done would require a defined inventory showing that the intended functionality is exposed through the API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100