Idea based on other awesome pages: kotlin.link, awesome-typescript...
To add new entries, make a PR creating a new markdown .md file in the _bundles folder using other files as reference for the structure.
bundle("0️⃣https://github.com/korlibs/korge-bundles.git1️⃣::korge-admob2️⃣::1f15b6228bfe9deeccb995aff950c04923cebee63️⃣##daf1d3ced756e412a8eb389721ccf753d8900a5cd5dd503ffef19e37e510c4e8")
- 0️⃣ Link to GIT repository (a URL you can use with
git clone URL) - 1️⃣
::and a folder inside the GIT repository or.for the root directory - 2️⃣
::and a ref (branch, tag or commit) in the GIT repository. Normally a specific commit SHA1 hash referencing a specific commit. - 3️⃣
##and a SHA256 hash of the content of that folder. That SHA256 is generated by the plugin by using the actual content of the referenced folder files. If you don't specify the##segment, that's a warning on the plugin, pointing to the right SHA256. And if the hash is specified and doesn't match, the gradle building fails with a mismatch.
https://en.wikipedia.org/wiki/SHA-1
Since 2005, SHA-1 has not been considered secure against well-funded opponents
Just referencing to a SHA1 commit would not be secure enough as a collision could be found. But the extra SHA256 for the content allows to securely reference to external repositories without worrying for the content to be modified. In fact, a malicious attacker would need to have access to a repository, rewrite/reupload the history of the repository creating a commit with the same SHA1, that also has the same SHA256 for the content, which is impractical.
This means that a single bundle URL should load always the same content, or to not load anything.