Reference Source

State Right-to-Repair Laws: Coverage, Requirements, and Effective Dates

Which US states have enacted right-to-repair laws, what products each law covers (electronics, agricultural equipment, powered wheelchairs, automobiles), the price threshold above which parts and documentation must be provided, whether parts-pairing is prohibited, the enforcement mechanism (state AG only vs. private right of action), penalty amounts, and the effective date. As of August 2026, at least 8 states have enacted laws and 28+ have pending legislation.

Records6
Sources1
Verified
Review by
Licenceunknown

The data

statelaw citationeffective datecovered productsprice thresholdparts pairing prohibitedexcluded productsenforcementmax penalty
CaliforniaRight to Repair ActJuly 1, 2024electronics and appliance$50 or more; over $100 for up to seven years, $50 to $99.99 for up to three yearsnot addressedalarm systems (such as fire protection systems); video game consoles; products posing safety or security risks if repaired improperly; products no longer provided by manufacturer to authorized resellersno private cause of action; state actors may bring a civil action in Superior Court$1,000 per day for the first violation, $2,000 per day for the second violation, and $5,000 per day for the third and subsequent violations
ColoradoRight to Repair law2024digital electronic equipment, agricultural equipment, and powered wheelchairsnot specifiedtrue, for digital equipment manufactured or used in the state after January 1, 2026Marine vessels, aviation and motor vehicles; Medical devices other than powered wheelchairs; Video game consoles; Certain construction-related equipmentdeceptive trade practice; may be privately enforcedup to $20,000 per violation
MassachusettsAn Act Relative to Automotive Repair2013automobilesnot specifiednot addressednon-automotive products (law centers on automobiles)unfair method of competition and an unfair or deceptive act; private cause of action available under Section 6(c) after written notice through NASTF processcivil penalties are available up to $10,000 for each violation
MinnesotaDigital Fair Repair ActJuly 1, 2024digital electronic equipmentnot specifiednot addressedFarm machinery; Portable generators; Motor vehicles; Cybersecurity products; Medical Equipment and devices; Video game consolesdeceptive trade practice; private cause of action under Deceptive Trade Practices Act; attorney general civil penalties up to $25,000civil penalties up to $25,000
New YorkDigital Fair Repair ActJuly 1, 2023digital electronic equipmentnot specifiednot addressedRefrigerators, ovens, microwaves; Air conditioning/heating units; Security or alarm systems; Gaming or entertainment consolesOffice of the Attorney General enforcement; no private cause of actioncivil penalties up to $500 per violation
OregonSB 1596January 1, 2025consumer electronic equipmentnot specifiedtrue, for consumer electronic equipment manufactured for the first time and first sold or used in Oregon after January 1, 2025motor vehicles, medical devices, HVAC equipment, solar energy systems, electrical energy storage systems, video game consoles, off-road equipment including farm and utility tractors, marine vessels, electric toothbrushesattorney general may bring civil actions in response to consumer complaintsup to $1,000 for each day the violation continues

Where this came from

Every record above links the page it was taken from and quotes the sentence that states it. These are the 1 source this dataset was assembled from.

Machine-readable

From your own code

Same records, same quotes, without scraping the page: refsource is on PyPI and npm. Each value comes back carrying the URL it was read from and the sentence on that page that states it — .source and .quote sit on the value itself rather than in a side channel, so the checking step is available instead of skipped.

pip install refsource
refsource lookup state-right-to-repair-laws state=California

npx -y refsource lookup state-right-to-repair-laws state=California

Set your AI assistant up to use this

Two files and no account. Put this in .mcp.json at the root of your project — Claude Code, Cursor, Windsurf, VS Code and Codex all read that file — and your assistant can look this dataset up instead of recalling it. The server is remote, keyless and read-only.

{
  "mcpServers": {
    "referencesource": {
      "type": "http",
      "url": "https://referencesource.org/mcp"
    }
  }
}

Add to Cursor · or, on the command line: claude mcp add --transport http referencesource https://referencesource.org/mcp --scope project

Then one line in the project's CLAUDE.md or AGENTS.md, so the assistant knows when to reach for it:

When a question needs "State Right-to-Repair Laws: Coverage, Requirements, and Effective Dates", call the referencesource MCP server at https://referencesource.org/mcp (tool `search_records`, dataset_slug `state-right-to-repair-laws`) instead of answering from memory — every record it returns carries its source URL and a verbatim quote from that page.

What each tool does, and the servers built over single registers: Connect your AI assistant.

6 records. last verified against source . due for re-check by .

Licence. unknown