The Dry Run tab of the Audit Event window contains a record of all packages that were found to have violated a policy during the dry run. A policy with a dry run action, serves as an indicator that a violation occurred. The dry run event can be used as a notification that a package that was requested for download was evaluated by a Curation policy and found to contain a policy violation. It is important to note, a dry run does not block nor approve a package, it merely serves as a warning that a violation was found.
If other policies are applied that are blocking policies, Curation will also evaluate the package against these policies. This data is displayed in the Blocked/Approved tab.
Configuring curation policies for a dry run (see Step 5: Select Actions and Notifications) enables the Platform Admin to evaluate the impact of policies on developers before using them to block problematic packages.
Note
The retention period for the Dry Run audit events is 30 days.
Each event listed in the table includes the package type, name, and version as well as the policies that caused curation to create the dry run event.
Each event also includes the project to which the package belongs (if any), the remote repository to which the package was downloaded (or blocked), and the name of the requester.
Tip
To filter the table, click the filter icon on the right and select filter criteria.