[Security] Subresource Integrity - SRI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 111k
- Forks
- 4k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 45
Description
I have been thinking about opportunities for us to harden everything, and we could theoretically add Subresource Integrity to the build pipeline. Since that whole flow is entirely controlled by tauri and we can fingerprint the assets are guaranteed to be the same, we could potentially use this for external validation of the app - where a notary knows the checksums and the app validates these checksums or die().
Here is something to read about SRI
https://sri.js.org/
Contributor guide
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
The issue names no files, tests, or entry points. Start by reviewing the SRI reference and the Tauri-controlled build pipeline, then determine how asset fingerprints and validation should fit. The issue does not specify concrete completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100