On October 16, GitHub announced general availability of open source license compliance for eligible GitHub Enterprise Cloud customers.
The feature checks new or changed dependencies against an organization's license policy.
It brings up two different questions:
- What are we allowed to do with code written by others?
- What records do we keep about the code we wrote ourselves?
I'm part of the Ecode team. We work on the second question.
Ecode helps create dated records for code files. Your device calculates a SHA-256 fingerprint. The service registers it in a database, adds a trusted RFC 3161 timestamp, and records it on Polygon.
You receive a certificate and verification files. Your source code stays on your device.
Together with the original files and development history, these records can help support an authorship claim.
Ecode doesn't check software licenses or give permission to use someone else's code. Keep license information and evidence of your own work together.
Prepared with AI assistance.
Top comments (0)