H.R. 1121 (119th)Bill Overview

No DeepSeek on Government Devices Act

Government Operations and Politics|Computers and information technologyComputer security and identity theft
Cosponsors
Support
Democratic
Introduced
Feb 7, 2025
Discussions
Bill Text
Current stageCommittee

Referred to the House Committee on Oversight and Government Reform.

Introduced
Committee
Floor
President
Law
Congressional Activities
01 · The brief
Plain-English summaryWhat this bill actually does

This bill directs the OMB, with several federal agencies, to produce standards requiring removal of the “DeepSeek” application (and successors by High Flyer) from executive agency information technology within 60 days. The standards must include exceptions for law enforcement, national security, and security researchers, and require documented risk mitigation for any authorized uses.

Why people may split

Liberals demand transparency and limits on secrecy exceptions.

Watch point

Narrow, administrable policy with low fiscal impact could attract bipartisan support, though vendor-specific naming may provoke some opposition.

This bill directs the OMB, with several federal agencies, to produce standards requiring removal of the “DeepSeek” application (and successors by High Flyer) from executive agency information technology within 60 days.

The standards must include exceptions for law enforcement, national security, and security researchers, and require documented risk mitigation for any authorized uses.

Passage40/100

Content is narrow and low-cost, aiding passage in House, but vendor-specific prohibition and procedural hurdles make final enactment uncertain.

CredibilityPartial

How solid the drafting looks.

Contention30/100

Liberals demand transparency and limits on secrecy exceptions.

02 · What it does

Who stands to gain, and who may push back.

Likely benefits vs burdens50% / 50%
Federal agenciesFederal agencies

These are examples from the analysis, not a ranked list of the most-affected groups.

Likely helped
  • Federal agenciesRemoves a named third‑party application from federal devices, reducing an identifiable application risk vector.
  • Federal agenciesRequires documented risk mitigation for exceptions, increasing agency accountability for authorized uses.
  • Potential benefitClarifies executive branch authority to set application controls on government information technology.
Likely burdened
  • Potential burdenAgencies will face administrative and technical costs to locate, remove, and monitor the application.
  • Federal agenciesThe 60‑day timeline may strain agency IT and compliance resources during implementation.
  • Potential burdenExceptions processes could disrupt legitimate law enforcement, security research, or classified uses if delayed.
03 · Why people split

Why the argument around this bill splits.

Liberals demand transparency and limits on secrecy exceptions.
Progressive85%

Generally supportive because it protects government systems, employee data, and civil servants from potential security or privacy risks.

Would press for transparency about the risk assessment, public reporting, and limits on exceptions to avoid secrecy or mission creep.

Leans supportive
Centrist70%

Cautiously favorable as a targeted, limited government-device security measure, but wants clear evidence, defined standards, and nonpartisan criteria to avoid arbitrary application.

Would seek precise timelines and cost/implementation guidance.

Leans supportive
Conservative80%

Likely supportive on national-security grounds and prudent restriction of potentially risky apps on government devices.

Some conservatives may prefer a broader ban covering contractors or consumer use, or stronger actions against the vendor.

Leans supportive
04 · Can it pass?

The path through Congress.

Introduced

Reached or meaningfully advanced

Committee

Reached or meaningfully advanced

Floor

Still ahead

President

Still ahead

Law

Still ahead

Passage likelihood40/100

Content is narrow and low-cost, aiding passage in House, but vendor-specific prohibition and procedural hurdles make final enactment uncertain.

Scope and complexity
24%
Scopenarrow
24%
Complexitylow
Why this could stall
  • Potential litigation claiming improper singling out of a private company
  • Scope and substance of classified national-security exceptions
05 · Recent votes

Recent votes on the bill.

No vote history yet

The bill has not accumulated any surfaced votes yet.

06 · Go deeper

Go deeper than the headline read.

Included on this page

Liberals demand transparency and limits on secrecy exceptions.

Content is narrow and low-cost, aiding passage in House, but vendor-specific prohibition and procedural hurdles make final enactment uncert…

Unlocked analysis

Pro readers get the full perspective split, passage barriers, legislative design review, stakeholder impact map, and lens-based policy tradeoff analysis for No DeepSeek on Government Devices Act.

Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.

Perspective breakdownsPassage barriersLegislative design reviewStakeholder impact map
Open full analysis