Gathering detailed insights and metrics for yarn-audit-html
Gathering detailed insights and metrics for yarn-audit-html
Installations
npm install yarn-audit-htmlScore
57.6
Supply Chain
91.4
Quality
75.9
Maintenance
100
Vulnerability
99.6
License
Releases
32
Developer
davityavryan
Developer Guide
BETA
Module System
ESM
Min. Node Version
>=16
Typescript Support
Yes
Node Version
NPM Version
Statistics
29 Stars
184 Commits
13 Forks
2 Watching
10 Branches
6 Contributors
Updated on 27 Sept 2024
Languages
TypeScript (54.66%)
EJS (32.77%)
JavaScript (12.38%)
Shell (0.19%)
Total Downloads
Cumulative downloads
Total Downloads
1,901,347
Last day
5.1%
1,867
Compared to previous day
Last week
4.5%
10,269
Compared to previous week
Last month
10%
43,417
Compared to previous month
Last year
4.9%
522,597
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dev Dependencies
16
Optional Dependencies
1
Versions
yarn-audit-html
Generate a HTML report for Yarn Audit
Install
1yarn add -D yarn-audit-html 2# or globally 3yarn global add yarn-audit-html
Usage
To generate a report, run the following:
Yarn V1
1yarn audit --json | yarn yarn-audit-html
Yarn V2+
1yarn npm audit --json | yarn yarn-audit-html
By default, unique vulnerability list will be generated (Grouped by MODULE_NAME, VERSION, VULNERABLE_VERSIONS,
ADVISORY_CREATED_DATE and CWE) to yarn-audit.html. This way, even if same version of package has multiple
vulnerabilities, they will be counted.
If you want to specify the output file, add the --output option:
1yarn audit --json | yarn yarn-audit-html --output report.html
You can also fully customize the generated report by providing --template option followed by your own EJS template:
1yarn audit --json | yarn yarn-audit-html --template ./my-awesome-template.ejs
There is also a possibility to change default theme(materia) to any of available in
Bootswatch with --theme option followed by theme name: p.s. In future
major release default template will change to dark theme.
1yarn audit --json | yarn yarn-audit-html --theme darkly
If you'd like the generator to exit with non-zero exit code when vulnerabilities are found, you can add the
--fatal-exit-code option:
1yarn audit --json | yarn yarn-audit-html --fatal-exit-code
Inspired by npm-audit-html package.
See changelog here.
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.md:0
- Info: FSF or OSI recognized license: MIT License: LICENSE.md:0
Reason
SAST tool detected but not run on all commits
Details
- Info: SAST configuration detected: CodeQL
- Warn: 0 commits out of 13 are checked with a SAST tool
Reason
8 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-ghr5-ch3p-vcr6
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
- Warn: Project is vulnerable to: GHSA-3787-6prv-h9w3
- Warn: Project is vulnerable to: GHSA-9qxr-qj54-h672
- Warn: Project is vulnerable to: GHSA-m4v8-wqvr-p9f7
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Info: jobLevel 'actions' permission set to 'read': .github/workflows/codeql.yml:16
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/codeql.yml:17
- Warn: no topLevel permission defined: .github/workflows/codeql.yml:1
- Warn: no topLevel permission defined: .github/workflows/test.yml:1
- Info: no jobLevel write permissions found
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/17 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/davityavryan/yarn-audit-html/codeql.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/davityavryan/yarn-audit-html/codeql.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/davityavryan/yarn-audit-html/codeql.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/davityavryan/yarn-audit-html/codeql.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/test.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/davityavryan/yarn-audit-html/test.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/davityavryan/yarn-audit-html/test.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/davityavryan/yarn-audit-html/test.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:37: update your workflow using https://app.stepsecurity.io/secureworkflow/davityavryan/yarn-audit-html/test.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/test.yml:55: update your workflow using https://app.stepsecurity.io/secureworkflow/davityavryan/yarn-audit-html/test.yml/master?enable=pin
- Info: 0 out of 7 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 2 third-party GitHubAction dependencies pinned
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Score
3.1
/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