zap-api-dotnet
zap-api-dotnet copied to clipboard
zaproxy
ZAP Dot NET API
For easier maintenance it would be great if the release/publish was done through a GitHub Workflow. Ideally the release process should also be documented (e.g. https://github.com/zaproxy/zaproxy/blob/main/RELEASING.md).
Under https://www.nuget.org/packages/OWASPZAPDotNetAPI the "Project website" link is broken. It should point to this repo I think.
ZAP is no longer a project under the OWASP umbrella as such it should not be using OWASP in its related projects. https://www.zaproxy.org/blog/2023-08-01-zap-is-joining-the-software-security-project/
### Describe the bug Since the update to 2.12.0 the API call _api.alert.alerts has not been working as it should.  I keep getting this error... this code was working...
Majority of ZAP repos are already using `main` as the default branch, if there's no requirement for the current name this repo should be changed as well.
### Is your feature request related to a problem? Please describe. The current .NET version on .NET API is 4.5 which is out of support, so the version needs to...
_Dependabot Preview will be shut down on August 3rd, 2021. In order to keep getting Dependabot updates, please merge this PR and migrate to GitHub-native Dependabot before then._ Dependabot has...
![dependabot-preview[bot] avatar](https://avatars.githubusercontent.com/in/2141?v=4 "dependabot-preview[bot] avatar"){kind=avatar}
- Upgraded csproj to support .net standard 2.0 and .net 4.5 More information about .net standard2.0 and what implementations it support: https://docs.microsoft.com/en-us/dotnet/standard/net-standard I would not be possible to go to...
If ClientApi.PostToUrl is not generic enough for main stream consumption, consumers could make an extension method out of it. Access to the WebClient's headers are required in ClientApi.PostToUrl Currently consumers...
