Book a demo Start for free

Model Change Monitoring

Know when the models your software depends on change.

PinDiff monitors supported open-model repositories for changes to weights, licences, remote code, access and documentation — so your team doesn’t have to check them manually.

Monitor a model View real changes

Your application code can stay the same while your external model dependency changes.

If your code loads a model by name and follows main, the next download can return different weights, configuration or licence terms — with no change in your repository and nothing in your own commit history.

  1. Yesterday Application example-org/chat-7b @ main revision 3f9a2c1
  2. Upstream update
  3. Today Application example-org/chat-7b @ main revision 8b7d4e0
Example

What PinDiff monitors

Six upstream signals that can change how a model behaves, how it may be used, or whether it can be downloaded.

  • Model weights

    Weight files added, removed or replaced.

  • Licence

    The declared licence or licence file changed.

  • Remote code / configuration

    Custom code that can run when the model loads, and configuration values.

  • Access / gating

    Who can download the model changed.

  • Model card

    Documentation such as intended use, limitations or training data was edited.

  • Repository status

    The repository was deleted, moved or became unavailable.

How each signal is observed

A real recorded change

The latest material change PinDiff recorded.

From repository to change

  1. Repository
  2. Observation
  3. Snapshot
  4. Comparison
  5. Change detected
  6. Dependency context

PinDiff observes each repository once for everyone; your project dependencies add the context. See the methodology.

Next step

A model changed. Does it affect what you’re using?

Monitoring tells you what happened upstream. Revision Tracking helps determine whether your recorded dependency follows that change.

Next: Revision Tracking Start monitoring for free