cycode 3.6.1.dev1__tar.gz → 3.6.1.dev2__tar.gz

{cycode-3.6.1.dev1 → cycode-3.6.1.dev2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cycode
-Version: 3.6.1.dev1
+Version: 3.6.1.dev2
 Summary: Boost security in your dev lifecycle via SAST, SCA, Secrets & IaC scanning.
 License-Expression: MIT
 License-File: LICENCE
@@ -960,6 +960,24 @@ git push --no-verify
 > [!TIP]
 > The pre-push hook is triggered on `git push` command and scans only the commits that are about to be pushed, making it more efficient than scanning the entire repository.
 
+## Exclude Paths From Scans
+You can use a `.cycodeignore` file to tell the Cycode CLI which files and directories to exclude from scans.
+It works just like a `.gitignore` file. This helps you focus scans on your relevant code and prevent certain paths from triggering violations locally.
+
+### How It Works
+1. Create a file named `.cycodeignore` in your workfolder.
+2. List the files and directories you want to exclude, using the same patterns as `.gitignore`.
+3. Place this file in the directory where you plan to run the cycode scan command.
+
+> [!WARNING]
+> - **Invalid files**: If the `.cycodeignore` file contains a syntax error, the CLI scan will fail and return an error.
+> - **Ignoring paths vs. violations**: This file is for excluding paths. It's different from the CLI's capability to ignore specific violations (for example, by using the --ignore-violation flag).
+
+### Supported Scanners
+- SAST
+- Iac (comming soon)
+- SCA (comming soon)
+
 ## Scan Results
 
 Each scan will complete with a message stating if any issues were found or not.

{cycode-3.6.1.dev1 → cycode-3.6.1.dev2}/README.md

@@ -917,6 +917,24 @@ git push --no-verify
 > [!TIP]
 > The pre-push hook is triggered on `git push` command and scans only the commits that are about to be pushed, making it more efficient than scanning the entire repository.
 
+## Exclude Paths From Scans
+You can use a `.cycodeignore` file to tell the Cycode CLI which files and directories to exclude from scans.
+It works just like a `.gitignore` file. This helps you focus scans on your relevant code and prevent certain paths from triggering violations locally.
+
+### How It Works
+1. Create a file named `.cycodeignore` in your workfolder.
+2. List the files and directories you want to exclude, using the same patterns as `.gitignore`.
+3. Place this file in the directory where you plan to run the cycode scan command.
+
+> [!WARNING]
+> - **Invalid files**: If the `.cycodeignore` file contains a syntax error, the CLI scan will fail and return an error.
+> - **Ignoring paths vs. violations**: This file is for excluding paths. It's different from the CLI's capability to ignore specific violations (for example, by using the --ignore-violation flag).
+
+### Supported Scanners
+- SAST
+- Iac (comming soon)
+- SCA (comming soon)
+
 ## Scan Results
 
 Each scan will complete with a message stating if any issues were found or not.

cycode-3.6.1.dev2/cycode/__init__.py

@@ -0,0 +1 @@
+__version__ = '3.6.1.dev2'  # DON'T TOUCH. Placeholder. Will be filled automatically on poetry build from Git Tag

{cycode-3.6.1.dev1 → cycode-3.6.1.dev2}/pyproject.toml

@@ -21,7 +21,7 @@ classifiers = [
     "Programming Language :: Python :: 3.14",
 ]
 dynamic = ["dependencies"]
-version = "3.6.1.dev1"
+version = "3.6.1.dev2"
 
 [project.scripts]
 cycode = "cycode.cli.app:app"

cycode-3.6.1.dev1/cycode/__init__.py

@@ -1 +0,0 @@
-__version__ = '3.6.1.dev1'  # DON'T TOUCH. Placeholder. Will be filled automatically on poetry build from Git Tag