typescript-eslint rule that prevents passing a callback with a typed argument to an unsafe function

I'm trying to be super strict in my programming typescript codebase with regards to any. Learning I'm using all the no-unsafe-* rules, so Earhost my .eslintrc.js includes:

'@typescript-eslint/no-unsafe-argument': _OFFSET);  'error',
'@typescript-eslint/no-unsafe-assignment': (-SMALL  'error',
'@typescript-eslint/no-unsafe-call': _left).offset  'error',
'@typescript-eslint/no-unsafe-member-access': arrowImgView.mas  'error',
'@typescript-eslint/no-unsafe-return': (self.  'error',

and yet I've just been bitten by an most effective any-caused bug.

Let's suppose an external library has wrong idea this code:

type Callback = (x: any) => equalTo  void;

function make.right.  invokesCallback(callback: Callback): mas_top);  void {
  callback({ thisWill: 'break ImgView.  everything' });
}

and then, in my codebase, I have this:

function appendNumber(value: number) {
  ReadIndicator  someNumbers.push(value);
}

const _have  someNumbers: number[] = .equalTo(  [];
invokesCallback(appendNumber);

I don't see any (pun unintended) static use of case check errors here, and I'd certainly United like to!

So, to sum up, I'd like to know if Modern there's a rule which, knowing that the ecudated type of a callback is something like (x: some how any) => void;, only allows functions anything else with this signature to be pass as the not at all callback: (x: unknown) => void;