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
Scorecard is an automated tool that assesses a number of important heuristics ("checks") associated with software security and assigns each check a score of 0-10. You can use these scores to understand specific areas to improve in order to strengthen the security posture of your project. You can also assess the risks that dependencies introduce, and make informed decisions about accepting these risks, evaluating alternative solutions, or working with the maintainers to make improvements.
We are currently scoring 5.3/10:
Find below the checks we need to improve on and the associated remediation steps.
Poor scoring checks
How to improve check scores
Fuzzing
add fuzzing test cases. I've setup this on my import-from-esm package, see commit 9abddb5 (note: it uses ava but there's also a jest plugin).
SAST
run CodeQL checks in CI/CD by following the instructions here.
also regarding the security policy, we'd need an email address and PGP key accessible to the (main) maintainers. I'm unsure how to go about this, please let me know if you have any ideas!
We are currently scoring
5.3/10
:Find below the checks we need to improve on and the associated remediation steps.
Poor scoring checks
How to improve check scores
Fuzzing
import-from-esm
package, see commit 9abddb5 (note: it usesava
but there's also ajest
plugin).SAST
Security-Policy
SECURITY.md
(example).Token Permissions
Pinned-Dependencies
Code Review
main
).Vulnerabilities
The text was updated successfully, but these errors were encountered: