migrate repository reference to NVIDIA org

Signed-off-by: Jeffrey Martin <jemartin@nvidia.com>

.github/ISSUE_TEMPLATE/bug_report.md

@@ -10,7 +10,7 @@ labels: "bug"
   Useful Links:
   - Wiki: https://docs.garak.ai/garak
 
-  Before opening a new issue, please search existing issues https://github.com/leondz/garak/issues
+  Before opening a new issue, please search existing issues https://github.com/NVIDIA/garak/issues
 -->
 
 ## Steps to reproduce

.github/ISSUE_TEMPLATE/documentation.md

@@ -11,7 +11,7 @@ labels: "documentation"
   - Wiki: https://docs.garak.ai/garak
   - Code reference: https://reference.garak.ai/
 
-  Before opening a new issue, please search existing issues https://github.com/leondz/garak/issues
+  Before opening a new issue, please search existing issues https://github.com/NVIDIA/garak/issues
 -->
 
 ## Summary

.github/ISSUE_TEMPLATE/feature_suggestion.md

@@ -10,7 +10,7 @@ labels: "enhancement"
   Useful Links:
   - Wiki: https://docs.garak.ai/garak
 
-  Before opening a new issue, please search existing issues https://github.com/leondz/garak/issues
+  Before opening a new issue, please search existing issues https://github.com/NVIDIA/garak/issues
 -->
 
 ## Summary

.github/ISSUE_TEMPLATE/plugin_suggestion.md

@@ -10,7 +10,7 @@ labels: "new-plugin"
   Useful Links:
   - Wiki: https://docs.garak.ai/garak
 
-  Before opening a new issue, please search existing issues https://github.com/leondz/garak/issues
+  Before opening a new issue, please search existing issues https://github.com/NVIDIA/garak/issues
 -->
 
 ## Summary

.github/ISSUE_TEMPLATE/question.md

@@ -11,7 +11,7 @@ labels: "question"
   - Wiki: https://docs.garak.ai/garak
   - Code reference: https://reference.garak.ai/
 
-  Before opening a new issue, please search existing issues https://github.com/leondz/garak/issues
+  Before opening a new issue, please search existing issues https://github.com/NVIDIA/garak/issues
 -->
 
 ## Summary

.github/PULL_REQUEST_TEMPLATE.md

@@ -20,7 +20,7 @@ List the steps needed to make sure this thing works
 - [ ] ...
 - [ ] **Verify** the thing does what it should
 - [ ] **Verify** the thing does not do what it should not
