The reverse export name -> packages exporting it view of a signature source, each entry ordered by download
count (descending, ties by name) so whoever has to pick one exporter starts with the package a script most
likely means.
Building the view reads every package blob of a bundle, which is why of memoizes it on the source
object rather than on the caller: signature sources are opened once per process (see getSharedSigSource)
and are immutable, so every analyzer mounting the same bundle shares one index instead of re-scanning the
database per analysis. It is deliberately analyzer-independent -- self-package exclusion belongs to the caller
(see FlowrAnalyzerPackageVersionsSigDbPlugin.packagesExporting), not to the index.
The reverse
export name -> packages exporting itview of a signature source, each entry ordered by download count (descending, ties by name) so whoever has to pick one exporter starts with the package a script most likely means.Building the view reads every package blob of a bundle, which is why of memoizes it on the source object rather than on the caller: signature sources are opened once per process (see getSharedSigSource) and are immutable, so every analyzer mounting the same bundle shares one index instead of re-scanning the database per analysis. It is deliberately analyzer-independent -- self-package exclusion belongs to the caller (see FlowrAnalyzerPackageVersionsSigDbPlugin.packagesExporting), not to the index.