Viewing Curation Policy Status for AI Catalog Models
Learn how JFrog AI Catalog shows Curation policy status on model pages.
The JFrog AI Catalog integrates JFrog Curation decisions directly into the model interface. AI developers can quickly see whether a model is blocked by organizational policies, read the reasons for a block, and open policy details. When a model is blocked, critical actions are disabled to support compliance and security. This includes Use model and Deployment when your model type supports them.
Where Curation Appears on the Model Page
Curation state is shown in the following places.
| Location | What you see |
|---|---|
| Status badge | In the model header, next to the model name and version selector. |
| Action buttons | Use model and Deployment are disabled when the model is blocked. |
| Policies tab | A tab in the navigation strip that lists blocking policies and opens detailed policy drawers. |
Status Badge
The status badge summarizes compliance for the model in repositories managed by JFrog ML that you can access.
| Badge | Color | Meaning |
|---|---|---|
| Blocked | Red | At least one organizational policy blocks the latest version of this model. |
| Allowed | Green | No organizational Curation policies currently block this model. |
Note
When a model is Blocked, Use model and Deployment workflows are disabled for that model.
Policies Tab
The Policies tab shows why a model is restricted.
When the model is blocked, the tab label can include a red badge with the number of active blocking policies. An example label is Policies (2).
Active Policies Table
The table lists policies that apply to the selected model.
| Column | Description |
|---|---|
| Policy name | Identifier for the policy. Selecting it opens the detail drawer. |
| Condition | The criteria that matched, such as a malicious package or an unapproved license. |
| Action | The enforcement action, shown as a Block chip. |
Curation Policy Details
Selecting a Policy name in the table opens the Curation Policy Details pane with the full configuration context for that policy.
| Field | Description |
|---|---|
| Scope | Repositories or projects governed by this policy. |
| Condition Type | Risk category, such as Vulnerability, License, or Malicious Package. |
| Supported | Icons for package types compatible with this condition. |
| Waiver option | How to request or submit a policy waiver, when applicable. |
| Decision group | Stakeholders or owners responsible for policy decisions. |
| History | Timestamps for policy creation and last update. |
Frequently Asked Questions
This section provides answers to frequently asked questions about Curation policy status on AI Catalog model pages.
FAQs
Q: What does a Blocked badge mean on an AI Catalog model?
A: A red Blocked badge in the model header means at least one organizational policy blocks the latest version of this model in repositories managed by JFrog ML that you can access. When a model is Blocked, Use model and Deployment workflows are disabled for that model.
Q: What does an Allowed badge mean?
A: A green Allowed badge means no organizational Curation policies currently block this model. The status badge summarizes compliance for the model in repositories managed by JFrog ML that you can access.
Q: Where can I see which policies block a model?
A: The Policies tab in the model page navigation strip lists blocking policies and opens detailed policy drawers. When the model is blocked, the active policies table shows each policy name, the condition that matched, and a Block enforcement action; the tab label can include a red badge with the count of active blocking policies (for example, Policies (2)).
Q: What appears in the Curation Policy Details pane?
A: Selecting a Policy name in the active policies table opens the Curation Policy Details pane with the full configuration context for that policy. The pane shows scope, condition type, supported package types, waiver option, decision group, and history (including timestamps for policy creation and last update).
Q: Why are Use model and Deployment disabled?
A: When a model is Blocked, critical actions are disabled to support compliance and security, including Use model and Deployment when your model type supports them. These actions remain unavailable until organizational Curation policy status no longer blocks the model.