conventional-gitSAFE
Conventional Commits and Conventional Branch enforcement, validation, and generation
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://github.com/gajaguar/conventional-git/actions/workflows/ci.yml) [](https://github.com/gajaguar/conventional-git/actions/workflows/python.yml) [](LICENSE) [](pyproject.toml) [](https://github.com/gajaguar/conventional-git)
Conventional Commits and Conventional Branch enforcement, validation, and generation
Contents
- About
- Key features
- Requirements
- Installation
- Usage
- Agents
- CLI reference
- Configuration
- Architecture
- Platform notes
- Documentation
- Contributing
- License
About
One rule runs on three surfaces:
- A deterministic Git hook enforces it for human contributors.
- Structured violations over MCP let agents self-correct.
- A CLI lets you validate and generate names and messages directly.
Key features
- Validate commits and branches with
code,field,message, and
fix_hint fields.
- Report
ERRORandWARNINGseverity. - Generate commit messages and branch names with
create. - Install Git hooks with
hook install. - Expose validation and convention details through MCP tools.
- Report installed extras, providers, and credential sources with
`capabil
03eb81eecc6dOBSERVED · 2026-10-11Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add conventional-git-tools -- npx -y conventional-git-tools
{
"mcpServers": {
"conventional-git-tools": {
"command": "npx",
"args": [
"-y",
"conventional-git-tools"
]
}
}
}Exposed tools (4)
2 read · 2 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
describe_convention | read | config = Config.load() |
suggest_commit_message | write | config = Config.load() |
validate_branch_name | read | policy = branch_vocab.resolve_policy(Config.load()) |
validate_commit_message | write | policy = commit_vocab.resolve_policy(Config.load()) |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (6)
.markdownlint-cli2.jsonc
.markdownlint.yaml
.pre-commit-config.yaml
.pre-commit-hooks.yaml
env["TYPESAFE_BASE_URL"] = "http://127.0.0.1:9"
cspell, markdownlint-cli2
Gates applied: no_behavioural_pass.
03eb81eecc6dfull audit observations/trust-audit/mcp-server/gajaguar__conventional-git.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-11 | 03eb81eecc6d | SAFE | B | 89 | first audit |
Questions
What is the conventional-git MCP server?
Conventional Commits and Conventional Branch enforcement, validation, and generation
What tools does conventional-git expose?
4 in total: 2 read-only, 2 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is conventional-git safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does conventional-git need?
No credential environment variables were found in its source, so it appears to need none.
How does conventional-git run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as conventional-git-tools.
How current is this page?
The grade is for one exact copy of the source (03eb81eecc6d), read on 2026-10-11. The repository is watched and re-audited when it changes.