You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+31-46Lines changed: 31 additions & 46 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,55 +1,51 @@
1
-
# {{ cookiecutter.project_name }}
1
+
# codejson-crosswalk
2
2
3
-
{{ cookiecutter.project_description }}
3
+
A TypeScript npm package for bidirectional conversion between code.json and other metadata formats
4
4
5
5
## About the Project
6
6
7
-
**{project statement}**
8
-
9
-
<!---
10
-
### Project Vision
11
-
**{project vision}** -->
12
-
13
-
<!--
14
-
### Project Mission
15
-
**{project mission}** -->
16
-
17
-
<!--
18
-
### Agency Mission
19
-
TODO: Good to include since this is an agency-led project -->
20
-
21
-
<!--
22
-
### Team Mission
23
-
TODO: Good to include since this is an agency-led project -->
7
+
There is no automated bridge between code.json and other software metadata formats. This package provides a single function call to convert between code.json and codemeta.json (and future formats), with code.json at the center of a hub-and-spoke architecture.
24
8
25
9
## Core Team
26
10
27
11
A list of core team members responsible for the code and documentation in this repository can be found in [COMMUNITY.md](COMMUNITY.md).
28
12
29
13
## Repository Structure
30
14
31
-
<!-- TODO: Including the repository structure helps viewers quickly understand the project layout. 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. -->
│ │ ├── handler.ts # Coordinator functions for codemeta conversions
27
+
│ │ └── README.md # Documentation for mapping files
28
+
│ ├── types/
29
+
│ │ └── MappingEntry.ts # Shared MappingEntry type definition
30
+
│ └── index.ts # Package entry point and public API
31
+
├── .github/ # GitHub Actions workflows
35
32
```
36
33
37
-
38
-
**{list directories and descriptions}**
39
-
40
-
<!-- TODO: Add 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. -->
41
-
42
-
**{list of .md at top directory and descriptions}**
43
-
44
34
# Development and Software Delivery Lifecycle
45
35
46
36
The 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).
47
37
48
38
## Local Development
49
39
50
-
<!--- TODO - with example below:
51
-
This 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.
52
-
-->
40
+
This project uses [Bun](https://bun.sh/) as its runtime and package manager.
41
+
42
+
```bash
43
+
# Install dependencies
44
+
bun install
45
+
46
+
# Run tests
47
+
bun test
48
+
```
53
49
54
50
## Coding Style and Linters
55
51
@@ -59,7 +55,6 @@ Each application has its own linting and testing guidelines. Lint and code tests
59
55
60
56
## Branching Model
61
57
62
-
<!--- TODO - with example below:
63
58
This project follows [trunk-based development](https://trunkbaseddevelopment.com/), which means:
64
59
65
60
* Make small changes in [short-lived feature branches](https://trunkbaseddevelopment.com/short-lived-feature-branches/) and merge to `main` frequently.
@@ -79,29 +74,19 @@ Thank you for considering contributing to an Open Source project of the US Gover
79
74
80
75
## Community
81
76
82
-
The {{ cookiecutter.project_name }} 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.
77
+
The codejson-crosswalk 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.
83
78
84
79
We 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.
85
80
86
81
We 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.
87
82
88
83
### Community Guidelines
89
84
90
-
Principles 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.
91
-
92
-
<!--
93
-
## Governance
94
-
Information about how the {{ cookiecutter.project_name }} community is governed may be found in [GOVERNANCE.md](GOVERNANCE.md).
95
-
-->
85
+
Principles and guidelines for participating in our open source community 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.
96
86
97
87
## Feedback
98
88
99
-
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.**
100
-
101
-
<!--
102
-
## Glossary
103
-
Information about terminology and acronyms used in this documentation may be found in [GLOSSARY.md](GLOSSARY.md).
104
-
-->
89
+
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 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.**
105
90
106
91
## Policies
107
92
@@ -121,7 +106,7 @@ For more information about our Security, Vulnerability, and Responsible Disclosu
121
106
122
107
A Software Bill of Materials (SBOM) is a formal record containing the details and supply chain relationships of various components used in building software.
123
108
124
-
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/{{ cookiecutter.project_org }}/{{ cookiecutter.project_repo_name }}/network/dependencies.
109
+
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/DSACMS/codejson-crosswalk/network/dependencies.
125
110
126
111
For more information and resources about SBOMs, visit: https://www.cisa.gov/sbom.
0 commit comments