digitalriver — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited digitalriver (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Digital River is an ecommerce platform that provides payment processing, fraud prevention, and global tax compliance services. It's used by software companies, manufacturers, and retailers who sell digital products or online services internationally. Developers might need to integrate with Digital River to handle payments or manage subscriptions in their applications.
Official docs: https://developer.digitalriver.com/
This skill uses the Membrane CLI to interact with DigitalRiver. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.
Install the Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/climembrane login --tenantA browser window opens for authentication.
Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with membrane login complete <code>.
membrane search digitalriver --elementType=connector --jsonTake the connector ID from output.items[0].element?.id, then:
membrane connect --connectorId=CONNECTOR_ID --jsonThe user completes authentication in the browser. The output contains the new connection id.
When you are not sure if connection already exists:
membrane connection list --jsonIf a DigitalRiver connection exists, note its connectionId
When you know what you want to do but not the exact action ID:
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --jsonThis will return action objects with id and inputSchema in it, so you will know how to run it.
| Name | Key | Description |
|---|---|---|
| List Orders | list-orders | Returns a list of orders with pagination and filtering options |
| List Subscriptions | list-subscriptions | Returns a list of subscriptions with pagination options |
| List Customers | list-customers | Returns a list of customers with pagination and filtering options |
| List SKUs | list-skus | Returns a list of SKUs (products) with pagination and filtering options |
| List Checkouts | list-checkouts | Returns a list of checkouts with pagination options |
| Get Order | get-order | Retrieves an order by its unique ID |
| Get Subscription | get-subscription | Retrieves a subscription by its unique ID |
| Get Customer | get-customer | Retrieves a customer by their unique ID |
| Get SKU | get-sku | Retrieves a SKU (product) by its unique ID |
| Get Checkout | get-checkout | Retrieves a checkout by its unique ID |
| Create Order | create-order | Creates a new order from a checkout or directly |
| Create Subscription | create-subscription | Creates a new subscription |
| Create Customer | create-customer | Creates a new customer in DigitalRiver |
| Create SKU | create-sku | Creates a new SKU (product) in DigitalRiver |
| Create Checkout | create-checkout | Creates a new checkout session for a purchase |
| Update Order | update-order | Updates an existing order by ID |
| Update Subscription | update-subscription | Updates an existing subscription by ID |
| Update Customer | update-customer | Updates an existing customer by ID |
| Update SKU | update-sku | Updates an existing SKU (product) by ID |
| Update Checkout | update-checkout | Updates an existing checkout by ID |
membrane action run --connectionId=CONNECTION_ID ACTION_ID --jsonTo pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"When the available actions don't cover your use case, you can send requests directly to the DigitalRiver API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpointCommon options:
| Flag | Description |
|---|---|
-X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
-H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" |
-d, --data | Request body (string) |
--json | Shorthand to send a JSON body and set Content-Type: application/json |
--rawData | Send the body as-is without any processing |
--query | Query-string parameter (repeatable), e.g. --query "limit=10" |
--pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.