Visible resource record
Resource pages keep version context, source references, package metadata, parser/import readback, compatibility notes, checksums, target context, and community feedback close to the adoption decision.
Transparency
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.
Resource pages keep version context, source references, package metadata, parser/import readback, compatibility notes, checksums, target context, and community feedback close to the adoption decision.
Scan readback, unsafe artifact warnings, prompt-risk findings, and package-analysis summaries are recorded as signals users can inspect before reuse.
Uploaded packages, workflow files, and external references are treated as untrusted. Intake checks describe what was analyzed without running third-party code as a platform workload.
Suspicious submissions can be held for review. Quarantine, moderation, publisher context, workflow sanitizer readback, and target guidance labels belong in transparency detail rather than homepage marketing copy.
A transparent record helps users make a narrower decision, but it is not a substitute for local review, environment controls, or user judgment.