@wumo You’re correct that kotlinx-metadata-jvm doesn’t provide any access to annotations stored in the class file. In fact, there’s no trace of those annotations in the metadata itself (@kotlin.Metadata annotation), so they will always need to be loaded by external means. For example, matching the ExecutableElement instance with the function metadata by the JVM signature (passed to JvmFunctionExtensionVisitor.visit). We might consider providing a bunch of small libraries on top of kotlinx-metadata-jvm to provide this matching for popular use cases (annotation processing, reflection, class file processing). Could you please report an issue?