OSPS-AC-02.01 checks allow_forking, which does not measure collaborator permission defaults
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
Research direction
Find the OSPS-AC-02.01 control and inspect its check, name, help text, and remediation references to allow_forking. First decide how the control should handle organization-owned versus user-owned repositories, as the issue says this needs a decision; for organization repositories, assess default_repository_permission from GET /orgs/{org}. Done means the control evaluates the stated collaborator-permission requirement and its name, help text, and remediation match.
Written by the indexing model from the issue text.
Description
OSPS-AC-02.01 (Maturity Level 1-3) reads:
When a new collaborator is added, the version control system MUST require manual permission assignment, or restrict the collaborator permissions to the lowest available privileges by default.
The control is named AllowForking and concludes PASS on gh api /repos/{owner}/{repo} -> allow_forking == true. Whether forking is allowed has nothing to do with the permissions a new collaborator receives, so this PASS is unrelated to the requirement.
Suggested direction:
- for organization-owned repositories, the org's
default_repository_permission(GET /orgs/{org}, visible to org owners) is closer:readornonesatisfies the requirement; - for user-owned repositories GitHub requires choosing a permission when inviting a collaborator, which arguably satisfies "manual permission assignment"; that needs a decision rather than a check;
- update the control's name, help text and remediation (which also reference allow_forking).
- Dominant language
- Python
- Stars
- 22
- Forks
- 27
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 39
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 darnitdevorg/darnit
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
darnitdevorg/darnit#589 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
darnitdevorg/darnit#587 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
darnitdevorg/darnit#585 ·
Maintainers usually reply within 1 day
-
quality
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
darnitdevorg/darnit#523 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
darnitdevorg/darnit#516 ·
Maintainers usually reply within 1 day
All issues in darnitdevorg/darnit
Similar issues
-
python triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/semantic-kernel#14590 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
pinterest/pymemcache#662 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 62/100
gnocchixyz/gnocchi#1527 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
tenstorrent/tt-model-manager#181 ·
Maintainers usually reply within 1 day