Back to search

Bill Text Stats

12
Analyzed sections
N/A
Detected dollar total
0
Tax signals
8
Deadlines

Signal counts

Tax density 0.0%
Spending density 8.3%
Agency 9
Statutory Reference 9
Deadline 8
Privacy 3
Spending 1
Studies 1

Top agencies

agency shall 3
Administrator of the Office of Electronic 2
Administrator of the office of electronic government 1
Administrator of the Office of Electronic Government 1
Administrator of the Office of Electronic Government a 1
Administrator of the Office of Electronic Government shall 1

Statutory references

section 11103 of title 40 2
44 USC 3501 1
50 U.S.C. 3003 1
Public Law 118-187 1
section 3502 of title 44 1
section 3502 of title 44 1
section 3502 of title 44 1
section 552 of title 5 1

House Votes

No House roll call votes have been linked to this bill yet.

Timeline

Dec 23, 2024

Presented to President.

Dec 23, 2024

Presented to President.

Dec 23, 2024

Signed by President.

Dec 23, 2024

Signed by President.

Dec 23, 2024

Became Public Law No: 118-187.

Dec 23, 2024

Became Public Law No: 118-187.

Dec 18, 2024

Message on Senate action sent to the House.

Dec 17, 2024

Passed/agreed to in Senate: Passed Senate without amendment by Unanimous Consent.

Dec 17, 2024

Passed Senate without amendment by Unanimous Consent. (consideration: CR S7093)

Dec 5, 2024

Received in the Senate, read twice.

Dec 4, 2024

Mr. Langworthy moved to suspend the rules and pass the bill, as amended.

Dec 4, 2024

Considered under suspension of the rules. (consideration: CR H6340-6342)

Dec 4, 2024

DEBATE - The House proceeded with forty minutes of debate on H.R. 9566.

Dec 4, 2024

Passed/agreed to in House: On motion to suspend the rules and pass the bill, as amended Agreed to by voice vote. (text: CR H6340-6342)

Dec 4, 2024

On motion to suspend the rules and pass the bill, as amended Agreed to by voice vote. (text: CR H6340-6342)

Dec 4, 2024

Motion to reconsider laid on the table Agreed to without objection.

Sep 18, 2024

Committee Consideration and Mark-up Session Held

Sep 18, 2024

Ordered to be Reported by the Yeas and Nays: 39 - 0.

Sep 12, 2024

Introduced in House

Sep 12, 2024

Introduced in House

Sep 12, 2024

Referred to the House Committee on Oversight and Accountability.

Affected Sectors

How to read this

Sectors are deterministic matches from official Congress.gov data and cached bill text. They are source-derived signals, not conclusions about intent or economic effect.

Evidence matches count official fields, normalized subjects, cached text snippets, or extracted entities that matched the sector rules.

Impact is a bill-level rollup used for sorting and filtering. It is not an economic impact estimate.

Confidence is the strongest individual match score behind that sector.

Evidence snippets show why a sector matched and can repeat when Congress.gov repeats the same phrase across official fields.

Technology and data privacy
79 evidence matches
Impact 100% Confidence 84%

Computers and information technology

cybersecurity inline" id="HA319291B48C6459198C442FA98A8FAB4" (2) how source code sharing and open-source software collaboration can improve cybersecurity at agencies;

cybersecurity cluding estimates of the frequency and dollar value of such duplication; (2) how source code sharing and open-source software collaboration can improve cybersecurity at agencies; (3) how the adoption of cloud-based software ma

Defense
39 evidence matches
Impact 100% Confidence 76%

