This guide covers advanced scanning techniques and configuration options for power users.

Custom Scan Rules

You can define custom scanning rules using a configuration file:

{
  "rules": {
    "license-detection": {
      "enabled": true,
      "strictness": "high"
    },
    "dependency-analysis": {
      "enabled": true,
      "depth": 5
    }
  }
}

Filtering Results

Filter scan results by license type:

mcp-semclone scan --filter-license "MIT,Apache-2.0"

Filter by severity:

mcp-semclone scan --min-severity medium

Integration with CI/CD

GitHub Actions

Add MCP-SEMCLONE to your GitHub Actions workflow:

name: OSS Compliance Check
on: [push, pull_request]

jobs:
  compliance:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Run MCP-SEMCLONE
        run: |
          npm install -g mcp-semclone
          mcp-semclone scan --fail-on-error

GitLab CI

For GitLab CI integration:

compliance-check:
  stage: test
  script:
    - npm install -g mcp-semclone
    - mcp-semclone scan --format gitlab
  artifacts:
    reports:
      compliance: compliance-report.json

Performance Optimization

For large projects, use these optimization flags:

mcp-semclone scan --parallel 4 --cache --exclude node_modules

Conclusion

These advanced techniques will help you customize MCP-SEMCLONE to fit your specific needs and workflows.