Create Security Policy
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github
- Domain
- documentation, security
Research direction
Review the OpenJS Project Security Reporting guidelines and GitHub's documentation for repository security policies, linked in the issue. Use the repository's Security tab to determine the available setup, and consider the policy complete when the project has a published security reporting policy that meets the minimal graduation guidelines.
Written by the indexing model from the issue text.
Description
As part of project graduation, every OpenJS project must have a security policy.
Minimal guidelines can be found here and project owners are encouraged to use GitHub's native security policy features that can be found under the "security" tab.
- Dominant language
- JavaScript
- Stars
- 18
- Forks
- 8
- Avg merge
- 50m
- Merged PRs (30d)
- 13
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.
More from visgl/vis.gl
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·