f title 40 This Act shall not apply to classified source code or source code developed primarily for use in a national security system (as defined in section 11103 of title 40, United States Code /re

f title 40 58126" (i) primarily for use in a national security system (as defined in section 11103 of title 40, United States Code /re

03 an agency, or part of an agency, that is an element of the intelligence community (as defined in section 3(4) of the National Security Act of 1947 ( 50 U.S.C. 3003(4) ). /subparagra

Housing and real estate
1 evidence matches
Impact 82% Confidence 76%

Not later than ts to or community development of the shared code; and (iv) the number and circumstances of all exemptions granted under section 4(a)(2). (B) Reporting requirement (i) Requirement Not later than 1 year after the date of the e

CBO Cost Estimates

Official Congressional Budget Office cost estimate links associated with this bill through Congress.gov records.

How to read this

CBO estimates are official source documents with their own assumptions, scope, and publication dates. They can score a bill, a version of a bill, or a broader legislative package.

LawLinter stores the source link from Congress.gov and does not replace the CBO document. Use these cards as pointers for source review, not as independent fiscal advice.

CBO context shows source-attributed Congressional Budget Office cost estimates linked from official Congress.gov bill records. It is research context only; read the official CBO source document for assumptions, scope, and dates.

Campaign Finance Context

Related FEC/OpenFEC campaign-finance records for lawmakers and candidates tied to this bill through source-attributed legislative relationships. These are not donations to the bill itself.

How to read this

Amounts shown here are campaign-finance totals for sponsor or cosponsor-linked candidates and their committees in the displayed FEC cycle.

They are not donations to this bill, spending on this bill, or proof that money influenced or caused sponsorship, cosponsorship, votes, or legislative outcomes.

If multiple linked lawmakers have FEC records, this section can show multiple candidate cards and separate sponsor/cosponsor rollups.

Campaign-finance context uses source-attributed FEC/OpenFEC records that are related or relevant to the displayed bill, lawmaker, candidate, committee, or legislative relationship through deterministic links. It is research context only, not proof of influence, causation, endorsement, or that money caused a sponsorship, vote, or legislative outcome.

No FEC/OpenFEC campaign-finance context is currently linked for this bill.

Lobbying Context

Related LDA.gov filings where public lobbying activity descriptions reference this bill. These records are source-attributed research context, not evidence of influence or causation.

How to read this

LDA filings are public lobbying disclosure records. LawLinter links them here only when the filing activity text contains an exact-looking reference to this bill.

A filing can mention many issues, clients, agencies, or bills. A match should be treated as a pointer for review, not as a conclusion about why legislation changed or how any lawmaker acted.

Lobbying context uses source-attributed LDA.gov records that appear related to this bill through bill references in public lobbying activity descriptions. It is research context only, not proof of influence, causation, endorsement, lobbying effectiveness, or legislative intent.

No LDA.gov lobbying disclosure context is currently linked for this bill.

Summary

49 Public Law Jul 29, 2025

Source code Harmonization And Reuse in Information Technology Act or the SHARE IT Act This act requires federal agencies to ensure that custom-developed code (i.e., source code that is produced under an agency contract, funded exclusively by the federal government, or developed by federal employees as part of their official duties) and certain technical components of the code such as architecture designs and metadata are (1) owned by the agency, (2) stored at no less than one public or private repository, and (3) accessible to federal employees under certain procedures. Agency contracts for custom-development of software must acquire and exercise rights sufficient to allow government-wide access, sharing, use, and modification of any custom-developed code. The act does not apply to source code that is classified, developed primarily for use in a national security system, or developed by an element of the intelligence community. An agency's office of the chief information officer may exempt source code from being shared or made publicly accessible to protect individual privacy. Within 120 days of enactment, the Office of Electronic Government shall establish minimum reporting standards for agencies relating to certain topics, such as measuring the frequency of reuse of code. Within one year of enactment, the Federal Acquisition Regulation must be revised to implement the act's provisions.

00 Introduced in House Dec 2, 2024

Source code Harmonization And Reuse in Information Technology Act or the SHARE IT Act This bill requires federal agencies to ensure that custom-developed code (i.e., source code that is produced under an agency contract, funded exclusively by the federal government, or developed by federal employees as part of their official duties) and certain technical components of the code such as architecture designs and metadata are (1) owned by the agency, (2) stored at no less than one public or private repository, and (3) accessible to federal employees under certain procedures. Agency contracts for custom-development of software must acquire and exercise rights sufficient to allow government-wide access, sharing, use, and modification of any custom-developed code. The bill does not apply to source code that is classified, developed primarily for use in a national security system, or developed by an element of the intelligence community. An agency's office of the chief information officer may exempt source code from being shared or made publicly accessible to protect individual privacy.

Sponsors

Amendments

No amendment records are currently available for this bill.
Compiled bill record. Bill pages combine Congress.gov source payloads, normalized relationships, cached text analysis, vote links, and deterministic sector/signal extraction. This is not an official government record or legal advice; use the official source link when accuracy matters.