[repo-monitor] Low: Real person's LinkedIn profile URL hardcoded in public example

[Liohtml]

Summary

A real individual's LinkedIn profile URL is hardcoded in the public example code. The URL identifies a specific private person by name and ID, constituting a privacy concern under GDPR/EU data protection standards for a publicly distributed code repository.

Location

• File: examples/scrape_person.rs
• Line(s): 27

Severity

Low

Details

let person = scraper
    .scrape("https://www.linkedin.com/in/elke-hartmann-68081a370")
    .await?;

The URL encodes a real person's full name and LinkedIn profile identifier. Publishing this in an open-source scraping tool's example code:

1. May violate GDPR Article 5 (data minimisation) by unnecessarily exposing a data subject's identity in code that demonstrates scraping their profile.
2. Could invite unwanted automated scraping of that individual's profile by anyone who runs the example without modification.

Suggested Fix

Replace the real profile URL with an obviously fictional placeholder:

let person = scraper
    .scrape("https://www.linkedin.com/in/example-user-profile")
    .await?;

Or use a public figure's profile that is widely used as a canonical example (e.g., a company's official representative with explicit consent).

---

Automated finding by repo-monitor

[Liohtml]

Analysis

Confirmed. Fix this.

examples/scrape_person.rs:27:

let person = scraper
    .scrape("https://www.linkedin.com/in/elke-hartmann-68081a370")
    .await?;

A real person's full name and LinkedIn profile ID is hardcoded in a public repository's example code that demonstrates how to scrape LinkedIn profiles. This creates two problems:

1. Privacy: Publishing someone's LinkedIn profile URL in scraping example code without their consent is a data subject rights issue under GDPR Article 5(1)(b) (purpose limitation) and Article 5(1)(c) (data minimisation). The person didn't consent to having their identity used in a tool that demonstrates how to scrape their profile.

2. Practical: Any real LinkedIn profile URL will eventually break — accounts get deleted, renamed, or made private.

Fix — replace with a clearly fictional example:

let person = scraper
    .scrape("https://www.linkedin.com/in/jane-doe-example-profile")
    .await?;

Or use a documented test account that the project maintainer controls and has explicitly consented to using for this purpose.

This is the quickest fix in the entire issue list — a single line change that eliminates a GDPR concern. Do it in the next commit.

Effort: 2 min.