You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/checks.md
+8-7
Original file line number
Diff line number
Diff line change
@@ -292,9 +292,12 @@ The highest score is awarded when all workflows avoid the dangerous code pattern
292
292
Risk: `High` (possibly vulnerable to attacks on known flaws)
293
293
294
294
This check tries to determine if the project uses a dependency update tool,
295
-
specifically [dependabot](https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates) or
Out-of-date dependencies make a project vulnerable to known flaws and prone to attacks.
298
301
These tools automate the process of updating dependencies by scanning for
299
302
outdated or insecure requirements, and opening a pull request to update them if
300
303
found.
@@ -310,7 +313,7 @@ low score is therefore not a definitive indication that the project is at risk.
310
313
311
314
312
315
**Remediation steps**
313
-
- Signup for automatic dependency updates with [dependabot](https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates) or [renovatebot](https://docs.renovatebot.com/configuration-options/) and place the config file in the locations that are recommended by these tools. Due to https://github.com/dependabot/dependabot-core/issues/2804 Dependabot can be enabled for forks where security updates have ever been turned on so projects maintaining stable forks should evaluate whether this behavior is satisfactory before turning it on.
316
+
- Signup for automatic dependency updates with one of the previously listed dependency update tools and place the config file in the locations that are recommended by these tools. Due to https://github.com/dependabot/dependabot-core/issues/2804 Dependabot can be enabled for forks where security updates have ever been turned on so projects maintaining stable forks should evaluate whether this behavior is satisfactory before turning it on.
314
317
- Unlike dependabot, renovatebot has support to migrate dockerfiles' dependencies from version pinning to hash pinning via the [pinDigests setting](https://docs.renovatebot.com/configuration-options/#pindigests) without aditional manual effort.
315
318
316
319
## Fuzzing
@@ -478,9 +481,7 @@ dependencies using the [GitHub dependency graph](https://docs.github.com/en/code
478
481
- If your project is producing an application and the package manager supports lock files (e.g. `package-lock.json` for npm), make sure to check these in the source code as well. These files maintain signatures for the entire dependency tree and saves from future exploitation in case the package is compromised.
479
482
- For Dockerfiles used in building and releasing your project, pin dependencies by hash. See [Dockerfile](https://github.com/ossf/scorecard/blob/main/cron/internal/worker/Dockerfile) for example. If you are using a manifest list to support builds across multiple architectures, you can pin to the manifest list hash instead of a single image hash. You can use a tool like [crane](https://github.com/google/go-containerregistry/blob/main/cmd/crane/README.md) to obtain the hash of the manifest list like in this [example](https://github.com/ossf/scorecard/issues/1773#issuecomment-1076699039).
480
483
- For GitHub workflows used in building and releasing your project, pin dependencies by hash. See [main.yaml](https://github.com/ossf/scorecard/blob/f55b86d6627cc3717e3a0395e03305e81b9a09be/.github/workflows/main.yml#L27) for example. To determine the permissions needed for your workflows, you may use [StepSecurity's online tool](https://app.stepsecurity.io/) by ticking the "Pin actions to a full length commit SHA". You may also tick the "Restrict permissions for GITHUB_TOKEN" to fix issues found by the Token-Permissions check.
481
-
- To help update your dependencies after pinning them, use tools such as
Copy file name to clipboardExpand all lines: docs/checks/internal/checks.yaml
+8-9
Original file line number
Diff line number
Diff line change
@@ -57,9 +57,12 @@ checks:
57
57
Risk: `High` (possibly vulnerable to attacks on known flaws)
58
58
59
59
This check tries to determine if the project uses a dependency update tool,
60
-
specifically [dependabot](https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates) or
Out-of-date dependencies make a project vulnerable to known flaws and prone to attacks.
63
66
These tools automate the process of updating dependencies by scanning for
64
67
outdated or insecure requirements, and opening a pull request to update them if
65
68
found.
@@ -75,9 +78,7 @@ checks:
75
78
76
79
remediation:
77
80
- >-
78
-
Signup for automatic dependency updates with
79
-
[dependabot](https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates) or
80
-
[renovatebot](https://docs.renovatebot.com/configuration-options/) and place
81
+
Signup for automatic dependency updates with one of the previously listed dependency update tools and place
81
82
the config file in the locations that are recommended by these tools. Due to
82
83
https://github.com/dependabot/dependabot-core/issues/2804 Dependabot can
83
84
be enabled for forks where security updates have ever been turned on so projects
@@ -506,9 +507,7 @@ checks:
506
507
the "Pin actions to a full length commit SHA". You may also tick the "Restrict permissions for GITHUB_TOKEN" to fix issues found
507
508
by the Token-Permissions check.
508
509
- >-
509
-
To help update your dependencies after pinning them, use tools such as
0 commit comments