loopbackio / loopbackio/security
Adopt OSSF Security Insights 1.0 specification
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100