Skip to content

OSPO: Updating Repo to Tier 0 - #466

Open
sachin-panayil wants to merge 2 commits into
developfrom
OSPO/outbounding
Open

OSPO: Updating Repo to Tier 0#466
sachin-panayil wants to merge 2 commits into
developfrom
OSPO/outbounding

Conversation

@sachin-panayil

Copy link
Copy Markdown

Welcome to the Federal Open Source Community!

Hello, and thank you for your contributions to the Federal Open Source Community. 🙏

This pull request is being sent on behalf of the CMS Source Code Stewardship Taskforce, in compliance with The Federal Source Code Inventory Policy, M-16-21, and in preparation for the SHARE IT Act.

This bundled PR includes:

  • A pre-filled code.json with automated repository metadata
  • An automated code.json workflow for ongoing maintenance
  • SECURITY.md and COMMUNITY.md templates to enhance your repository

If you have questions, please file an issue here or join our #cms-ospo slack channel here.

Next Steps

1. Review and Update code.json

  • We have automatically calculated some fields, but many require manual input
  • Please enter the missing fields by directly editing code.json in the Files Changed tab on your pull request
  • Alternatively, use our form tool to create your code.json via a formsite, then download and paste it here

For more information about code.json metadata requirements, please visit the gov-codejson repository.

2. Review SECURITY.md and COMMUNITY.md

We've included starter templates to help your project follow open source best practices. Please customize these files to fit your project's specific needs

  • SECURITY.md
    • Provides guidelines for responsibly reporting and handling security vulnerabilities to help keep the project and its users safe.
  • COMMUNITY.md
    • Outlines the project’s community structure, roles, and guidelines for collaboration and contribution.

3. Optional: Upgrade Your Repository Maturity Model Tier

  • Want to improve your repository's maturity? The OSPO can help!
  • Please reach out to us via slack and our team will assist with the process
  • This step is completely optional. Reach out if you'd like to learn more or visit our repo-scaffolder repository

@sachin-panayil sachin-panayil self-assigned this Feb 27, 2026
@sachin-panayil
sachin-panayil requested a review from a team as a code owner February 27, 2026 15:40
@codecov

codecov Bot commented Feb 27, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.85%. Comparing base (1a6f451) to head (a23ab66).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #466   +/-   ##
========================================
  Coverage    91.85%   91.85%           
========================================
  Files           33       33           
  Lines          700      700           
  Branches       129      129           
========================================
  Hits           643      643           
  Misses          35       35           
  Partials        22       22           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant