Gathering detailed insights and metrics for @trivikr-test/client-rbin-types
Gathering detailed insights and metrics for @trivikr-test/client-rbin-types
Gathering detailed insights and metrics for @trivikr-test/client-rbin-types
Gathering detailed insights and metrics for @trivikr-test/client-rbin-types
Modularized AWS SDK for JavaScript.
npm install @trivikr-test/client-rbin-types
Typescript
Module System
Min. Node Version
Node Version
NPM Version
TypeScript (99.65%)
Java (0.23%)
JavaScript (0.1%)
Gherkin (0.01%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
Apache-2.0 License
3,358 Stars
9,565 Commits
618 Forks
42 Watchers
17 Branches
168 Contributors
Updated on Jul 11, 2025
Latest Version
3.52.0
Package Id
@trivikr-test/client-rbin-types@3.52.0
Unpacked Size
114.64 kB
Size
17.76 kB
File Count
49
NPM Version
8.5.0
Node Version
16.14.2
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
33
AWS SDK for JavaScript Rbin Client for Node.js, Browser and React Native.
This is the Recycle Bin API Reference. This documentation provides descriptions and syntax for each of the actions and data types in Recycle Bin.
Recycle Bin is a resource recovery feature that enables you to restore accidentally deleted snapshots and EBS-backed AMIs. When using Recycle Bin, if your resources are deleted, they are retained in the Recycle Bin for a time period that you specify.
You can restore a resource from the Recycle Bin at any time before its retention period expires. After you restore a resource from the Recycle Bin, the resource is removed from the Recycle Bin, and you can then use it in the same way you use any other resource of that type in your account. If the retention period expires and the resource is not restored, the resource is permanently deleted from the Recycle Bin and is no longer available for recovery. For more information about Recycle Bin, see Recycle Bin in the Amazon Elastic Compute Cloud User Guide.
To install the this package, simply type add or install @aws-sdk/client-rbin using your favorite package manager:
npm install @aws-sdk/client-rbin
yarn add @aws-sdk/client-rbin
pnpm add @aws-sdk/client-rbin
The AWS SDK is modulized by clients and commands.
To send a request, you only need to import the RbinClient
and
the commands you need, for example CreateRuleCommand
:
1// ES5 example 2const { RbinClient, CreateRuleCommand } = require("@aws-sdk/client-rbin");
1// ES6+ example 2import { RbinClient, CreateRuleCommand } from "@aws-sdk/client-rbin";
To send a request, you:
send
operation on client with command object as input.destroy()
to close open connections.1// a client can be shared by different commands. 2const client = new RbinClient({ region: "REGION" }); 3 4const params = { 5 /** input parameters */ 6}; 7const command = new CreateRuleCommand(params);
We recommend using await operator to wait for the promise returned by send operation as follows:
1// async/await. 2try { 3 const data = await client.send(command); 4 // process data. 5} catch (error) { 6 // error handling. 7} finally { 8 // finally. 9}
Async-await is clean, concise, intuitive, easy to debug and has better error handling as compared to using Promise chains or callbacks.
You can also use Promise chaining to execute send operation.
1client.send(command).then( 2 (data) => { 3 // process data. 4 }, 5 (error) => { 6 // error handling. 7 } 8);
Promises can also be called using .catch()
and .finally()
as follows:
1client 2 .send(command) 3 .then((data) => { 4 // process data. 5 }) 6 .catch((error) => { 7 // error handling. 8 }) 9 .finally(() => { 10 // finally. 11 });
We do not recommend using callbacks because of callback hell, but they are supported by the send operation.
1// callbacks. 2client.send(command, (err, data) => { 3 // proccess err and data. 4});
The client can also send requests using v2 compatible style. However, it results in a bigger bundle size and may be dropped in next major version. More details in the blog post on modular packages in AWS SDK for JavaScript
1import * as AWS from "@aws-sdk/client-rbin"; 2const client = new AWS.Rbin({ region: "REGION" }); 3 4// async/await. 5try { 6 const data = await client.createRule(params); 7 // process data. 8} catch (error) { 9 // error handling. 10} 11 12// Promises. 13client 14 .createRule(params) 15 .then((data) => { 16 // process data. 17 }) 18 .catch((error) => { 19 // error handling. 20 }); 21 22// callbacks. 23client.createRule(params, (err, data) => { 24 // proccess err and data. 25});
When the service returns an exception, the error will include the exception information, as well as response metadata (e.g. request id).
1try { 2 const data = await client.send(command); 3 // process data. 4} catch (error) { 5 const { requestId, cfId, extendedRequestId } = error.$metadata; 6 console.log({ requestId, cfId, extendedRequestId }); 7 /** 8 * The keys within exceptions are also parsed. 9 * You can access them by specifying exception names: 10 * if (error.name === 'SomeServiceException') { 11 * const value = error.specialKeyInException; 12 * } 13 */ 14}
Please use these community resources for getting help. We use the GitHub issues for tracking bugs and feature requests, but have limited bandwidth to address them.
aws-sdk-js
on AWS Developer Blog.aws-sdk-js
.To test your universal JavaScript code in Node.js, browser and react-native environments, visit our code samples repo.
This client code is generated automatically. Any modifications will be overwritten the next time the @aws-sdk/client-rbin
package is updated.
To contribute to client you can check our generate clients scripts.
This SDK is distributed under the Apache License, Version 2.0, see LICENSE for more information.
No vulnerabilities found.
Reason
30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
security policy file detected
Details
Reason
binaries present in source code
Details
Reason
SAST tool is not run on all commits -- score normalized to 7
Details
Reason
Found 8/30 approved changesets -- score normalized to 2
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
Project has not signed or included provenance with any releases.
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
project is not fuzzed
Details
Reason
28 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More