GitHub expands license checks. How do you document the code your team creates?

On October 16, GitHub announced general availability of open source license compliance for eligible Enterprise Cloud repositories. It checks new or changed dependencies against an enterprise license policy.

That prompted a question for us at Ecode: alongside checking third-party code, how do teams document their own contributions?

Consider an agency delivering a project containing open-source libraries and a custom module. Keeping dependency records, agreements and dated copies of the custom code can make its history easier to explain later.

Ecode adds a timestamped record of a file’s SHA-256 fingerprint. Registration is free, and the source code stays on your device. It does not check licenses or determine ownership.

What is harder for your team to document: third-party dependencies or the history of your own code?

GitHub announcement:

https://github.blog/changelog/20...

About Ecode:

https://onecoderegister.io/?utm_...