Clear resource pages
Resource pages keep version context, source references, package details, compatibility notes, checksums, setup context, and community feedback close to the adoption decision.
Transparency
What Agentique shows before adoption
Agentique keeps review evidence visible without turning it into a blanket safety promise. This page explains the checks and boundaries behind public resource records.Signals users can inspect
Homepage copy stays focused on discovery and adoption. Detailed governance language stays here, where creators and adopters can review what the platform records and what it does not promise.
Visible review notes
Scan signals, unsafe-file warnings, prompt-risk findings, and package summaries are recorded as signals users can inspect before reuse.
No automatic running
Uploaded packages, workflow files, and external references are treated as untrusted. Intake checks describe what was reviewed without running third-party code as a platform workload.
Review before publication
Suspicious submissions can be held for review. Moderation state, publisher context, cleaned workflow steps, and setup guidance labels belong in transparency detail rather than homepage marketing copy.
Boundaries stay explicit
A transparent record helps users make a narrower decision, but it is not a substitute for local review, environment controls, or user judgment.
- Visible checks are review signals, not platform approval.
- Automated scans are not safety certification or a malware-free guarantee.
- Agentique does not run third-party agents as hosted workloads in the current public product path.
- Target downloads are shown only when public download evidence exists; guidance-only targets are setup notes, not direct install flows.
- Private or organization-scoped records stay hidden unless public-safe metadata is explicitly allowed.
- Public status helps users compare resources; it does not expose internal scoring, operator playbooks, or private review notes.