{"id":18793084,"url":"https://github.com/dsacms/reverse-scorecard-generation","last_synced_at":"2026-02-23T18:34:02.585Z","repository":{"id":251148737,"uuid":"836522529","full_name":"DSACMS/reverse-scorecard-generation","owner":"DSACMS","description":"Combine column-major HHS Zero Trust Scorecard Excel spreadsheets into a row-major CSV file.","archived":false,"fork":false,"pushed_at":"2025-11-05T22:45:15.000Z","size":42,"stargazers_count":0,"open_issues_count":1,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-11-06T00:18:36.672Z","etag":null,"topics":["csv","excel","python"],"latest_commit_sha":null,"homepage":"","language":"Python","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":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"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}},"created_at":"2024-08-01T03:10:28.000Z","updated_at":"2025-11-05T22:45:19.000Z","dependencies_parsed_at":"2025-05-22T10:46:30.216Z","dependency_job_id":null,"html_url":"https://github.com/DSACMS/reverse-scorecard-generation","commit_stats":null,"previous_names":["dsacms/reverse-scorecard-generation"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/DSACMS/reverse-scorecard-generation","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/DSACMS%2Freverse-scorecard-generation","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/DSACMS%2Freverse-scorecard-generation/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/DSACMS%2Freverse-scorecard-generation/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/DSACMS%2Freverse-scorecard-generation/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/DSACMS","download_url":"https://codeload.github.com/DSACMS/reverse-scorecard-generation/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/DSACMS%2Freverse-scorecard-generation/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29750625,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-23T07:44:07.782Z","status":"ssl_error","status_checked_at":"2026-02-23T07:44:07.432Z","response_time":90,"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":["csv","excel","python"],"created_at":"2024-11-07T21:23:29.186Z","updated_at":"2026-02-23T18:34:02.565Z","avatar_url":"https://github.com/DSACMS.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Reverse Scorecard Generation\n\nCombine column-major HHS Zero Trust Scorecard Excel spreadsheets into a row-major CSV file.\n\n## About the Project\n\n**Combine column-major HHS Zero Trust Scorecard Excel spreadsheets into a row-major CSV file.**\n\n### Usage Instructions\n\nSteps to use the script:\n\n1. `cd` into the repo folder.\n2. Install dependencies: `pip install -r requirements.txt`\n3. Put Excel files in the `input_files` folder.\n4. Run the script: `python script.py`.\n5. The script will generate a `out.csv` file. OR, you can put an existing `out.csv` file in the repo folder and the script will append new roles to the CSV file (it will not overwrite existing rows).\n\n\n\u003c!-- \n### Project Mission\n**{project mission}** --\u003e\n\n\u003c!-- \n### Agency Mission\nTODO: Recommended to include since this is an agency-led project --\u003e\n\n\u003c!-- \n### Team Mission\nTODO: Recommended to include since this is an agency-led project --\u003e\n\n## Core Team\n\nA full list of contributors can be found on [https://github.cms.gov/DSACMS/reverse-scorecard-generation/graphs/contributors](https://github.cms.gov/DSACMS/reverse-scorecard-generation/graphs/contributors).\n\n\u003c!--\n## Documentation Index\n\nTODO: This is a like a 'table of contents\" for your documentation. Tier 0/1 projects with simple README.md files without many sections may or may not need this, but it is still extremely helpful to provide \"bookmark\" or \"anchor\" links to specific sections of your file to be referenced in tickets, docs, or other communication channels.\n\n**{list of .md at top directory and descriptions}**\n--\u003e\n\n\u003c!--\n## Repository Structure\n\nTODO: Using the \"tree -d\" command can be a helpful way to generate this information, but, be sure to update it as the project evolves and changes over time.\n\n**{list directories and descriptions}**\n--\u003e\n\n\u003c!--\n# Development and Software Delivery Lifecycle\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--\u003e\n\n\u003c!--\n## Local Development\n\nTODO - with example below:\nThis project is monorepo with several apps. Please see the [api](./api/README.md) and [frontend](./frontend/README.md) READMEs for information on spinning up those projects locally. Also see the project [documentation](./documentation) for more info.\n--\u003e\n\n\u003c!--\n## Coding Style and Linters\n\nTODO - Add the repo's linting and code style guidelines\n\nEach application has its own linting and testing guidelines. Lint and code tests are run on each commit, so linters and tests should be run locally before committing.\n--\u003e\n\n\u003c!--\n## Branching Model\n\nTODO - with example below:\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 development environment. Releases are created to push changes to production.\n--\u003e\n\n\u003c!--\n## Contributing\nThank you for considering contributing to an Open Source project of the US Government! For more information about our contribution guidelines, see [CONTRIBUTING.md](CONTRIBUTING.md).\n--\u003e\n\n\u003c!--\n## Codeowners\nThe contents of this repository are managed by **{responsible organization(s)}**. Those responsible for the code and documentation in this repository can be found in [CODEOWNERS.md](CODEOWNERS.md).\n--\u003e\n\n\u003c!--\n## Community\nThe Reverse Scorecard Generation 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--\u003e\n\n\u003c!--\n### Community Guidelines\nPrinciples and guidelines for participating in our open source community are can be found in [COMMUNITY_GUIDELINES.md](COMMUNITY_GUIDELINES.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--\u003e\n\n\u003c!--\n## Feedback\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 **{contact email}**. If you would like to comment on the tool itself, please let us know by filing an **issue on our GitHub repository.**\n--\u003e\n\n\u003c!--\n## Glossary\nInformation about terminology and acronyms used in this documentation may be found in [GLOSSARY.md](GLOSSARY.md).\n--\u003e\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:* Unfortunately, we cannot accept secure submissions via\nemail or via GitHub Issues. Please use our website to submit vulnerabilities at\n[https://hhs.responsibledisclosure.com](https://hhs.responsibledisclosure.com).\nHHS maintains an acknowledgements page to recognize your efforts on behalf of\nthe American public, but you are also welcome to submit anonymously.\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 and related rights in the work worldwide are waived through the [CC0 1.0 Universal public domain dedication](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 submitting a pull request or issue, you are agreeing to comply with this waiver of copyright interest.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdsacms%2Freverse-scorecard-generation","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdsacms%2Freverse-scorecard-generation","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdsacms%2Freverse-scorecard-generation/lists"}