These are tools published by employees that can be used by OSPOs for managing open source at scale. Please consider adding the OSPO label to GitHub projects that are valuable to open source program office teams and submit a PR to add them to this file.
- Changing the default branch name for GitHub repositories
- GitHub Action: Automatically open a pull request for repositories that have no CONTRIBUTING.md file
- Code of conduct detector based off Licensee
- License compliance - A Ruby Gem to detect under what license a project is distributed
- Licensed: A Ruby gem to cache and verify the licenses of dependencies
- GitHub Action: Allow users to configure their risk threshold for security issues reported by GitHub Code Scanning, Secret Scanning and Dependabot Security.
- Safe Settings - an app to manage policy-as-code and apply repository settings to repositories across an organization.
- GitHub's Balanced Employee IP Agreement - A policy which balances preserving the ability of employees to work on open source projects with the need to protect GitHub's intellectual property.
- Product: Dependency Graph
- Default community health file
- License detection and APIs (uses
licenseefrom above) - Organization Insights
- TODO Group: https://todogroup.org/guides/
- GitHub: opensource.guide
- Google: https://opensource.google/documentation/reference
- Linux Foundation: https://www.linuxfoundation.org/resources/open-source-guides/creating-an-open-source-program
- opensource.com: https://opensource.com/article/20/5/open-source-program-office
- ben.balter.com: https://ben.balter.com/2021/06/15/managing-open-source-communities-at-scale/