Adopt OSSF Security Insights 1.0 specification

Open
#37 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
Domain
security

Research direction

Start by reading the OSSF Security Insights 1.0 specification and the linked Jaeger SECURITY-INSIGHTS.yml example. Review the related security.txt, security-README, and LoopBack security issue references, then define how LoopBack would adopt the specification and document comparisons with similar standards.

Written by the indexing model from the issue text.

Description

openssf

OSSF Security Insights 1.0 specification was recently-ish announced. It defines a standard YAML file to declare a project's security processes

Adopting this specification

#todo: How exactly would LoopBack adopt this specification?

Existing implementations

Comparisons

#todo: Add comparisons between similar standards such as:

References

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.