record file contents / hashes
Open
Nobody has claimed this yet.
dynamic analysis
enhancement
good first issue
- Dominant language
- Go
- Stars
- 912
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
can be useful for diffing / analysis once a malicious package is detected. hashes can be used to compare if a malicious file is included in other packages etc.
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
No files, tests, or entry points are named. First review how package-analysis currently inspects and records package files, then define where file contents and hashes would be stored and how they support comparison across packages. Done means the required contents or hashes are recorded for detected malicious packages and can be used for cross-package analysis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100