This repository has been archived by the owner on Oct 18, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey wikke, Jude, MIT 2014 (Plasma Physics) & Twitter 2021 (Machine learning), here. I've been building this tool to enable developers to digitally sign their source code so that they can track it across platforms (e.g. bitcoin, aws, gitlab, linode, azure, etc.). I'm still building so feel free to push back, give me feedback or flat out tell me 'this sucks 😂'.\n It's an optional feature to digitally sign you source-code and track it via a blockchain (filecoin) node should you ever be audited or become entangled in a software supply-chain attack. The long-term vision is to index developer code, protect the community from supply chain attacks and be able to recommend to optimal collaboration opportunites that complement their focus. Simply compare the byte encrypted signature in you yml with the hash written to your blockchain node. If they ever differ you should escalate. See the wikke-digital-copyright for complete instructions. Feel free to contact me directly to review any questions before accepting. ~~Best: pi@haiphenai.com