recloudstream / recloudstream/cloudstream
CloudStream is missing dependency verification
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 10.7k
- Forks
- 1.1k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 15
Description
Cloudstream is currently missing dependency verification.
This would prevent supply chain attacks and add more trust in the build process. This is especially useful for us as we fully rely on automated builds for pre-release. Adding it would increase dependency management overhead but I feel like the increased security is worth the cost.
Should we add it? Opinions are welcome!
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
Start with the linked Gradle dependency verification documentation and inspect the configuration used by the automated pre-release builds. Determine which dependencies and verification metadata must be covered; done means the automated builds verify dependencies successfully and the required maintenance overhead is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system, ci-cd, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100