Installations
npm install @trivikr-test/client-rbin-typesDeveloper Guide
Typescript
Yes
Module System
N/A
Min. Node Version
>=12.0.0
Node Version
16.14.2
NPM Version
8.5.0
Score
56.7
Supply Chain
57.4
Quality
71.9
Maintenance
100
Vulnerability
99.6
License
Releases
Contributors
Languages
TypeScript (99.64%)
Java (0.23%)
JavaScript (0.11%)
Gherkin (0.02%)
Love this project? Help keep it running — sponsor us today! 🚀
Developer
aws
Download Statistics
Total Downloads
333
Last Day
1
Last Week
3
Last Month
16
Last Year
58
GitHub Statistics
Apache-2.0 License
3,220 Stars
8,694 Commits
602 Forks
44 Watchers
12 Branches
169 Contributors
Updated on Feb 20, 2025
Maintainers
Package Meta Information
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
Total Downloads
Cumulative downloads
Total Downloads
333
Last Day
0%
1
Compared to previous day
Last Week
-50%
3
Compared to previous week
Last Month
300%
16
Compared to previous month
Last Year
-10.8%
58
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
33
@aws-sdk/client-rbin
Description
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.
Installing
To install the this package, simply type add or install @aws-sdk/client-rbin using your favorite package manager:
npm install @aws-sdk/client-rbinyarn add @aws-sdk/client-rbinpnpm add @aws-sdk/client-rbin
Getting Started
Import
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";
Usage
To send a request, you:
- Initiate client with configuration (e.g. credentials, region).
- Initiate command with input parameters.
- Call
sendoperation on client with command object as input. - If you are using a custom http handler, you may call
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);
Async/await
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.
Promises
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 });
Callbacks
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});
v2 compatible style
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});
Troubleshooting
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}
Getting Help
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.
- Visit Developer Guide or API Reference.
- Check out the blog posts tagged with
aws-sdk-json AWS Developer Blog. - Ask a question on StackOverflow and tag it with
aws-sdk-js. - Join the AWS JavaScript community on gitter.
- If it turns out that you may have found a bug, please open an issue.
To test your universal JavaScript code in Node.js, browser and react-native environments, visit our code samples repo.
Contributing
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.
License
This SDK is distributed under the Apache License, Version 2.0, see LICENSE for more information.
No vulnerabilities found.
Reason
30 commit(s) and 16 issue activity found in the last 90 days -- score normalized to 10
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: Apache License 2.0: LICENSE:0
Reason
security policy file detected
Details
- Info: security policy file detected: github.com/aws/.github/SECURITY.md:1
- Info: Found linked content: github.com/aws/.github/SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: github.com/aws/.github/SECURITY.md:1
- Info: Found text in security policy: github.com/aws/.github/SECURITY.md:1
Reason
no dangerous workflow patterns detected
Reason
binaries present in source code
Details
- Warn: binary detected: codegen/gradle/wrapper/gradle-wrapper.jar:1
- Warn: binary detected: tests/react-native/End2End/android/gradle/wrapper/gradle-wrapper.jar:1
Reason
Found 5/30 approved changesets -- score normalized to 1
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/stale_issues.yml:12
- Warn: no topLevel permission defined: .github/workflows/closed-issue-message.yml:1
- Warn: no topLevel permission defined: .github/workflows/codegen-ci.yml:1
- Warn: no topLevel permission defined: .github/workflows/commit-message-lint.yml:1
- Warn: no topLevel permission defined: .github/workflows/git-sync.yml:1
- Warn: no topLevel permission defined: .github/workflows/handle-stale-discussions.yml:1
- Warn: no topLevel permission defined: .github/workflows/issue-regression-labeler.yml:1
- Warn: no topLevel permission defined: .github/workflows/lock.yml:1
- Warn: no topLevel permission defined: .github/workflows/pre-commit-hooks.yml:1
- Warn: no topLevel permission defined: .github/workflows/stale_issues.yml:1
- Info: no jobLevel write permissions found
Reason
Project has not signed or included provenance with any releases.
Details
- Warn: release artifact v3.751.0 not signed: https://api.github.com/repos/aws/aws-sdk-js-v3/releases/201012869
- Warn: release artifact v3.750.0 not signed: https://api.github.com/repos/aws/aws-sdk-js-v3/releases/200780930
- Warn: release artifact v3.749.0 not signed: https://api.github.com/repos/aws/aws-sdk-js-v3/releases/200459197
- Warn: release artifact v3.748.0 not signed: https://api.github.com/repos/aws/aws-sdk-js-v3/releases/200228914
- Warn: release artifact v3.747.0 not signed: https://api.github.com/repos/aws/aws-sdk-js-v3/releases/199953551
- Warn: release artifact v3.751.0 does not have provenance: https://api.github.com/repos/aws/aws-sdk-js-v3/releases/201012869
- Warn: release artifact v3.750.0 does not have provenance: https://api.github.com/repos/aws/aws-sdk-js-v3/releases/200780930
- Warn: release artifact v3.749.0 does not have provenance: https://api.github.com/repos/aws/aws-sdk-js-v3/releases/200459197
- Warn: release artifact v3.748.0 does not have provenance: https://api.github.com/repos/aws/aws-sdk-js-v3/releases/200228914
- Warn: release artifact v3.747.0 does not have provenance: https://api.github.com/repos/aws/aws-sdk-js-v3/releases/199953551
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 5 are checked with a SAST tool
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/closed-issue-message.yml:11: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-v3/closed-issue-message.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codegen-ci.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-v3/codegen-ci.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codegen-ci.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-v3/codegen-ci.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/commit-message-lint.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-v3/commit-message-lint.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/commit-message-lint.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-v3/commit-message-lint.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/git-sync.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-v3/git-sync.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/handle-stale-discussions.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-v3/handle-stale-discussions.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/issue-regression-labeler.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-v3/issue-regression-labeler.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/lock.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-v3/lock.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pre-commit-hooks.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-v3/pre-commit-hooks.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pre-commit-hooks.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-v3/pre-commit-hooks.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/stale_issues.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-v3/stale_issues.yml/main?enable=pin
- Info: 0 out of 6 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 6 third-party GitHubAction dependencies pinned
Reason
21 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-67mh-4wv8-2f99
- Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
- Warn: Project is vulnerable to: GHSA-76p7-773f-r4q5
- Warn: Project is vulnerable to: GHSA-4vvj-4cpr-p986
- Warn: Project is vulnerable to: GHSA-h5c3-5r3r-rr8q
- Warn: Project is vulnerable to: GHSA-rmvr-2pp2-xj38
- Warn: Project is vulnerable to: GHSA-xx4v-prfh-6cgc
- Warn: Project is vulnerable to: GHSA-qwcr-r2fm-qrc7
- Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
- Warn: Project is vulnerable to: GHSA-rv95-896h-c2vc
- Warn: Project is vulnerable to: GHSA-qw6h-vgh9-j6wx
- Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
- Warn: Project is vulnerable to: GHSA-rhx6-c78j-4q9w
- Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-m6fv-jmcg-4jfg
- Warn: Project is vulnerable to: GHSA-cm22-4g7w-348p
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
- Warn: Project is vulnerable to: GHSA-vg6x-rcgg-rjx6
- Warn: Project is vulnerable to: GHSA-9crc-q9x8-hgqq
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Score
4
/10
Last Scanned on 2025-02-17
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