swt 4.1.1

Sweet is a high-performance code health and architectural integrity analyzer. It is plug-and-play: it works immediately with zero configuration using intelligent defaults, while offering the flexibility to enforce stricter standards via .swtrc files.

By quantifying technical debt and identifying complex logic patterns, Sweet helps teams adhere to core engineering principles like SRP (Single Responsibility Principle) and DRY (Don't Repeat Yourself).

🍬 Why Sweet?

Most linters focus on syntax; Sweet focuses on maintainability. It acts as a surgical tool to prevent the "Big Ball of Mud" anti-pattern by monitoring the physical and logical weight of your components.

• Enforce SRP: Identify "God Functions" and bloated files that take on too many responsibilities.
• Encourage Decoupling: Track dependency density to prevent tangled, hard-to-test modules.
• Prevent Logic Bloat: Detect deep nesting and cognitive complexity before they become technical debt.
• Eliminate Redundancy: Project-wide inspection to find duplicated logic that should be abstract or shared.

🍬 Metrics

Sweet evaluates code health through four primary lenses of maintainability:

🍬 Features

• Blazing Fast: Process thousands of files in milliseconds (self-analysis in <10ms).
• Hierarchical Config: Cascading .swtrc files for directory-specific rule sets.
• Global Inspection: Project-wide duplicate detection with detailed occurrence mapping.
• Intelligent Defaults: Language-specific thresholds tuned for different ecosystems.
• Quality Guard: Native support for pre-push hooks to block "Bitter" code.
• Auto-Update: Built-in update system to keep your tool always sharp.

🍭 Supported Languages

🍬 Installation

Visit the Releases Page for native installers:

• Windows: .msi
• Linux: .deb, .rpm

Crates.io

cargo install swt

📖 Usage

Run a standard health check:

swt [path]

Deep Inspection

Find exact code fragments repeated across different files:

swt inspect [path]

Strip Comments

AI Agents often generate verbose comments. Reclaim your logic:

swt uncomment <file> [--aggressive]

Update

Check or install new versions:

swt check-updates
swt update

🔌 Power User Integration

Sweet follows the Unix philosophy. It plays perfectly with the standard Rust toolbelt (fd, rg) to handle massive refactors in seconds.

With fd (Fast Find): Strip comments from every Rust file in your project at once.

fd -e rs -x swt uncomment

With ripgrep (rg): Target only the files that contain a specific "Bitter" pattern or AI-generated signature.

rg "TODO:" -l | xargs swt uncomment

🏗️ CI/CD Integration

If you are using GitHub Actions, you don't need to manually install Sweet. We've built Refinery-RS, a surgical quality gate and build pipeline for Rust projects.

Refinery-RS CI

Integrate Sweet with clippy and rustfmt in one single step:

jobs:
  quality-gate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: sircesarium/refinery-rs/ci@main
        with:
          enable-sweet: true   # Runs 'swt' maintainability analysis
          enable-clippy: true  # Runs standard Rust lints
          enable-fmt: true     # Ensures consistent formatting

⚙️ Configuration

Sweet resolves .swtrc files hierarchically.

{
  "$schema": "https://raw.githubusercontent.com/SirCesarium/sweet/main/schema.json",
  "thresholds": {
    "global": { 
      "max_lines": 400, 
      "max_lines_per_function": 200
    },
    "severities": {
      "max-repetition": "warning"
    }
  }
}

🍭 Severity Levels

By default, all rule violations are treated as errors (causing a non-zero exit code). You can downgrade specific rules to warnings (informational only, exit code 0) in your .swtrc.

🍭 In-file Control

Disable specific checks via comments in the first 20 lines: // @swt-disable max-lines max-repetition

Rules: max-lines, max-depth, max-imports, max-repetition, max-lines-per-function.

To ignore a file entirely, use @sweetignore.

🤝 Contributing

See CONTRIBUTING.md for technical specifications and how to add new languages.

📜 License

Licensed under the MIT License.