Ask after the evidence is visible.

Ask is a scoped recommendation layer, not the source of truth. Start with a scan or a registry row, then ask for synthesis over the evidence that is already inspectable.

What decision needs synthesis?

Ready for a shipping question.

Attach package evidence if needed.

No file scanned.

If you arrived here without a scan, attach a package file or open the full scan workspace first. The scan result stays separate from the recommendation.

Attach a package file inside Ask

Supports package manifests, lockfiles, CycloneDX JSON, SPDX JSON, Go/Cargo files, Python requirements, TOML manifests, and plain package lists.

No package evidence attached yet. Ask can still answer from public registry and context, but scan evidence makes the recommendation more concrete.
Waiting
Ask Publicus No answer yet

Short recommendation. Inspectable proof.

The answer will keep package status, dated context, and model output clearly separated.

Why this landed here
  • Ask a concrete question to start.
Recommended actions
  • Use a component name, advisory id, or deployment context.
Constraints
  • No constraints yet.
Follow-up questions
How Publicus answered
  1. Tool activity appears after the first answer.