Create a control for review/maintenance/upkeep
Open
Nobody has claimed this yet.
criteria
enhancement
- Dominant language
- Go
- Stars
- 166
- Forks
- 44
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 13
Description
In discussing #302 today:
- Don’t have a specific guidance around keeping dependencies up to date
- Have a policy for addressing SCA findings, but not frequency
- VM-05.03 somewhat addresses this at level 3
- Evan would like a “heartbeat” that the project is maintained
- Decision: have a level 2 or 3 control around frequency of review / maintenance / upkeep
- Decision: consider adding a criteria around a dated statement that the software is currently maintained (this is an inverse of DO-04 and DO-05, because @evankanderson doesn't believe in statements about the future)
Contributor 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.
Research direction
Start by reading the discussion in #302 and the existing VM-05.03, DO-04, and DO-05 controls. Resolve whether the new control belongs at level 2 or 3 and whether it should include a dated statement of current maintenance; done means the agreed review, upkeep, and maintenance criteria are documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100