Repository navigation
[Query] Signature
Generated from 'wiki-query.ts' on 2026-11-08, 15:21:58 UTC (v2.17.4), do not edit directly.
Signature Query [overview]
Inspects the signature database: packages, function signatures, source and documentation links.
This query is requested with the type signature.
Run in the REPL: :query @signature [<pkg>[@<version>]] [<pkg>::<fn> | <fn>] [--param <name>[,...]] [--required <n>] [<name>(<arg>, [<role>], *) [<prop>]] [--cg] [--cg-max <n>] [--help]
This query is the read-side interface to flowR's signature database—the very same database
that resolves library() and :: calls during the dataflow analysis. It lets you ask what flowR actually knows about a package
or a function, without needing R or a network connection.
What you get back depends on how specific you are:
| Given | Result |
|---|---|
| nothing | a summary of the loaded databases |
package |
the full package view: version, CRAN links, dependencies, exports |
package + function
|
the full function view: parameters, definition site, source and documentation links, S3 relations |
a glob in either (gg*, geom_*) |
the set of matching packages or functions |
The version property accepts an exact version, a glob (3.*), a semver range (>=3.0.0), or a release-date bound (<=2026, >=2021.05).
Without it, the release that flowR resolved for the analyzed script is used, so the signature you see is the one the analysis actually assumed.
Given a script such as:
library(dplyr)
lead(1:10, n = 1)we can inspect the signature of the function it calls:
[ { "type": "signature", "package": "dplyr", "function": "lead" } ]Show Results
Results (prettified and summarized):
Query: signature (5 ms)
╰ dplyr::lead v1.2.1
╰ lead(x, n = 1L, default = NULL, order_by = NULL, ...)
╰ exported can-throw
╰ source R/lead-lag.R:74 https://github.com/cran/dplyr/blob/1.2.1/R/lead-lag.R#L74
╰ docs rdrr.io man v1.2.1
╰ calls (6): -, <, abort, shift, check_number_whole, check_dots_empty0
Show Detailed Results as Json
The analysis ran (including parsing and normalization and the query) within the generation environment.
The JSON contains the ids of the nodes in question (see the Interface wiki page).
{"signature":{".meta":{},"databases":[{"scope":"current","version":2,"date":"2026-07-19"},{"scope":"base","version":2,"date":"2026-07-19"},{"scope":"history","version":2,"date":"2026-07-19"}],"packageCount":23765,"sourceCount":3,"function":{"name":"lead","package":"dplyr","version":"1.2.1","exported":true,"properties":["exported","can-throw"],"parameters":[{"name":"x","props":2},{"name":"n","props":0,"default":"1L"},{"name":"default","props":0,"default":"NULL"},{"name":"order_by","props":0,"default":"NULL"},{"name":"...","props":2}],"callees":["-","<","abort","shift","check_number_whole","check_dots_empty0"],"file":"R/lead-lag.R","line":74,"sourceUrl":"https://github.com/cran/dplyr/blob/1.2.1/R/lead-lag.R#L74","docUrl":"https://rdrr.io/cran/dplyr/man/lead-lag.html","manUrl":"https://github.com/cran/dplyr/blob/1.2.1/man/lead-lag.Rd"}},".meta":{}}The parameters and requiredParameters properties additionally filter by the shape of a function, which is useful to find
functions you only half-remember: { package: '*', parameters: ['data', 'mapping'] } finds every known function taking both of these.
Note
The results depend on which database shards are mounted; with none available the query reports that no database is loaded rather than failing.
See the Signature Database page for the storage format, the configuration under solver.sigdb, and how to obtain further shards.
To find out what a script uses, reach for the Dependencies Query; to find out which versions it is compatible with, see the Guess Dependency Versions Query.
Implementation Details
The Signature Query is executed by executeSignatureQuery.
Currently maintained by Florian Sihler and Oliver Gerstl at Ulm University
Email | GitHub | Penguins | Portfolio
- 🧑💻 Developer Onboarding
- 💻 Setup
- 👓 Overview
- 🪟 Interfacing with flowR
- 🌋 Core
- 🧹 Testing & Linting (Benchmark Page)
⁉️ FAQ- ℹ️ Extra Information