Interactive Audit Tool

Audit Log Generator

Generate compliance-ready audit logs for agent sessions. Track file changes, dependency updates, and configuration modifications with risk scoring.

Install

Get the CLI Tool

Run the audit logger locally as an MCP server, or try the interactive demo below.

npx @clinetools/audit-logger
Requires Node.js 18+
  • Git-aware audit log generation with author tracking
  • Risk scoring (0-100) with PASS / REVIEW / FAIL compliance
  • Dependency change detection (added/removed/upgraded)
  • Config file monitoring (.env, CI, Docker)
  • Export as JSON, CSV, or Markdown reports
Tutorial

How to Use It

Three ways to generate audit logs — pick the one that fits your workflow.

1

Try Online

Use the interactive demo below to explore audit reports with sample data — no install needed.

↓ Jump to interactive demo
2

Use via CLI

Run as a local MCP server and connect any MCP-compatible client.

npx @clinetools/audit-logger
3

Add to Cline / Claude Code

Add the tool to your MCP settings for instant access from your AI assistant.

"audit-logger": { "command": "npx", "args": ["@clinetools/audit-logger"] }

MCP Client Configuration 

{
  "mcpServers": {
    "audit-logger": {
      "command": "npx",
      "args": ["@clinetools/audit-logger"]
    }
  }
}

Example: generate_audit_log — clean session (12 actions, low risk, PASS) 

// Call the tool:
generate_audit_log({ projectPath: "/home/user/my-api", since: "2026-02-08T10:00:00Z" })

// Output:
{
  "summary": {
    "totalActions": 12,
    "riskScore": 8,
    "compliance": "PASS",
    "contributors": ["Alice Chen"],
    "categoryCounts": {
      "file_create": 1, "file_modify": 5, "file_delete": 0,
      "dep_change": 0, "git_commit": 6, "config_change": 0
    }
  },
  "actions": [ ... 12 entries ... ],
  "dependencyChanges": [],
  "configChanges": []
}

Example: export_audit_report — markdown format output 

// Call the tool:
export_audit_report({ format: "markdown" })

// Output:
# Audit Report
**Project:** /home/user/my-api
**Period:** 2026-02-08 10:00 - 2026-02-08 14:30
**Risk Score:** 8 / 100 (PASS)
**Contributors:** Alice Chen

## Actions (12 total)
| Time | Type | Author | Description |
|------|------|--------|-------------|
| 10:05 | git_commit | Alice Chen | Initial project setup |
| 10:12 | file_create | Alice Chen | Created src/routes/users.ts |
| ... |

## Dependency Changes
_No dependency changes detected._

## Config Changes
_No config file changes detected._
Live Demo

Try It Online

Select a sample session to see the audit log generator in action. No code to paste — the tool scans git history and the filesystem.

Select a Demo Session

Choose a scenario to generate its audit report

Action Categories

How It Works

What the Logger Tracks

The audit logger inspects your project's git history and filesystem to build a comprehensive compliance trail.

Git Integration

Uses git log as the primary data source — extracting commits, file status changes, authors, and timestamps. Falls back to filesystem timestamps for non-git projects.

Change Classification

Every action is classified: file_create, file_modify, file_delete, dep_change, git_commit, config_change. This taxonomy makes it easy to spot anomalies.

Risk Assessment

Risk score (0-100) weights config deletions (+15), dependency changes (+5 each), security-sensitive files (+10), and high volume (+10). Compliance: PASS < 25, REVIEW 25-50, FAIL > 50.

Dependency Tracking

Diffs package.json across commits to detect added, removed, or upgraded packages. Unknown new dependencies in production are a red flag.

Config File Monitoring

Tracks changes to .env, Dockerfile, CI configs, and build configs. Config changes have outsized security impact and deserve extra scrutiny.

Compliance Reporting

Export as JSON for automation, CSV for spreadsheets, or Markdown for documentation. Every format includes the full audit trail for compliance evidence.

Need Continuous Audit Logging?

Set up automated audit trails for your development workflow.

Get Started