collect hash for downloaded archive
Open
Nobody has claimed this yet.
enhancement
static analysis
- Dominant language
- Go
- Stars
- 912
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
We currently collect the hashsum for package files but not for the package archive itself. If we do this both for dynamic analysis and static analysis, we can then at least check that the analysed tarball is the same between the two types analysis.
For a start, we can do this for static analysis
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
Start by tracing the static-analysis download path and the existing collection of hashsums for package files. Add collection of the downloaded package archive's hash for static analysis, with the result available for comparison against dynamic analysis later. Done means the analysed static-analysis tarball has a recorded hash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100