scanning
Here are 387 public repositories matching this topic...
RustScan has an accessible mode, rustscan --accessible which should promise not to have any weird ASCII text in it.
Write CI that runs RustScan with --accessible a few times, with different flags / options and check the terminal output to see if it contains one of these:
[!][~][>]| {}
If any of these characters appear in any of the tests, fail the CI. E
-
Updated
Sep 30, 2021 - C
Hey, here we need add url decoding cuz that invalid link with symbols of get request like ?, &, = etc
p.s thx for awesome tool
-
Updated
Jun 10, 2021 - Python
-
Updated
Nov 1, 2021 - PowerShell
-
Updated
Sep 14, 2021 - C#
-
Updated
Jul 6, 2020 - Python
-
Updated
Oct 27, 2021 - Python
RITA does not store information on how long an import took or how much data was processed in an import.
This ticket is to implement, at a minimum, those metrics mentioned above into the RITA logging.
-
Updated
Oct 30, 2021 - C++
-
Updated
Oct 31, 2021 - TypeScript
-
Updated
Dec 9, 2020 - Python
-
Updated
Jan 23, 2018 - Shell
-
Updated
Aug 14, 2018 - Python
-
Updated
Nov 1, 2021 - XSLT
-
Updated
Aug 11, 2021 - Python
-
Updated
Oct 8, 2019 - Python
-
Updated
Oct 26, 2021 - Java
-
Updated
Jan 29, 2020 - Swift
-
Updated
Nov 1, 2021 - Python
-
Updated
Mar 24, 2021 - Python
-
Updated
Sep 3, 2020 - Go
-
Updated
Apr 25, 2018 - Python
Hi,
It would be interesting to have those new rules integrated in ChopChop, see : https://github.com/nnposter/nndefaccts/blob/master/http-default-accounts-fingerprints-nndefaccts.lua
-
Updated
Jan 25, 2016 - C#
Improve this page
Add a description, image, and links to the scanning topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the scanning topic, visit your repo's landing page and select "manage topics."

Describe the solution you'd like
I'd like to go back to using a CHANGELOG.md to track changes. This will be the first step in updating the ci/cd process to increase the frequency of patches/deploys.
Additional context
Go through https://github.com/zricethezav/gitleaks/releases and create a CHANGELOG.md file
cc @zricethezav