Project: add SECURITY.md and CODE_OF_CONDUCT.md
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 83/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Read CONTRIBUTING.md to confirm the existing security reporting guidance, then add SECURITY.md and CODE_OF_CONDUCT.md with the details in the issue. Update README.md and CONTRIBUTING.md to link both files. Check GitHub's Community Standards page for both files, then open a PR referencing this issue.
Written by the indexing model from the issue text.
Description
Context
CONTRIBUTING.md says vulnerabilities go through private GitHub security advisories, but there is no SECURITY.md for GitHub to surface and no code of conduct.
Proposed scope
SECURITY.md: supported versions (latest release), how to report privately (advisory link), expected response time, scope note (the Maestro bridge, the remote-control page and the portal are the sensitive surfaces).CODE_OF_CONDUCT.md: Contributor Covenant 2.1 with a contact method.- Link both from the README and CONTRIBUTING.md.
Acceptance criteria
- GitHub's Community Standards page shows both files as present.
How to get started
- Read CONTRIBUTING.md, run
npm install && npm start. - Comment here so nobody duplicates the work; ask questions in the thread, we are happy to point you at the right file.
- Open a PR that references this issue. Run
npm test(ornpm run test:unit) first.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 adaumsilva/OrchestrAI
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
adaumsilva/OrchestrAI#51 ·
-
documentation good first issue help wanted project
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
adaumsilva/OrchestrAI#46 ·
-
area:ux enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
adaumsilva/OrchestrAI#45 ·
-
area:ux enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
adaumsilva/OrchestrAI#44 ·
-
area:ux enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
adaumsilva/OrchestrAI#43 ·
All issues in adaumsilva/OrchestrAI
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
awesome-dsh-plugin/awesome-dsh-plugin#9184 ·
Maintainers usually reply within 1 day
-
CloudredirectOpen
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
0.2.1-rc.3 compatibility: 21 peer ranges enumerate exact versions, so rc.3 is rejectedPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NanmiCoder/dsh-agent-teams#277 ·
Maintainers usually reply within 1 day
-
[ordering-review] workshop order graph: 1 confirmed ordering problem, 3 cycles are false positivesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#4943 ·
Maintainers usually reply within 1 day