OpenRefine / OpenRefine/openrefine.org
Provide checksums for downloads
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 161
- Forks
- 142
- Avg merge
- 6h 10m
- Merged PRs (30d)
- 9
Description
It has been requested multiple times that we publish the checksums of our downloads. This helps people check the integrity of the software they have downloaded. This could be integrated in the website, hopefully in a non-intrusive way for the user (only showing this information to the people who need it) and for the release manager (not having to compute those checksums manually would be great).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing how downloads and releases are published on the website, then define a way to expose download checksums without burdening users or release managers; done means published downloads have verifiable checksums and the computation is not manual.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100