Gathering detailed insights and metrics for @adobe/eslint-config-aio-lib-config
Gathering detailed insights and metrics for @adobe/eslint-config-aio-lib-config
Installations
npm install @adobe/eslint-config-aio-lib-configDeveloper
adobe
Developer Guide
BETA
Module System
CommonJS
Min. Node Version
Typescript Support
No
Node Version
18.19.1
NPM Version
10.2.4
Statistics
2 Stars
57 Commits
3 Forks
24 Watching
5 Branches
236 Contributors
Updated on 06 Jan 2023
Languages
JavaScript (100%)
Total Downloads
Cumulative downloads
Total Downloads
138,307
Last day
85.8%
877
Compared to previous day
Last week
-5.2%
6,488
Compared to previous week
Last month
235.4%
25,204
Compared to previous month
Last year
217.8%
73,854
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Peer Dependencies
8
Versions
eslint-config-aio-lib-config
Shareable ESLint config for AIO libs
Publishing (!!!!)
Any update to a dependency/peer dependency must be a major version update, if not a lot of tests will break during npm install because of a version mismatch. Use of semver is warranted here so users can choose when to update their config instead of it being forced on them. The 2.x update broke a lot of tests.
Installation
To install, use npm 5 or greater:
1npm install --save-dev @adobe/eslint-config-aio-lib-config 2npx install-peerdeps --dev @adobe/eslint-config-aio-lib-config
Add to the root .eslintrc.json file
Add this to your .eslintrc.json file in the root of your module:
1{ 2 "extends": "@adobe/eslint-config-aio-lib-config" 3}
Exclude test/e2e folders from the node/no-unpublished-require rule
The node/no-unpublished-require rule prevents using a module when it hasn't been added in the dependencies key in package.json.
This setting excludes this rule for test folders, where the module may have been added in the devDependencies key in package.json only.
Add this setting to a .eslintrc.json file in the affected folder:
1{ 2 "rules": { 3 "node/no-unpublished-require": 0 4 } 5}
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities 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
security policy file detected
Details
- Info: security policy file detected: github.com/adobe/.github/.github/SECURITY.md:1
- Info: Found linked content: github.com/adobe/.github/.github/SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: github.com/adobe/.github/.github/SECURITY.md:1
- Info: Found text in security policy: github.com/adobe/.github/.github/SECURITY.md:1
Reason
Found 6/24 approved changesets -- score normalized to 2
Reason
dependency not pinned by hash detected -- score normalized to 1
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/eslint-config-aio-lib-config/node.js.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/eslint-config-aio-lib-config/node.js.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/node.js.yml:34: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/eslint-config-aio-lib-config/node.js.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-push-publish-to-npm.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/eslint-config-aio-lib-config/on-push-publish-to-npm.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-push-publish-to-npm.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/eslint-config-aio-lib-config/on-push-publish-to-npm.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/on-push-publish-to-npm.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/eslint-config-aio-lib-config/on-push-publish-to-npm.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/version-bump-publish.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/eslint-config-aio-lib-config/version-bump-publish.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/version-bump-publish.yml:23: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/eslint-config-aio-lib-config/version-bump-publish.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/version-bump-publish.yml:34: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/eslint-config-aio-lib-config/version-bump-publish.yml/master?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/node.js.yml:29
- Warn: npmCommand not pinned by hash: .github/workflows/on-push-publish-to-npm.yml:18
- Warn: npmCommand not pinned by hash: .github/workflows/version-bump-publish.yml:27
- Info: 0 out of 6 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 3 third-party GitHubAction dependencies pinned
- Info: 1 out of 4 npmCommand dependencies pinned
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/node.js.yml:1
- Warn: no topLevel permission defined: .github/workflows/on-push-publish-to-npm.yml:1
- Warn: no topLevel permission defined: .github/workflows/version-bump-publish.yml:1
- Info: no jobLevel write permissions found
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 14 are checked with a SAST tool
Score
4.8
/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