Adopt OpenSSF Scorecards

Open
#25 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github
Domain
security

Research direction

Start by reviewing the OpenSSF Scorecards project and the linked ossf/scorecard issue 3352 about exporting the in-toto file format. Define how Scorecards should be adopted for this LoopBack security repository and what output maintainers and users should be able to inspect when the work is complete.

Written by the indexing model from the issue text.

Description

openssf

OpenSSF Scorecards is a software which attempts to grade a project's Git Repository based on a number of checks. This information would be useful to the maintainers to identify areas that need remediation, and for LoopBack users to evaluate the security posture of the project against an industry-recognised checklist.

There is ongoing discussion for exporting in-toto file format, which can be helpful in supplementing SLSA provenance: https://github.com/ossf/scorecard/issues/3352

see: https://github.com/ossf/scorecard

Dominant language
TypeScript
Stars
4
Forks
1
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from loopbackio/security

All issues in loopbackio/security

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.