[repo-health] Low: README Rust version badge (1.70+) is likely stale — Cargo.toml missing `rust-version` field

[Liohtml]

Summary

The README displays a badge claiming Rust 1.70+ is sufficient, but Cargo.toml contains no rust-version field to enforce or document the MSRV. chromiumoxide 0.9 (published mid-2024) and other dependencies likely require a newer toolchain than 1.70 (released May 2023). Without a rust-version field, contributors and CI get no actionable error when they use an outdated compiler.

Category

README

Severity

Low

Location

• File: README.md — badge line
• File: Cargo.toml — missing rust-version field

Details

chromiumoxide 0.9 depends on crates such as windows-registry and uses API patterns that require at minimum Rust 1.75+ (stabilised async fn in traits, etc.). 1.70 predates several stabilisations used by the dependency tree.

Cargo enforces MSRV through the rust-version field in [package]:

error: package `chromiumoxide v0.9.1` cannot be built because it requires rustc 1.XX or newer

Without this field, a contributor using Rust 1.70 gets cryptic compiler errors instead.

Suggested Fix

1. Determine the actual MSRV by running cargo msrv or checking chromiumoxide's declared MSRV.
2. Add to Cargo.toml:

[package]
name = "linkedin-scraper"
version = "0.1.0"
edition = "2021"
rust-version = "1.75"  # adjust to actual minimum

3. Update the README badge:

[![Rust](https://img.shields.io/badge/rust-1.75%2B-orange.svg)](https://www.rust-lang.org)

Effort Estimate

15 min

---

Automated finding by repo-health-agent v1.0