gpg-check of artifacts.
Open
stage/waiting-on-upstream
theme/artifact
theme/dependencies
type/enhancement
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
Would it make sense to expand the artifact checksum to actually gpg checking the jar/binary when using java-driver, raw and other drivers that would benefit?
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or implementation entry points are named. Start by locating the existing artifact checksum handling for the java-driver, raw, and other drivers, then clarify the GPG verification scope and supported artifacts. Done should include an agreed approach for checking the referenced jars or binaries and coverage for the affected drivers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100