-- [ ] **Document** the thing and how it works ([Example](https://github.com/leondz/garak/blob/61ce5c4ae3caac08e0abd1d069d223d8a66104bd/garak/generators/rest.py#L24-L100))
+- [ ] **Document** the thing and how it works ([Example](https://github.com/NVIDIA/garak/blob/61ce5c4ae3caac08e0abd1d069d223d8a66104bd/garak/generators/rest.py#L24-L100))
 
 If you are opening a PR for a new plugin that targets a **specific** piece of hardware or requires a **complex or hard-to-find** testing environment, we recommend that you send us as much detail as possible.
 

.github/workflows/cla.yml

@@ -14,7 +14,7 @@ permissions:
 
 jobs:
   CLAAssistant:
-    if: github.repository_owner == 'leondz'
+    if: github.repository_owner == 'NVIDIA'
     runs-on: ubuntu-latest
     steps:
       - name: "CA & DCO Assistant"
@@ -27,7 +27,7 @@ jobs:
           PERSONAL_ACCESS_TOKEN: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
         with:
           path-to-signatures: 'signatures/cla.json'
-          path-to-document: 'https://github.com/leondz/garak/blob/main/CA_DCO.md' # e.g. a CLA or a DCO document
+          path-to-document: 'https://github.com/NVIDIA/garak/blob/main/CA_DCO.md' # e.g. a CLA or a DCO document
           # branch should not be protected
           branch: 'main'
           use-dco-flag: true

.github/workflows/labels.yml

@@ -26,7 +26,7 @@ on:
 
 jobs:
   handle-labels:
-    if: github.repository_owner == 'leondz'
+    if: github.repository_owner == 'NVIDIA'
     runs-on: ubuntu-latest
     steps:
       - uses: actions/github-script@v7
@@ -81,7 +81,7 @@ jobs:
                     git push origin <BRANCH_NAME>
 
                     # Now browse to the following URL and create your pull request!
-                    # - https://github.com/leondz/garak/pulls
+                    # - https://github.com/NVIDIA/garak/pulls
                     \`\`\`
 
                     This helps protect the process, ensure users are aware of commits on the branch being considered for merge, allows for a location for more commits to be offered without mingling with other contributor changes and allows contributors to make progress while a PR is still being reviewed.
@@ -119,7 +119,7 @@ jobs:
 
                     This includes:
 
-                    - All of the item points within this [template](https://github.com/leondz/garak/blob/master/.github/ISSUE_TEMPLATE/bug_report.md)
+                    - All of the item points within this [template](https://github.com/NVIDIA/garak/blob/master/.github/ISSUE_TEMPLATE/bug_report.md)
                     - Screenshots showing the issues you're having
                     - Exact replication steps
 
@@ -131,7 +131,7 @@ jobs:
                   close: true,
                   comment: `
                     When creating an issue, please ensure that the default issue template has been updated with the required details:
-                    https://github.com/leondz/garak/issues/new/choose
+                    https://github.com/NVIDIA/garak/issues/new/choose
 
                     Closing this issue. If you believe this issue has been closed in error, please provide any relevant output and logs which may be useful in diagnosing the issue.
                   `

.github/workflows/maintain_cache.yml

@@ -19,7 +19,7 @@ permissions:
 
 jobs:
   build:
-    if: github.repository_owner == 'leondz'
+    if: github.repository_owner == 'NVIDIA'
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v3

CONTRIBUTING.md

@@ -31,12 +31,12 @@ And if you like the project, but just don't have time to contribute, that's fine
 
 If you want to ask a question, good places to check first are the [garak quick start docs](https://docs.garak.ai) and, if its a coding question, the [garak reference](https://reference.garak.ai/).
 
-Before you ask a question, it is best to search for existing [Issues](https://github.com/leondz/garak/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first. You can also often find helpful people on the garak [Discord](https://discord.gg/uVch4puUCs).
+Before you ask a question, it is best to search for existing [Issues](https://github.com/NVIDIA/garak/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first. You can also often find helpful people on the garak [Discord](https://discord.gg/uVch4puUCs).
 
 
 If you then still feel the need to ask a question and need clarification, we recommend the following:
 
-- Open an [Issue](https://github.com/leondz/garak/issues/new).
+- Open an [Issue](https://github.com/NVIDIA/garak/issues/new).
 - Provide as much context as you can about what you're running into.
 - Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
 
@@ -58,7 +58,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
 
 - Make sure that you are using the latest version.
 - Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://reference.garak.ai/). If you are looking for support, you might want to check [this section](#i-have-a-question)).
-- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/leondz/garak/issues?q=label%3Abug).
+- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/NVIDIA/garak/issues?q=label%3Abug).
 - Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
 - Collect information about the bug:
   - Stack trace (Traceback)
@@ -75,7 +75,7 @@ You should never report security related issues, vulnerabilities or bugs includi
 
 We use GitHub issues to track bugs and errors. If you run into an issue with the project:
 
-- Open an [Issue](https://github.com/leondz/garak/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
+- Open an [Issue](https://github.com/NVIDIA/garak/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
 - Explain the behavior you would expect and the actual behavior.
 - Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
 - Provide the information you collected in the previous section.
@@ -98,14 +98,14 @@ This section guides you through submitting an enhancement suggestion for garak,
 
 - Make sure that you are using the latest version.
 - Read the [documentation](https://reference.garak.ai/) carefully and find out if the functionality is already covered, maybe by an individual configuration.
-- Perform a [search](https://github.com/leondz/garak/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
+- Perform a [search](https://github.com/NVIDIA/garak/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
 - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
 - Check out our [guide for contributors](https://reference.garak.ai/en/latest/contributing.html), which includes our coding workflow and a [guide to constructing a plugin](https://reference.garak.ai/en/latest/contributing.generator.html).
 
 <!-- omit in toc -->
 #### How Do I Submit a Good Enhancement Suggestion?
 
-Enhancement suggestions are tracked as [GitHub issues](https://github.com/leondz/garak//issues).
+Enhancement suggestions are tracked as [GitHub issues](https://github.com/NVIDIA/garak/issues).
 
 - Use a **clear and descriptive title** for the issue to identify the suggestion.
 - Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
@@ -143,4 +143,4 @@ Updating, improving and correcting the documentation
 
 <!-- omit in toc -->
 ## Attribution
-This guide is based on the **contributing-gen**. [Make your own](https://github.com/bttger/contributing-gen)!
+This guide is based on the **contributing-gen**. [Make your own](https://github.com/bttger/contributing-gen)!

FAQ.md

@@ -39,11 +39,11 @@ Not immediately, but if you have the Gradio skills, get in touch!
 
 ## Can you add support for vulnerability X?
 
-Perhaps - please [open an issue](https://github.com/leondz/garak/issues/new), including a description of the vulnerability, example prompts, and tag it "new plugin" and "probes".
+Perhaps - please [open an issue](https://github.com/NVIDIA/garak/issues/new), including a description of the vulnerability, example prompts, and tag it "new plugin" and "probes".
 
 ## Can you add support for model X?
 
-Would love to! Please [open an issue](https://github.com/leondz/garak/issues/new), tagging it "new plugin" and "generators".
+Would love to! Please [open an issue](https://github.com/NVIDIA/garak/issues/new), tagging it "new plugin" and "generators".
 
 ## How much disk space do I need to run garak?
 
@@ -96,7 +96,7 @@ Adding a custom generator is fairly straight forward. One can either add a new c
 ## How can I redirect `garak_runs/` and `garak.log` to another place instead of `~/.local/share/garak/`?
 
 * `garak_runs` is configured via top-level config param `reporting.report_dir` and also CLI argument `--report_prefix` (which currently can include directory separator characters, so an absolute path can be given)
-* An example of the location of the config param can be seen in https://github.com/leondz/garak/blob/main/garak/resources/garak.core.yaml
+* An example of the location of the config param can be seen in https://github.com/NVIDIA/garak/blob/main/garak/resources/garak.core.yaml
 * If `reporting.report_dir` is set to an absolute path, you can move it anywhere
 * If it's a relative path, it will be within the garak directory under the "data" directory following the cross-platform [XDG base directory specification](https://specifications.freedesktop.org/basedir-spec/latest/) for local storage
 * There's no CLI or config option for moving `garak.log`, which is also stored in the XDG data directory

README.md

@@ -9,9 +9,9 @@
 `garak`'s a free tool. We love developing it and are always interested in adding functionality to support applications. 
 
 [![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
-[![Tests/Linux](https://github.com/leondz/garak/actions/workflows/test_linux.yml/badge.svg)](https://github.com/leondz/garak/actions/workflows/test_linux.yml)
-[![Tests/Windows](https://github.com/leondz/garak/actions/workflows/test_windows.yml/badge.svg)](https://github.com/leondz/garak/actions/workflows/test_windows.yml)
-[![Tests/OSX](https://github.com/leondz/garak/actions/workflows/test_macos.yml/badge.svg)](https://github.com/leondz/garak/actions/workflows/test_macos.yml)
+[![Tests/Linux](https://github.com/NVIDIA/garak/actions/workflows/test_linux.yml/badge.svg)](https://github.com/NVIDIA/garak/actions/workflows/test_linux.yml)
+[![Tests/Windows](https://github.com/NVIDIA/garak/actions/workflows/test_windows.yml/badge.svg)](https://github.com/NVIDIA/garak/actions/workflows/test_windows.yml)
+[![Tests/OSX](https://github.com/NVIDIA/garak/actions/workflows/test_macos.yml/badge.svg)](https://github.com/NVIDIA/garak/actions/workflows/test_macos.yml)
 [![Documentation Status](https://readthedocs.org/projects/garak/badge/?version=latest)](http://garak.readthedocs.io/en/latest/?badge=latest)
 [![discord-img](https://img.shields.io/badge/chat-on%20discord-yellow.svg)](https://discord.gg/uVch4puUCs)
 [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
@@ -61,7 +61,7 @@ python -m pip install -U garak
 The standard pip version of `garak` is updated periodically. To get a fresher version, from GitHub, try:
 
 ```
-python -m pip install -U git+https://github.com/leondz/garak.git@main
+python -m pip install -U git+https://github.com/NVIDIA/garak.git@main
 ```
 
 ### Clone from source
@@ -71,7 +71,7 @@ python -m pip install -U git+https://github.com/leondz/garak.git@main
 ```
 conda create --name garak "python>=3.10,<=3.12"
 conda activate garak
-gh repo clone leondz/garak
+gh repo clone NVIDIA/garak
 cd garak
 python -m pip install -e .
 ```
@@ -298,7 +298,7 @@ Larger artefacts, like model files and bigger corpora, are kept out of the repos
 
 ## FAQ
 
-We have an FAQ [here](https://github.com/leondz/garak/blob/main/FAQ.md). Reach out if you have any more questions! [leon@garak.ai](mailto:leon@garak.ai)
+We have an FAQ [here](https://github.com/NVIDIA/garak/blob/main/FAQ.md). Reach out if you have any more questions! [leon@garak.ai](mailto:leon@garak.ai)
 
 Code reference documentation is at [garak.readthedocs.io](https://garak.readthedocs.io/en/latest/).
 

docs/source/cliref.rst

@@ -3,7 +3,7 @@ CLI reference for garak
 
 ::
 
-  garak LLM vulnerability scanner v0.10.0 ( https://github.com/leondz/garak ) at 2024-10-31T09:41:09.763226
+  garak LLM vulnerability scanner v0.10.0 ( https://github.com/NVIDIA/garak ) at 2024-10-31T09:41:09.763226
   usage: python -m garak [-h] [--verbose] [--report_prefix REPORT_PREFIX]
                          [--narrow_output]
                          [--parallel_requests PARALLEL_REQUESTS]
@@ -93,4 +93,4 @@ CLI reference for garak
                           with JSON containing a prompt and target
     --interactive.py      Launch garak in interactive.py mode
   
-  See https://github.com/leondz/garak
+  See https://github.com/NVIDIA/garak

docs/source/configurable.rst

@@ -195,7 +195,7 @@ You can see the parameters for any given plugin using garak ``--plugin_info``.
 .. code-block:: text
 
     $ python -m garak --plugin_info probes.grandma.Win10
-    garak LLM vulnerability scanner v0.10.0 ( https://github.com/leondz/garak ) at 2024-09-11T11:54:07.215242
+    garak LLM vulnerability scanner v0.10.0 ( https://github.com/NVIDIA/garak ) at 2024-09-11T11:54:07.215242
     Configured info on probes.grandma.Win10:
                             description: Will the model yield a Windows 10 product key if we beg it to?
                          DEFAULT_PARAMS: {'generations': 1}

docs/source/contributing.generator.rst

@@ -230,7 +230,7 @@ Testing
 
 Now that the pieces for our generator are in place - a subclass of ``garak.generators.base.Generator``, with some customisation in the constructor, and an overridden ``_call_model()`` method, plus a ``DEFAULT_CLASS`` given at module level - we can start to test.
 
-A good first step is to fire up the Python interpreter and try to import the module. Garak supports a specific range of tested Python versions (listed in `pyproject.toml <https://github.com/leondz/garak/blob/main/pyproject.toml>`_, under the ``classifiers`` descriptor), so remember to use the right Python version for testing.
+A good first step is to fire up the Python interpreter and try to import the module. Garak supports a specific range of tested Python versions (listed in `pyproject.toml <https://github.com/NVIDIA/garak/blob/main/pyproject.toml>`_, under the ``classifiers`` descriptor), so remember to use the right Python version for testing.
 
 .. code-block:: bash
 
@@ -299,7 +299,7 @@ The next step is to try some integration tests - executing garak from the comman
 
 Add some of your own tests if there are edge-case behaviours, general validation, or other things in ``__init__()``, ``_call_model()``, and other new methods that can be checked. Plugin-specific tests should go into a new file, ``tests/generators/test_[modulename].py``.
 
-If you want to see the full, live code for the Replicate garak generator, it's here: `garak/generators/replicate.py <https://github.com/leondz/garak/blob/main/garak/generators/replicate.py>`_ .
+If you want to see the full, live code for the Replicate garak generator, it's here: `garak/generators/replicate.py <https://github.com/NVIDIA/garak/blob/main/garak/generators/replicate.py>`_ .
 
 Done!
 =====
@@ -318,4 +318,4 @@ This tutorial covered a tool that takes text as input and produces text as outpu
 
     modality: dict = {"in": {"text"}, "out": {"text"}}
 
-For an example of a multimodal model, check out LLaVa in `garak.generators.huggingface <https://github.com/leondz/garak/blob/main/garak/generators/huggingface.py>`_ . 
+For an example of a multimodal model, check out LLaVa in `garak.generators.huggingface <https://github.com/NVIDIA/garak/blob/main/garak/generators/huggingface.py>`_ .