How to Keep an Open Source Register — and Why Buyers Ask for One

Maintain a register of open-source dependencies used in your product to track licenses, identify vulnerabilities, and ensure compliance.

PlayersCTO
Initial Effort3 SP
Ongoing3 SP
FrequencyQuarterly
StagePre-Revenue

Much like your English professor wanted to see a Works Cited page, potential buyers will want to see all the open-source material your code uses disclosed.

The goal: Create a simple register of all open-source licenses used and dependencies.

How can Golden Section Assist?

Steps:

  1. Task a member of your dev team with identifying all open-source licenses and dependencies used.
  2. Fill in the appropriate information on the template provided.

Questions this play answers

What open-source licenses am I using?

Much like your English professor wanted to see a Works Cited page, potential buyers will want to see all the open-source material your code uses disclosed.

How do I ensure open-source license compliance?

Much like your English professor wanted to see a Works Cited page, potential buyers will want to see all the open-source material your code uses disclosed.

How do I scan for open-source vulnerabilities?

Much like your English professor wanted to see a Works Cited page, potential buyers will want to see all the open-source material your code uses disclosed.

When should I contribute to open-source projects?

Much like your English professor wanted to see a Works Cited page, potential buyers will want to see all the open-source material your code uses disclosed.

How do I manage open-source dependencies?

Much like your English professor wanted to see a Works Cited page, potential buyers will want to see all the open-source material your code uses disclosed.