Glossary

advisory

A published record of a vulnerability in a package. The SBOM job matches the dependency manifest against a feed of advisories.

agent

The program that runs on a monitored device and reports its state.

analysis

One examination of the sources of a workspace. See Analysis.

baseline

The accepted state of a monitored device. Every difference from it is drift.

device

A machine that Midair watches. A device runs an agent, and it runs no work. See Monitoring.

distribution

A build that Midair deploys: an analyser, a test environment, or a monitoring agent. See Distributions.

attack vector

One avenue into the system that somebody wants probed, and the loop that keeps probing it: an analysis, a plan from an AI provider, a generated test suite, a run, and a judgement that feeds the next plan. See Attack vectors.

drift

The set of differences between the last report of a device and its baseline.

finding

One item that an analysis reported. It names a file, a line, a severity and a rule.

hypothesis

A claim that one iteration of an attack vector builds its tests to attack. The verdicts of the run refer back to it by its identifier.

job

One kind of work that the analyser does: defects, dependencies, authors, SBOM or metrics. See Jobs.

node

A machine that runs the work of a workspace. Midair reaches it over SSH. See Nodes.

project

What the HTTP API, the MCP tools and the release notes call a workspace. See workspace.

result tree

The tree that Midair builds from the log of a test run. The packages and the sessions are the branches, and the tests are the leaves.

run

One execution of a template. A run has a state, a log and results. Midair never writes over a run. See Concepts.

SBOM

Software bill of materials. The dependency manifest of the workspace, with the licences and the known advisories.

scope

Two meanings. On a screen, the workspace that the picker at the top selects. On a token, one of the named permissions that the token carries. See API tokens and the HTTP API.

seat

The access level that a team holds on one workspace: viewer, developer or maintainer. See Users, teams and access.

TE

Test Environment. The framework that the test suites are built on.

suspicious place

One item that an analysis reported beside the findings. It states that the code decides something and that nobody has confirmed the decision. It is never a defect, and it never changes whether a run passes. See Suspicious places.

template

The reusable description of what to run. A template carries no results. See Concepts.

verdict

The outcome of one test. A result tree entry carries the obtained verdict and the expected verdict.

workspace

The record that groups the runs, the devices and the comments of one piece of software. It is the unit of access, of scope and of configuration. See Workspaces.