jfrog-curation-onboarding

To set up JFrog Curation policies on existing remote repositories, provide your JFrog Platform URL and credentials. The skill validates Curation status, collects a notification email, enables Curation on target repositories, and creates eight security, license, and operational risk policies.

JFrog Curation onboarding creates eight curation policies: one Block Malicious policy that actively blocks downloads, and seven dry-run policies that log security, license, and operational risk violations without blocking them for auditing purposes.

Yes, you can automate JFrog Curation onboarding for multiple projects using the Automated Manifest-Driven mode. This operating mode supports per-project scope and policy updates across environments, contrasting with the single-instance Standalone Interactive mode.

JFrog Curation does not block all malicious packages during onboarding. Only the Block Malicious policy blocks downloads, while the remaining seven security, license, and operational risk policies run in dry-run mode to log violations without blocking.

Yes, a notification email is required to enable curation protection on your repositories. The skill collects this email during the onboarding workflow before enabling curation on target repositories and creating the protection policies.

Standalone Interactive onboarding configures JFrog Curation on a single instance interactively, while Automated Manifest-Driven onboarding automates governance across multiple projects using a manifest, applying per-project scope and policy updates.