hackforla / hackforla/311-data
PRD - Implement repository security best practices
- Dominant language
- JavaScript
- Stars
- 73
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
### Overview
We need to implement the following best practices so that the 311 Data project has all processes in place to prevent or handle security flaws.
### More Info
This list comes from a ChatGPT list, so it doesn't have knowledge about anything we've completed already. We also most likely need to double check with the org-rep to determine if this list is worth considering.
### Action Items
- [ ] Create draft security advisory for private discussion
- [ ] Collaborate on fixes using temporary private forks
- [ ] Request CVE identification numbers (GitHub is a CVE Numbering Authority)
- [ ] Publish advisory once patch is ready
- [ ] Advisory automatically feeds into GitHub Advisory Database
- [ ] Create workflow for: Coordinated Vulnerability Disclosure (CVD)
- aka Security vulnerabilities should be handled privately until fixes are available
- [ ] **Dependency Security**:
- [ ] - **Dependency Graph**: Enable to track project dependencies
- [ ] - **Dependabot Alerts**: Automated vulnerability notifications
- [ ] - **Dependabot Security Updates**: Automatic pull requests for security patches
- [ ] - **Dependabot Version Updates**: Keep dependencies current
- [ ] - **Dependency Review**: Visualize dependency changes in pull requests
- [ ] **Code Security Features**:
- [ ] - **Code Scanning**: Automated vulnerability detection using CodeQL
- [ ] - **Default Setup**: GitHub automatically configures scanning
- [ ] - **Advanced Setup**: Custom workflow configuration
- [ ] - **Copilot Autofix**: AI-powered vulnerability remediation
- [ ] **Secret Protection**:
- [ ] - **Secret Scanning**: Detect exposed credentials and tokens
- [ ] - **Push Protection**: Prevent secret commits
- [ ] - **Non-provider Pattern Detection**: Find custom secret formats
- [ ] Create all repository level documentation
- [ ] - `CODE_OF_CONDUCT.md` - Community behavior standards
- [ ] - `CONTRIBUTING.md` - Contribution guidelines and processes
- [x] - `SECURITY.md` - Vulnerability reporting instructions
- https://github.com/hackforla/311-data/blob/main/SECURITY.md
- [ ] - `SUPPORT.md` - Support resources and contact information
- [ ] - Issue and pull request templates
- [ ] - Discussion category forms
- [ ] - Funding/sponsor information
### Resources/Instructions
- https://docs.google.com/document/d/1Aa1qBEUfrMq4d4d4bg_rCaQ-K_za-yTCEAK-ViyxiwA/edit?tab=t.0
Contributor guide
Assessment
This issue has not been assessed yet.