npmpackage.info

Gathering detailed insights and metrics for jest-sonar

Other packages similar to jest-sonar

jest-sonar-reporter

2.0.0

A Sonar test reporter for Jest.

@casualbot/jest-sonar-reporter

2.4.0

A Sonar test reporter for Jest.

anthem-jest-sonar-reporter

2.0.4

A Sonar test reporter for Jest.

sonar-scanner

3.1.0

Wrap sonar-scanner as a node module

Gathering detailed insights and metrics for jest-sonar

jest-sonar

A jest reporter that generates sonar reports

0.2.16

MIT

JavaScript

18,449,483 3.6

Installations

npm install jest-sonar

Pull Requests

Open

2

Total

52

Closed

13

Merged

37

Issues

Open

3

Total

21

Closed

18

Releases

v0.2.16

Published on 21 Apr 2023

View all 1 releases

Developer

sh33dafi

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

13.14.0

NPM Version

8.11.0 Statistics

50 Stars

120 Commits

11 Forks

3 Watching

9 Branches

7 Contributors

Updated on 14 Sept 2024

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

18,449,483

Last day

3.4%

30,859

Compared to previous day

Last week

2.8%

153,461

Compared to previous week

Last month

13.2%

651,467

Compared to previous month

Last year

31.5%

6,981,752

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

entities strip-ansi

Dev Dependencies

@commitlint/cli @commitlint/config-conventional eslint eslint-config-prettier eslint-plugin-prettier husky jest prettier semantic-release standard-version

Versions

jest-sonar

jest-sonar is a custom test reporter for Jest. It converts the generated report into Sonar's Generic Execution format.

Installation

Using yarn:

1$ yarn add -D jest-sonar

Using npm:

1$ npm i -D jest-sonar

Configuration

Configure Jest in your jest.config file and add jest-sonar to the list of reporters.

1module.exports = {
2    ...
3    reporters: ['default',  'jest-sonar'],
4    ...
5}
6

Customize the reporter

The following options can be set to customize the reporter:

Option	Environment override	Description	Default	Accepted values
outputDirectory	JEST_SONAR_OUTPUT_DIR	The directory to which the report should be written	The projects root dir	string
outputName	JEST_SONAR_OUTPUT_NAME	The name of the report	sonar-report.xml	string
reportedFilePath	JEST_SONAR_REPORTED_FILE_PATH	Should the path be relative or absolute	'relative'	'relative' or 'absolute'
relativeRootDir	JEST_SONAR_RELATIVE_ROOT_DIR	The root directory for the relative path	jest `rootDir`	string

You can set these options when defining the reporter in jest.config:

1module.exports = {
2    ...
3        reporters: ['default',  ['jest-sonar', {
4            outputDirectory: 'my/custom/directory',
5            outputName: 'my-new-report-name.xml',
6            reportedFilePath: 'absolute'
7        }]],
8    ...
9}
10

Or you can override these options via environment variables. Environment variables will always take precedence over options set via jest.config

1$ JEST_SONAR_OUTPUT_DIR=./specialDir/ npm run jest

Contribution

Contribution guidelines for this project

Contributions to this project are welcome, either by submitting bug reports, submitting feature requests or submitting pull requests.

Creating a pull request

Fork the repo on GitHub
Clone and make changes on your machine
Commit and Push the changes to your fork
Submit a Pull request so that we can review your changes

NOTE: Be sure to merge the latest change from "upstream" before making a pull request!

Licence

This project uses the MIT license.

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

7

SAST

Determines if the project uses static code analysis.

2

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 2

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/ci.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/codeql-analysis.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:41: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/codeql-analysis.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:48: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/codeql-analysis.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:62: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/codeql-analysis.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/gh-release.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/gh-release.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/gh-release.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/gh-release.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/lock-closed-issue.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/lock-closed-issue.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pr-ci.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/pr-ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pr-ci.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/pr-ci.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/pr-ci.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/pr-ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/release.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/sh33dafi/jest-sonar/release.yml/main?enable=pin
Info: 0 out of 11 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 4 third-party GitHubAction dependencies pinned
Info: 2 out of 2 npmCommand dependencies pinned

1

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

1

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

Security-Policy

Determines if the project has published a security policy.

Score

3.6

/10

Last Scanned on 2024-11-18

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