AWS Cryptographic helpers for Javascript and Node.js
Installations
npm install @aws-crypto/crc32
Releases
Unable to fetch releases
Developer
aws
Developer Guide
Module System
CommonJS
Min. Node Version
>=16.0.0
Typescript Support
Yes
Node Version
16.20.1
NPM Version
lerna/5.6.2/node@v16.20.1+x64 (linux)
Statistics
64 Stars
263 Commits
34 Forks
18 Watching
17 Branches
36 Contributors
Updated on 21 Nov 2024
Languages
TypeScript (92.68%)
JavaScript (7.32%)
Total Downloads
Cumulative downloads
Total Downloads
816,701,556
Last day
-13.3%
1,895,474
Compared to previous day
Last week
1.4%
11,289,521
Compared to previous week
Last month
5.8%
47,536,375
Compared to previous month
Last year
86.8%
473,351,226
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
3
AWS SDK JS Crypto Helpers
AWS Cryptographic Helpers for Javascript and Node.js
Scope
This repository collects cryptographic helper packages. We have designed it to gather packages that implement simple primitives for the browser or Node.js. More information about AWS Crypto Tools can be found here
Project Status
This project is still in its early stages. Please send us your feedback. We might make breaking changes in future releases while the SDK is still in developer preview.
Getting started
Let’s walk through setting up a project that requires a cryptographically secure random value. The following steps use npm as an example. They assume you have node.js and npm already installed.
- Create a new node.js project.
- In the project, run:
npm install --save @aws-crypto/random-source-node@preview
- Create a new file called index.js, require the function, and then use it to get a random value.
1const { randomValues } = require("@aws-crypto/random-source-node"); 2async function example() { 3 try { 4 const rand = await randomValues(32); 5 console.log(rand.length); 6 } catch (err) { 7 console.error(err); 8 } 9} 10example();
Crypto Helper Package Index
Each package has readme details.
- crc32
- random-source-browser
- random-source-node
- random-source-universal
- sha256-browser
- sha256-js
- sha256-universal
- supports-web-crypto
Testing
To run the tests in every package.
npm install
npm test
Feedback
We welcome your feedback! If you have comments, questions, or suggestions, open a GitHub issue. We are actively monitoring issues and will respond to feedback as we prepare for our GA launch.
Contributing
We welcome your contributions! To fix a problem, or add to an existing package: create a pull request. You must submit all pull requests under the Apache 2.0 license. They will be reviewed by a team member prior to merging. We would appreciate, but do not require, unit tests for all significant contributions. See Contributing for more information.
License
This library is licensed under the Apache 2.0 License.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
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
Found 21/25 approved changesets -- score normalized to 8
Reason
8 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-qwcr-r2fm-qrc7
- Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-qw6h-vgh9-j6wx
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
- Warn: Project is vulnerable to: GHSA-m6fv-jmcg-4jfg
- Warn: Project is vulnerable to: GHSA-cm22-4g7w-348p
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/ci-unit-tests.yaml:1
- Warn: no topLevel permission defined: .github/workflows/daily_ci.yaml:1
- Warn: no topLevel permission defined: .github/workflows/promote-to-master-pr.yaml:1
- Warn: no topLevel permission defined: .github/workflows/pull.yaml:1
- Warn: no topLevel permission defined: .github/workflows/push.yaml:1
- Info: no jobLevel write permissions found
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci-unit-tests.yaml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-crypto-helpers/ci-unit-tests.yaml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci-unit-tests.yaml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-crypto-helpers/ci-unit-tests.yaml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci-unit-tests.yaml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-crypto-helpers/ci-unit-tests.yaml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/promote-to-master-pr.yaml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-sdk-js-crypto-helpers/promote-to-master-pr.yaml/master?enable=pin
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 2 third-party GitHubAction dependencies pinned
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 26 are checked with a SAST tool
Score
4.5
/10
Last Scanned on 2024-11-25
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