security.integrity_mismatch

A dependency's content differs from its lock


Type	`https://mthds.ai/errors/security.integrity_mismatch`
Family	`security`: Refusals made for safety. An implementation may also record each one as a security event.
Domain	`method`: the method's author acts, by changing the method
Retry	`no`: repeating the operation fails the same way
HTTP status	`422`
Raised as	a problem document, sent as the body of an HTTP response or kept in a run's record

What it means

A fetched dependency's content hashes to something other than the lock pins, so it changed since it was locked.

What to do

Find out why the dependency's content changed, such as a moved tag. Update the lock only once the new content is trusted.

Next steps

A problem carries the step aimed at whoever reads it: the first when its reader is the domain's actor, the method's author, and the second for any other reader.

Reader	Kind	Detail
The domain's actor	`change_method`	Check where the dependency '`{dependency}`' changed, then update its lock only if the change is trusted.
Any other reader	`contact_owner`	Ask the method's owner to check the dependency '`{dependency}`'.

Detail

The problem's detail is written from this template, filled with the occurrence's parameters:

The content of the dependency '{dependency}' differs from the hash its lock pins.

Parameters

Every parameter is present on every occurrence of the code.

Name	Type	Description
`dependency`	`identifier`	The dependency whose content differs.