securegit 0.8.5

Zero-trust git replacement with 12 built-in security scanners, LLM redteam bridge, universal undo, durable backups, and a 50-tool MCP server
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

# Contributing to SecureGit

Thank you for your interest in contributing to SecureGit.

## Getting Started

### Prerequisites

- Rust 1.70+ (stable)
- Git

### Development Setup

```bash
git clone https://github.com/armyknifelabs-tools/securegit.git
cd securegit
cargo build
cargo test
```

## Making Changes

1. Fork the repository
2. Create a feature branch: `git checkout -b feature/my-feature`
3. Make your changes
4. Run checks:
   ```bash
   cargo fmt --check
   cargo clippy --tests
   cargo test
   ```
5. Commit with a clear message describing the change
6. Push and open a pull request

## Code Style

- Run `cargo fmt` before committing
- All `cargo clippy --tests` warnings must be resolved
- All existing tests must pass
- Add tests for new functionality

## Pull Requests

- Keep PRs focused on a single change
- Include a description of what changed and why
- Reference any related issues

## Reporting Issues

- Use GitHub Issues for bugs and feature requests
- For security vulnerabilities, email security@armyknifelabs.com (see SECURITY.md)

## License

By contributing, you agree that your contributions will be licensed under the same license as the project (MIT OR Apache-2.0).