Function signature from etherscan-verified library cannot be decoded

[ckoopmann]

Assumption

I'm assuming that the signature service somehow auto imports signatures from etherscan verified contracts. (this is based on the observation that the service can decode functions that are unique to my smart contract deployment as soon as it is verified on etherscan).

Issue

If this is correct, than the import seems to miss external functions of deployed libraries.
This leads to tools such as foundry thatrely on openchain to decode traces being unable to decode them. (see here )
I am aware that I can provide these signatures to the service manually, but if possible it would be great if the service would automatically import these signatures from etherscan. (especially if such an automatic import already exists and could be extended to cover these signatures).

Example:

This library is verified on etherscan.
However its signatures are not available on the signature database.
For example the signature 0x1aafa9d8 which corresponds to the function swapExactTokensForTokens cannot be decoded on openchain.