Request an expedited review¶
When you need a held version sooner than its hold allows, ask your reviewers to look at it now. Your request puts an Expedited badge on the version in the console's Quarantine queue and alerts the reviewers.
A review request doesn't approve anything by itself. A reviewer still reads the findings and decides.
Send the request¶
Use your client token, the same one in your .npmrc. Name the exact version,
and say why you need it:
curl -sSf -X POST \
"https://provenix.example.com/api/v1/packages/lodash/versions/4.17.22/request-review" \
-H "Authorization: Bearer $PROVENIX_NPM_TOKEN" \
-H "Content-Type: application/json" \
-d '{"justification": "Fixes the checkout crash in shop-web; release is blocked."}'
For a scoped package, keep the scope and name as separate path segments:
/api/v1/packages/@acme/widgets/versions/2.1.0/request-review
The request goes to the console host (provenix.example.com), not the
registry host. A 451 for a known version includes the path to use, as
request_review_path.
What you get back¶
{
"package_name": "lodash",
"version": "4.17.22",
"justification": "Fixes the checkout crash in shop-web; release is blocked.",
"coalesced": false
}
Sending another request for the same version doesn't create a second one:
coalesced is true, and your justification is updated.
If it fails¶
| Status | Meaning |
|---|---|
404 |
Provenix doesn't know this version. Install it once first, which starts discovery, then try again. |
409 |
The version is already approved. Install it. |
429 |
You've sent more than 10 review requests this hour from this client. |
After the review¶
When a reviewer approves the version, run your install again. No change on your side is needed. If they reject it, the console shows their note: talk to them about an alternative version.