Safeguard
Model Family · Lino

Lino. The commit-time gut check.

Lino is the ~1B distilled-from-Griffin inline model. It runs locally inside the IDE, CLI, and pre-commit hook with sub-100 ms latency and zero source-code egress — so a developer never has to choose between speed and a real second pair of eyes.

~1B
Distilled parameters
INT8
Quantised weights
<80ms
p95 inline latency
100%
On-device inference
What Lino does

Fast, local, never the bottleneck.

Three jobs in the editor. Sub-100 ms so the developer never disables it.

Inline sink detection

Catches obvious dangerous sinks — unsafe deserialization, SSRF-able URL builders, unsanitised SQL, command-exec, path traversal — before code ever reaches CI.

Sanitiser awareness

Flags weak or missing sanitiser usage in known dangerous flows. Knows the difference between a real allow-list and a check that looks like one.

Local-only inference

Model weights ship with the IDE extension and CLI. No source code, prompts, or embeddings leave the developer machine. Zero network egress required.

Distillation lineage

Griffin's reasoning, pruned to inline shape.

How Lino inherits Griffin

  • Distilled from Griffin L with security-task distillation: both label distillation and intermediate-trace distillation.
  • INT8 quantised weights with calibration on security-task tensors.
  • Runs on CPU and modern Apple Silicon / x86 GPU laptops with no separate runtime.
  • Ships in the IDE extension, CLI, and pre-commit hook from one signed artefact.
  • Same security-augmented tokeniser as Griffin, pruned to the inline-relevant vocab.
Privacy posture

On the laptop, or not at all.

What stays on the developer machine

  • Weights are signed and verified at install; tampered binaries refuse to load.
  • No telemetry by default. The IDE extension makes no outbound requests at rest.
  • Opt-in anonymised telemetry, off until explicitly enabled, scoped to model latency stats — never source text.
  • Air-gapped operation supported out of the box; no online activation, no licence phone-home.
  • Source code, prompts, and embeddings never leave the developer machine under any configuration.
  • Update channel is verifiable: signed manifests, reproducible builds, content-addressed weight hashes.
Where Lino fits

Before the queue ever exists.

01IDE / CLI / pre-commit
Developer edits

Lino runs as the developer types and on every staged change.

02Lino
Local inference

Sub-80 ms sink + sanitiser check, fully on device, no network call.

03Editor
Editor surface

Finding shows up inline with a one-line explanation and the offending span.

04Developer
Fix before push

Issue is gone before CI ever sees it. No queue, no triage tax.

Catch it inline, fix it in the editor, never spend a triage hour on it.

Put Lino in the editor.

Sub-80 ms on the developer machine, no egress, distilled from the same brain as the rest of the lineup.