Rules and approvals
Deciding requests
Where requests come from and what approve, block and clear do.
Requests come from developers on the Requests page, and from installs that were blocked when Open a request when an install is blocked is on (Settings, Policy). Repeated blocks of the same package fold into one request and count up.
| Action | What happens |
|---|---|
| approve | Shows the dependency tree counts, asks for a note, then writes an allow rule for the name and the versions asked for. |
| approve, with dependencies | Only when Approving a request can approve its clean dependencies too is on. Also approves up to 500 dependencies that nothing is known against, each pinned to its resolved version. |
| block | Needs a reason. Writes a deny rule at priority 1000, for the versions asked for or the whole package. |
| clear | Removes the request and writes nothing. If the install is blocked again, a new request appears. |
| Approve selected / Clear selected | Decide many pending requests at once. |
Tip
Check the Vulnerabilities column before approving. It looks at the newest matching versions against the advisory feed.