jnkn

The Pre-Flight Impact Analysis Engine for Engineering Teams.

jnkn (pronounced "jun-kan") prevents production outages by stitching together the hidden dependencies between your Infrastructure (Terraform), Data Pipelines (dbt), and Application Code (Python/JS).

📚 Read the Full Documentation

The Blind Spot

Most tools operate in silos. Terraform sees resources, dbt sees tables, code sees imports. jnkn sees the glue.

It detects the invisible, cross-domain breaking changes that slip through every other tool:

graph LR
    subgraph "The Blind Spot"
        TF[Terraform Change] --"Breaks"--> CODE[App Configuration]
        CODE --"Breaks"--> DATA[Data Pipeline]
    end
    
    style TF fill:#ff6b6b,color:#fff
    style DATA fill:#ff6b6b,color:#fff

🚀 Quick Start

Get running in less than 2 minutes.

1. Installation

pip install jnkn

2. Initialize

Navigate to your project root. jnkn will automatically detect your stack (Python, Terraform, Kubernetes, etc.) and configure itself.

jnkn init

3. Check Impact

Run a check to see if your current changes break any downstream dependencies.

# Checks your current changes against the main branch
jnkn check

That's it. If you renamed a Terraform output that your app relies on, jnkn check will fail the build and tell you exactly what broke.

🤖 CI/CD Integration

Block breaking changes in Pull Requests before they merge.

# .github/workflows/jnkn.yml
steps:
  - uses: actions/checkout@v4
    with:
      fetch-depth: 0  # Required for diff analysis
      
  - name: Run Jnkn Gate
    run: |
      pip install jnkn
      # Fails if critical dependencies are broken
      jnkn check --git-diff origin/main HEAD --fail-if-critical

Supported Stacks

Contributing

We welcome contributions! Please see our Contributing Guide for details on how to set up your development environment.

License

MIT