Verifying crates.io releases with git sources
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 192
- Forks
- 43
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 1
Description
As part of our supply chain hardening, I'm trying to verify that for all crates we're using, the git sources match the published crate. This allows e.g. using the git diff for auditing the changes in a release.
The crates in this is repo have a `.cargo_vcs_info.json` in the published files, but the hash mentioned in it doesn't exist: 7d6d5acb30df69694bfc85c81513498ca93cc358
Would it be possible to publish ideally with a `.cargo_vcs_info.json` with a commit in the repo, or alternatively create tags for all crate releases so they can be matched?
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
Begin with the crates.io release process and the published `.cargo_vcs_info.json`; verify why commit 7d6d5acb30df69694bfc85c81513498ca93cc358 cannot be resolved in this repository. Done means published crates reference an existing repository commit, or each crate release has a matching git tag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100