garak VS Commit Together by Github

• Open-source and free
  Garak is an open-source LLM vulnerability scanner, making it accessible without licensing costs and allowing community contributions and transparency into how tests are conducted.
• Comprehensive vulnerability probes
  It includes a wide range of probes for testing prompt injection, jailbreaks, data leakage, toxicity generation, hallucination, and other known LLM failure modes, giving broad coverage for security and safety testing.
• Extensible framework
  Garak is designed to be modular, allowing users to write custom probes, detectors, and generators to test specific models or scenarios relevant to their use case.
• Supports multiple LLM backends
  It can interface with various model providers and local models, making it flexible for testing different types of LLM deployments including API-based and self-hosted models.
• Useful for red-teaming and compliance
  The tool helps organizations proactively identify weaknesses before deployment, which can support responsible AI practices and compliance with emerging AI safety regulations.

• Enhanced Collaboration
  Commit Together allows multiple authors to be credited in a single commit, which fosters a more collaborative environment and ensures everyone involved receives recognition for their contributions.
• Improved Code Review Process
  With multiple authors clearly listed, reviewers can better understand who contributed to which parts of the code, facilitating more directed questions and discussions.
• Accountability
  By attributing every change to the respective author, teams can easily track who made specific changes, which helps in accountability and understanding the history of a project.
• Efficiency in Pair Programming
  When pair programming, both developers can be credited for their combined effort, streamlining the process of sharing code ownership during collaborative sessions.

Possible disadvantages

• Complex Commit History
  Having multiple authors for a single commit may lead to a more complex commit history, making it harder to pinpoint individual contributions over time.
• Potential Workflow Conflicts
  Teams that are used to single-author commits may experience workflow conflicts or require adjustments in practices to accommodate multi-author contributions.
• Initial Setup Overhead
  Learners and new users might face a learning curve or require additional setup to understand and correctly implement the multi-author commit feature.
• Tooling Compatibility
  Some third-party tools and extensions might not fully support or display multi-author commits, leading to inconsistencies in those environments.

Tracking garak since Sep 2026.

• Ask HN: Do you rewrite pull requests?

  There is "Co-authored-by" which is supported on GitHub [1] and seems appropriate if the maintainer is basing the solution on someone's code. [1] https://github.blog/2018-01-29-commit-together-with-co-authors/. - Source: Hacker News / over 4 years ago