Repolinter Results

COMMUNITY.md

@@ -0,0 +1,9 @@
+## Table of Project Members 
+<!-- TODO: Who are the points of contact in your project who are responsible/accountable for the project? This can often be an engineering or design manager or leader, who may or may not be the primary maintainers of the project. 
+ Roles to include, but not limited to: Project Owner, Technical Lead, Developers/Contributors, Community Manager, Security Team, Policy Advisor, Contracting Officer's Representative, Compliance Officer, Procurement Officer --> 
+
+{{ cookiecutter.project_repo_name }} is supported by a dedicated team of individuals fulfilling various roles to ensure its success, security, and alignment with government standards and agency goals.
+
+| Role | Name | Affiliation |
+| :----- | :------ | :------------- |
+| {role} | {names} | {affiliations} |

CONTRIBUTING.md

@@ -17,14 +17,14 @@
  ### Workflow and Branching 
 <!--- TODO: Workflow Example
 We follow the [GitHub Flow Workflow](https://guides.github.com/introduction/flow/)
-1.  Fork the project
-2.  Check out the `main` branch
-3.  Create a feature branch
-4.  Write code and tests for your change
-5.  From your branch, make a pull request against `{{ cookiecutter.project_org }}/{{ cookiecutter.project_repo_name }}/main`
-6.  Work with repo maintainers to get your change reviewed
-7.  Wait for your change to be pulled into `{{ cookiecutter.project_org }}/{{ cookiecutter.project_repo_name }}/main`
-8.  Delete your feature branch
+1. Fork the project
+2. Check out the `main` branch
+3. Create a feature branch
+4. Write code and tests for your change
+5. From your branch, make a pull request against `{{ cookiecutter.project_org }}/{{ cookiecutter.project_repo_name }}/main`
+6. Work with repo maintainers to get your change reviewed
+7. Wait for your change to be pulled into `{{ cookiecutter.project_org }}/{{ cookiecutter.project_repo_name }}/main`
+8. Delete your feature branch
 -->
 
  ### Testing Conventions 

README.md

@@ -1,10 +1,8 @@
-# Repolinter Test 1
+# {name_of_project_here} 
 <!-- This should be 1-3 sentence short description of the project that can be used as a 'one-liner' to describe the repo. A best practice is using this same language as the official 'description' on a GitHub repo landing page. --> 
-This is a quick test project.
 
  ## About the Project 
 <!-- This should be a longer-form description of the project. It can include history, background, details, problem statements, links to design documents or other supporting materials, or any other information/context that a user or contributor might be interested in. --> 
-This is a real quick test project for Repolinter PR testing the actual flow of using this action.
 
  ## Project Mission 
 <!-- Provide the core mission and objectives driving this project. --> 
@@ -16,7 +14,7 @@ This is a real quick test project for Repolinter PR testing the actual flow of u
 <!-- Provide the team's mission and how they work together. --> 
 
  ## Core Team 
-An up-to-date list of core team members can be found in [MAINTAINERS.md](MAINTAINERS.md). At this time, the project is still building the core team and defining roles and responsibilities. We are eagerly seeking individuals who would like to join the community and help us define and fill these roles. 
+An up-to-date list of core team members can be found in [COMMUNITY.md](COMMUNITY.md). At this time, the project is still building the core team and defining roles and responsibilities. We are eagerly seeking individuals who would like to join the community and help us define and fill these roles. 
 
  ## Documentation Index 
 <!-- TODO: 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. --> 
@@ -55,9 +53,6 @@ Pull-requests are merged to `main` and the changes are immediately deployed to t
  ## Contributing 
 Thank 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). 
 
- ## Codeowners 
-The 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). 
-
  ## Community 
 The {name_of_project_here} 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.
 
@@ -68,9 +63,6 @@ We also recognize capacity building as a key part of involving a diverse open so
  ## Community Guidelines 
 Principles 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. 
 
- ## Feedback 
-If 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.** 
-
  ## Glossary 
 Information about terminology and acronyms used in this documentation may be found in [GLOSSARY.md](GLOSSARY.md). 
 
@@ -90,4 +82,4 @@ All contributions to this project will be released under the CC0 dedication. By
  ### Software Bill of Materials (SBOM) 
 A Software Bill of Materials (SBOM) is a formal record containing the details and supply chain relationships of various components used in building software.
 In the spirit of [Executive Order 14028 - Improving the Nation's Cyber Security](https://www.gsa.gov/technology/it-contract-vehicles-and-purchasing-programs/information-technology-category/it-security/executive-order-14028), a SBOM for this repository is provided here: https://github.com/{repo_org}/{repo_name}/network/dependencies.
-For more information and resources about SBOMs, visit: https://www.cisa.gov/sbom.
+For more information and resources about SBOMs, visit: https://www.cisa.gov/sbom.

code.json

@@ -1,51 +0,0 @@
-{
-  "name": "repolinter-test-1",
-  "description": "Test repository for Repolinter Actions",
-  "longDescription": "This is a playground to test various actions that are made with Github Actions",
-  "status": "ideation",
-  "permissions": {
-    "licenses": [
-      {
-        "URL": "LICENSE",
-        "name": "CC0-1.0"
-      }
-    ],
-    "usageType": "openSource"
-  },
-  "organization": "Centers for Medicare & Medicaid Services",
-  "repositoryURL": "https://github.com/DSACMS/repolinter-test-1",
-  "vcs": "git",
-  "laborHours": 2656,
-  "platforms": [
-    "web"
-  ],
-  "categories": [
-    "healthcare"
-  ],
-  "softwareType": "standalone/mobile",
-  "languages": [
-    "Python"
-  ],
-  "maintenance": "internal",
-  "date": {
-    "created": "2024-12-10T17:23:27Z",
-    "lastModified": "2025-02-13T20:20:45Z",
-    "metaDataLastUpdated": "2025-02-13T20:21:57.448Z"
-  },
-  "tags": [
-    "healthcare"
-  ],
-  "contact": {
-    "email": "opensource@cms.hhs.gov",
-    "name": "CMS Open Source Program Office"
-  },
-  "localisation": false,
-  "repositoryType": "tools",
-  "userInput": false,
-  "fismaLevel": "Low",
-  "group": "CMS/OA/DSAC",
-  "subsetInHealthcare": ["Policy", "Operational"],
-  "userType": "Government",
-  "repositoryHost": "github.com/DSACMS",
-  "maturityModelTier": 1
-}