{"id":18793082,"url":"https://github.com/dsacms/ospo-guide","last_synced_at":"2026-02-01T12:35:16.878Z","repository":{"id":231392466,"uuid":"781679170","full_name":"DSACMS/ospo-guide","owner":"DSACMS","description":"Open Source Program Office Guide for CMS.gov","archived":false,"fork":false,"pushed_at":"2026-01-22T19:42:44.000Z","size":4823,"stargazers_count":9,"open_issues_count":13,"forks_count":6,"subscribers_count":1,"default_branch":"main","last_synced_at":"2026-01-23T12:31:54.245Z","etag":null,"topics":["featured","guide","ospo"],"latest_commit_sha":null,"homepage":"https://dsacms.github.io/ospo-guide/","language":"HTML","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"cc0-1.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/DSACMS.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":"SECURITY.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2024-04-03T20:47:21.000Z","updated_at":"2026-01-22T19:42:50.000Z","dependencies_parsed_at":"2024-04-03T21:52:38.448Z","dependency_job_id":"16a6d040-0d77-447c-8fec-f8d66dfe99d3","html_url":"https://github.com/DSACMS/ospo-guide","commit_stats":null,"previous_names":["dsacms/ospo-guide"],"tags_count":1,"template":false,"template_full_name":null,"purl":"pkg:github/DSACMS/ospo-guide","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/DSACMS%2Fospo-guide","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/DSACMS%2Fospo-guide/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/DSACMS%2Fospo-guide/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/DSACMS%2Fospo-guide/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/DSACMS","download_url":"https://codeload.github.com/DSACMS/ospo-guide/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/DSACMS%2Fospo-guide/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28978177,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-01T12:13:08.691Z","status":"ssl_error","status_checked_at":"2026-02-01T12:13:08.356Z","response_time":56,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["featured","guide","ospo"],"created_at":"2024-11-07T21:23:28.694Z","updated_at":"2026-02-01T12:35:16.872Z","avatar_url":"https://github.com/DSACMS.png","language":"HTML","funding_links":[],"categories":[],"sub_categories":[],"readme":"# CMS Open Source Program Office Guide\n\nospo-guide is a collection of resources written by the CMS Open Source Program Office.\nhttps://dsacms.github.io/ospo-guide/\n\nWhat's in the guide:\n\n- [Inbound](https://dsacms.github.io/ospo-guide/inbound/)\n- [Outbound](https://dsacms.github.io/ospo-guide/outbound)\n- [Growing](https://dsacms.github.io/ospo-guide/growing)\n- [Resources](https://dsacms.github.io/ospo-guide/resources)\n- [About](https://dsacms.github.io/ospo-guide/about)\n\n# Digital Service at CMS (DSACMS)\n\nWe're a group of civic-minded technologists transforming how the federal government delivers healthcare to the American people. The Digital Service at CMS (DSAC) consists of engineers, designers, and product managers—serving our country by building and maintaining the technology underpinning our national health care programs.\n\n# Centers for Medicare and Medicaid Services (CMS)\n\nEvery day, millions of people in this country interact with the healthcare system. We believe these interactions should be straightforward, transparent and seamless. Whether it's looking for health insurance, making sense of medical bills, or researching nursing homes, we are working to unlock medical information and empower people with health data.\n\n- [76M people on Medicaid \u0026 CHIP](https://www.medicaid.gov/medicaid/program-information/medicaid-and-chip-enrollment-data/report-highlights/index.html) (2024)\n- [67M people on Medicare](https://data.cms.gov/summary-statistics-on-beneficiary-enrollment/medicare-and-medicaid-reports/medicare-monthly-enrollment) (2024)\n- [21M found insurance in ACA marketplace](https://www.cms.gov/newsroom/press-releases/historic-213-million-people-choose-aca-marketplace-coverage) (2024)\n\n# What does the Digital Service at CMS do?\n\nWe work to transform the U.S. healthcare system by:\n\n- Modernizing systems\n- Improving the design of healthcare experiences\n- Participating in policy development\n- Delivering value to the government, healthcare providers, and patients\n\nWe accomplish these goals by bringing the best and brightest talent from industry and government to CMS for a \"tour of duty.\" By collaborating closely with dedicated CMS career civil servants, our work includes everything from creating public websites to implementing new legislation in back-office systems. Learn more about our work [here.](https://www.cms.gov/digital-service)\n\n# What does the Open Source Program Office (OSPO) at CMS do?\n\nEstablish and maintain guidance, policies, practices, and talent pipelines that advance equity, build trust, and amplify impact across CMS, HHS, and Federal Open Source Ecosystems by working and sharing openly.\n\n## CMS OSPO in the News\n\n- [Open Source and the Digital Service at CMS.gov - All Things Open 2022](https://www.youtube.com/watch?v=Q0EJIevZS0I)\n- Whitehouse Open Source Software Security Initiative (OS3I) Supply Chain RFI\n- [Innersource Summit 2023: Innersource to Open Source Journey in Government](https://innersourcecommons.org/events/isc-2023/)\n- [Inside CMS’ Groundbreaking Open Source Program Office](https://www.youtube.com/watch?v=34LQnyB3ydQ)\n- [Repodiving into Open Source at CMS.gov](https://www.youtube.com/watch?v=AypgQch2Qpk)\n- [OSPOs in Highly Regulated Environments Panel Discussion @ Open Source Summit EU 2023](https://osseu2023.sched.com/event/1OGeo/panel-discussion-ospos-transition-paths-for-regulated-environments-ana-jimenez-santamaria-linux-foundation-maurice-hendriks-city-of-amsterdam-nico-rikken-alliander-clare-dillon-innersourcecommons-thomas-steenbergen-epam?iframe=no\u0026w=100%\u0026sidebar=yes\u0026bg=no)\n- TODOGroup OSPOlogy September 2023 Meeting\n- OSPOs for Good Summit 2023 @ United Nations Headquarters NYC\n- [PyCon May 2024](https://github.com/DSACMS/pycon-poster-2024/blob/main/repo-baselines.pdf)\n- Code for America May 2024\n- Open Source Summit North America (OSSNA) 2024\n  - [Establishing a Repository Baseline](https://www.youtube.com/watch?v=v0aaVBicOjI)\n  - [Repository Cohorts](https://www.youtube.com/watch?v=FpVNSAj9eDg)\n\n## Acknowlegements\n\nOur work is developed as a collaboration between the United States Digital Service (USDS.gov), The Department of Health and Human Services (HHS.gov), The Digital Service at the Centers for Medicare \u0026 Medicaid Services (CMS.gov), The USDigitalResponse.org, and other Federal Open Source Community Members.\n\nThank you all for your support and contributions.\n\n# Development and Software Delivery Lifecycle\n\nThe following guide is for members of the project team who have access to the repository as well as code contributors. The main difference between internal and external contributions is that external contributors will need to fork the project and will not be able to merge their own pull requests. For more information on contributing, see: [CONTRIBUTING.md](./CONTRIBUTING.md).\n\n## Local Development\n\nThe site uses 11ty. Ensure that you have the latest version of [Node](https://nodejs.org/en/download) installed.\n\nTo run the site locally:\n\n1. Clone this repo\n2. From the repo directory, run:\n   ```sh\n   npm install\n   npm run dev\n   ```\n3. Open http://localhost:8080\n\n## I’d like to make a contribution, how do I update this content?\n\nWe welcome contributions to be made to our resources. All are encouraged to suggest improvements that benefit the rest of the organization. To make a contribution to a document:\n\n1. Find markdown file with document contents located in `/content`.\n2. Make edits in a separate branch. Be sure to update `subnav` front matter if new sections are made.\n3. Create a pull request with anyone in the OSPO team as reviewers as noted in [COMMUNITY.md](COMMUNITY.md).\n\n## Coding Style and Linters\n\nWe use a github workflow in place that performs a number of tests on every pull request:\n\n- Automated accessbility test with`pa11y-ci`\n- Code linting with `eslint`\n- HTML validation with `html-validate`\n- Internal link checking with `check-html-links`\n\nAdditionally, we use `prettier` for code formatting.\n\n## Branching Model\n\nThis project follows [trunk-based development](https://trunkbaseddevelopment.com/), which means:\n\n- Make small changes in [short-lived feature branches](https://trunkbaseddevelopment.com/short-lived-feature-branches/) and merge to `main` frequently.\n- Be open to submitting multiple small pull requests for a single ticket (i.e. reference the same ticket across multiple pull requests).\n- Treat each change you merge to `main` as immediately deployable to production. Do not merge changes that depend on subsequent changes you plan to make, even if you plan to make those changes shortly.\n- Ticket any unfinished or partially finished work.\n- Tests should be written for changes introduced, and adhere to the text percentage threshold determined by the project.\n\nThis project uses **continuous deployment** using [Github Actions](https://github.com/features/actions) which is configured in the [./github/workflows](.github/workflows) directory.\n\nPull-requests are merged to `main` and the changes are immediately deployed to the production environment.\n\n## Community\n\nThe ospo-guide team is taking a community-first and open source approach to the product development of this tool. We believe government software should be made in the open and be built and licensed such that anyone can download the code, run it themselves without paying money to third parties or using proprietary software, and use it as they will.\n\nWe know that we can learn from a wide variety of communities, including those who will use or will be impacted by the tool, who are experts in technology, or who have experience with similar technologies deployed in other spaces. We are dedicated to creating forums for continuous conversation and feedback to help shape the design and development of the tool.\n\nWe also recognize capacity building as a key part of involving a diverse open source community. We are doing our best to use accessible language, provide technical and process documents, and offer support to community members with a wide variety of backgrounds and skillsets.\n\n### Community Guidelines\n\nPrinciples and guidelines for participating in our open source community are can be found in [COMMUNITY.md](COMMUNITY.md). Please read them before joining or starting a conversation in this repo or one of the channels listed below. All community members and participants are expected to adhere to the community guidelines and code of conduct when participating in community spaces including: code repositories, communication channels and venues, and events.\n\n## Feedback\n\nIf you have ideas for how we can improve or add to our capacity building efforts and methods for welcoming people into our community, please let us know at opensource@cms.hhs.gov. If you would like to comment on the tool itself, please let us know by filing an **issue on our GitHub repository.**\n\n### Policies\n\n### Open Source Policy\n\nWe adhere to the [CMS Open Source\nPolicy](https://github.com/CMSGov/cms-open-source-policy). If you have any\nquestions, just [shoot us an email](mailto:opensource@cms.hhs.gov).\n\n### Security and Responsible Disclosure Policy\n\n_Submit a vulnerability:_ Vulnerability reports can be submitted through [Bugcrowd](https://bugcrowd.com/cms-vdp). Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days.\n\nFor more information about our Security, Vulnerability, and Responsible Disclosure Policies, see [SECURITY.md](SECURITY.md).\n\n### Public domain\n\nThis project is in the public domain within the United States, and copyright\nand related rights in the work worldwide are waived through the [CC0 1.0\nUniversal public domain\ndedication](https://creativecommons.org/publicdomain/zero/1.0/) as indicated in [LICENSE](LICENSE).\n\nAll contributions to this project will be released under the CC0 dedication. By\nsubmitting a pull request or issue, you are agreeing to comply with this waiver\nof copyright interest.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdsacms%2Fospo-guide","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdsacms%2Fospo-guide","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdsacms%2Fospo-guide/lists"}