Gathering detailed insights and metrics for aws-xray-sdk-express
Gathering detailed insights and metrics for aws-xray-sdk-express
Installations
npm install aws-xray-sdk-expressReleases
24
Release 3.10.2
aws-xray-sdk-node@3.10.2
Published on 12 Nov 2024
Release 3.10.1
aws-xray-sdk-node@3.10.1
Published on 19 Sept 2024
Release 3.10.0
aws-xray-sdk-node@3.10.0
Published on 09 Sept 2024
Release 3.9.0
aws-xray-sdk-node@3.9.0
Published on 10 Jun 2024
Release 3.8.0
aws-xray-sdk-node@3.8.0
Published on 06 Jun 2024
Release 3.7.0
aws-xray-sdk-node@3.7.0
Published on 05 Jun 2024
Developer
aws
Developer Guide
BETA
Module System
CommonJS
Min. Node Version
>= 14.x
Typescript Support
Yes
Node Version
16.20.2
NPM Version
lerna/6.6.2/node@v16.20.2+x64 (linux)
Statistics
273 Stars
490 Commits
156 Forks
25 Watching
8 Branches
103 Contributors
Updated on 28 Nov 2024
Languages
JavaScript (95.63%)
TypeScript (4.29%)
Shell (0.08%)
Total Downloads
Cumulative downloads
Total Downloads
63,783,078
Last day
-7.2%
56,119
Compared to previous day
Last week
-0.7%
319,123
Compared to previous week
Last month
4.9%
1,321,394
Compared to previous month
Last year
-1%
14,610,046
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
1
Peer Dependencies
1
Versions
:mega: OpenTelemetry JavaScript with AWS X-Ray
AWS X-Ray supports using OpenTelemetry JavaScript and the AWS Distro for OpenTelemetry (ADOT) Collector to instrument your application and send trace data to X-Ray. The OpenTelemetry SDKs are an industry-wide standard for tracing instrumentation. They provide more instrumentations and have a larger community for support, but may not have complete feature parity with the X-Ray SDKs. See choosing between the ADOT and X-Ray SDKs for more help with choosing between the two.
If you want additional features when tracing your Node.js applications, please open an issue on the OpenTelemetry JS Instrumentation repository.
AWS X-Ray SDK for Node.js
Installing
The AWS X-Ray SDK for Node.js is compatible with Node.js version 14.x and later. There may be issues when running on the latest odd-numbered release of Node.js.
The latest stable version of the SDK is available from NPM. For local development, install the SDK in your project directory with npm.
npm install aws-xray-sdk
Use the --save option to save the SDK as a dependency in your application's package.json.
npm install aws-xray-sdk --save
Documentation
This repository hosts all the packages we publish, which each have their own README. The Core package README covers all basic use cases of the main X-Ray SDK, including its use in Lambda. The developer guide provides in-depth guidance about using the AWS X-Ray service and SDKs. The API Reference provides guidance for using this SDK and module-level documentation.
Sample App
To get started with a functional web application instrumented with the X-Ray SDK, check out our sample app.
Getting Help
Use the following community resources for getting help with the SDK. We use the GitHub issues for tracking bugs and feature requests.
- Ask a question in the AWS X-Ray Forum.
- Open a support ticket with AWS Support.
- If you think you may have found a bug, open an issue.
Opening Issues
If you encounter a bug with the AWS X-Ray SDK for Node.js, we want to hear about it. Before opening a new issue, search the existing issues to see if others are also experiencing the issue. Include the version of the AWS X-Ray SDK for Node.js, Node.js runtime, and other dependencies if applicable. In addition, include the repro case when appropriate.
The GitHub issues are intended for bug reports and feature requests. For help and questions about using the AWS X-Ray SDK for Node.js, use the resources listed in the Getting Help section. Keeping the list of open issues lean helps us respond in a timely manner.
Contributing
We support and accept PRs from the community.
This monorepo hosts the following npm packages for the SDK:
- aws-xray-sdk
- aws-xray-sdk-core
- aws-xray-sdk-express
- aws-xray-sdk-mysql
- aws-xray-sdk-postgres
- aws-xray-sdk-restify
- Community contributed packages
Community contributions for new Middleware
If you'd like to add support for a new web framework by writing middleware for X-Ray,
please do so by creating a new package within the sdk_contrib
directory.
We are not accepting pull requests for first-party packages at this time,
but will be more than happy to host them as community contributions. This means that AWS will:
- Host them in this repository
- Publish them to NPM
- Consider them the officially recommended way of using X-Ray with that framework
- Review & merge pull requests made against them by the community
- Allow issues related to them on this repo for visibility to the community
AWS will not:
- Provide first party support through AWS Forums, AWS customer support, etc for things like questions & debugging help
- Actively develop on them (e.g. if we add a feature to the Express middleware, it will not necessarily be added to middleware in
sdk_contrib)
Testing from Source
This repo uses Lerna (use v6 or lower) to manage multiple packages. To install Lerna as a CLI:
npm install -g lerna
To install devDependencies and peerDependencies for all packages:
lerna bootstrap --hoist
This repo has a combination of TypeScript and JavaScript source files. To transpile the TypeScript files for testing, run:
lerna run compile
To run tests for all packages:
lerna run test
or go to each package and run npm test as usual.
License
The AWS X-Ray SDK for Node.js is licensed under the Apache 2.0 License. See LICENSE and NOTICE.txt for more information.
No vulnerabilities found.
Reason
all changesets reviewed
Reason
16 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
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: Apache License 2.0: LICENSE:0
Reason
no binaries found in the repo
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
6 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-v88g-cgmw-v5xw
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-mxhp-79qh-mcx6
- Warn: Project is vulnerable to: GHSA-f5x3-32g6-xq36
Reason
dependency not pinned by hash detected -- score normalized to 1
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/continuous-monitoring.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/continuous-monitoring.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/continuous-monitoring.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/continuous-monitoring.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/continuous-monitoring.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/continuous-monitoring.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/deprecate_version.yml:11: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/deprecate_version.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/lint.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/lint.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/lint.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/lint.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/lint.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/lint.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pr-build.yml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/pr-build.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pr-build.yml:52: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/pr-build.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pr-build.yml:60: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/pr-build.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/pr-build.yml:95: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/pr-build.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/release.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/release.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/release.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:59: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/release.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/smoke-test.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/smoke-test.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/smoke-test.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/aws/aws-xray-sdk-node/smoke-test.yml/master?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/continuous-monitoring.yml:32
- Warn: npmCommand not pinned by hash: .github/workflows/deprecate_version.yml:17
- Warn: npmCommand not pinned by hash: .github/workflows/lint.yml:23
- Warn: npmCommand not pinned by hash: .github/workflows/pr-build.yml:58
- Warn: npmCommand not pinned by hash: .github/workflows/release.yml:26
- Warn: npmCommand not pinned by hash: .github/workflows/smoke-test.yml:25
- Warn: npmCommand not pinned by hash: .github/workflows/smoke-test.yml:31
- Warn: npmCommand not pinned by hash: .github/workflows/smoke-test.yml:32
- Warn: npmCommand not pinned by hash: .github/workflows/smoke-test.yml:33
- Warn: npmCommand not pinned by hash: .github/workflows/smoke-test.yml:34
- Warn: npmCommand not pinned by hash: .github/workflows/smoke-test.yml:43
- Warn: npmCommand not pinned by hash: .github/workflows/smoke-test.yml:44
- Info: 0 out of 15 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 2 third-party GitHubAction dependencies pinned
- Info: 3 out of 15 npmCommand dependencies pinned
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/continuous-monitoring.yml:1
- Warn: no topLevel permission defined: .github/workflows/deprecate_version.yml:1
- Warn: no topLevel permission defined: .github/workflows/lint.yml:1
- Warn: no topLevel permission defined: .github/workflows/pr-build.yml:1
- Warn: no topLevel permission defined: .github/workflows/release.yml:1
- Warn: no topLevel permission defined: .github/workflows/smoke-test.yml:1
- Info: no jobLevel write permissions found
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 30 are checked with a SAST tool
Score
6
/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