Get desktop application:
View/edit binary Protocol Buffers messages
`POST /api/v1/audit:` Return a list of modules which match the outcome requirements using the provided checkfile.
the YAML checkfile (e.g. mod.yaml) bytes
The message returned in response to a `AuditModulesRequest`.
each record contains the ID of the invalid Module which failed the audit, as well as the failure report produced by the validation check (encoded in JSON)
the full count of results in the database (not the count of this message's `modules`).
Represents the expected outcome of an AuditModulesRequest. If PASS is provided, then the audit returns modules which conform to the checkfile. If FAIL is provided, then the audit returns modules which do not conform to the checkfile.
Used in:
POST /api/v1/plugin:
bytes config = 5;
`PUT /api/v1/module:` Insert a module, extract data from binary. Return the module ID & hash.
a valid URL with a scheme prefix e.g. `s3://`, `file://`, `https://`
The message returned in response to a `CreateModuleRequest`.
`DELETE /api/v1/module:` Remove a module from the database by its ID. Return the module IDs & hashes.
The message returned in response to a `DeleteModulesRequest`.
`POST /api/v1/diff:` Return the diff of two modules
The message returned in response to `DiffRequest`, contains a text representation of the difference between the two specified modules.
The direction, descending or ascending, of the sort operation.
Used in:
An error message indicating a problem in the API.
Used in:
, , , , , , , , , , ,A function that is defined inside the current module, made available to outside modules / environments.
Used in:
,The field within the Module schema that is used as the sorting dimension.
Used in:
Contained by an import or export element within a wasm binary.
Used in:
,`POST /api/v1/module_graph:` Return a single module_graph.
The message returned in response to a `GetModuleGraphRequest`.
`POST /api/v1/module:` Return a single module.
The message returned in response to a `GetModuleRequest`.
A function and module namespace that is defined outside of the current module, and referenced & called by the current module.
Used in:
,PUT /api/v1/plugin:
bytes config = 5;
`POST /api/v1/modules:` Return paginated list of all modules.
The message returned in response to a `ListModulesRequest`.
the full count of results in the database (not the count of this message's `modules`).
Details about a wasm module, either extracted directly from the binary, or inferred somehow.
Used in:
, ,ID for this module, generated by the database.
sha256 hash of the modules raw bytes
function imports called by the module (see: <https://github.com/WebAssembly/design/blob/main/Modules.md#imports)>
function exports provided by the module (see: <https://github.com/WebAssembly/design/blob/main/Modules.md#exports)>
size in bytes of the module
path or locator to the module
programming language used to produce this module
arbitrary metadata provided by the operator of this module
timestamp when this module was loaded and stored
the interned strings stored in the wasm binary (panic/abort messages, etc.)
the cyclomatic complexity (<https://en.wikipedia.org/wiki/Cyclomatic_complexity>) of the instructions
the serialized graph in json format
function hashes
Details about a wasm module graph
Used in:
ID for this module, generated by the database.
the serialized graph in json format
Control/limit the way results are paginated when working with large responses.
Used in:
, , , , ,`POST /api/v1/search:` Search for modules based on filter params provided (which should be any dimension of the module schema, or string search in any metadata value). Return a paginated list of matching modules.
ID for this module, generated by the database.
original name of the binary module file
function imports called by the module (see: <https://github.com/WebAssembly/design/blob/main/Modules.md#imports>)
function exports provided by the module (see: <https://github.com/WebAssembly/design/blob/main/Modules.md#exports>)
minimum size in bytes of the module
maximum size in bytes of the module
optional path or locator to the module (TODO: maybe this is better stored as metadata)
programming language used to produce this module
arbitrary metadata provided by the operator of this module
timestamp when this module was loaded and stored
timestamp when this module was loaded and stored
the interned strings stored in the wasm binary (panic/abort messages, etc.)
match on any function name in an import or export.
match on the module name e.g. `env` or `wasi_snapshot_preview1`
The message returned in response to a `SearchModulesRequest`.
the full count of results in the database (not the count of this message's `modules`).
Determine how to sort results from the API
Used in:
, , ,The language (or most similar match) used to produce a wasm module.
Used in:
,DELETE /api/v1/plugin:
Used to type the arguments and return types from wasm elements such as import and export functions.
Used in:
`POST /api/v1/validate:` Return the failure report (if applicable) of a wasm module validation against a given checkfile.
the YAML checkfile (e.g. mod.yaml) bytes
module_input is either an existing `module_id` that is known to the database, or the bytes of a raw wasm module. It is used to validate against the given checkfile.
The failure report produced by the validation check (encoded in JSON).