Mmm.. smell that code!

Fresh NuGet packages in every repository.

Approve a version once. We prove it on a few repositories first, then it spreads to the rest.

Repositories with updated nugets
Fresh code smells good.

The problem

New vulnerabilities in NuGet packages keep coming. When your code lives in many repositories, each one costs the same work again.

  • Every fix touches every repository

    Edit, restore, build, test, commit. Then do it again in the next repository.

  • It never ends

    A new CVE vulnerability starts the same round again.

  • Some repositories get skipped

    The ones that are not a priority wait. The technical debt builds up, and nobody gets the time to fix it.

What you get

  • Decide once

    Approve a version yourself, or set a rule per repository group that approves what you want without a person. Security fixes come first.

  • Proven before it spreads

    A version is tried on a few canary repositories first. It spreads only after build and tests pass.

Proven on a few repositories before it reaches the rest.
Proven on a few repositories before it reaches the rest.

Is this for you?

  • For

    Teams with many .NET services or client projects, each in its own repository. Any team that does microservices will recognize this pain.

  • Not for

    A single application, a team that keeps all code in one repository, or a team that does not use .NET.

Set it up once

You add the necessary steps in your pipeline, and that is it. From then on, everything happens in the web app, or automatically if you choose. Start on the free tier. No credit card needed.

Join the waitlist

Smell That Code is not open to everyone yet. Join the waitlist and we will tell you when you can try it. A free tier lets you try it on your own repositories at no cost: connect a few of them and see what it would upgrade.