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
+26-15
Original file line number
Diff line number
Diff line change
@@ -1,38 +1,42 @@
1
1
# codejson-index-generator
2
+
2
3
Script to create an indexed code.json for agencies.
3
4
4
5
## About the Project
6
+
5
7
The GitHub Code.json Index Generator is a Python-based tool that helps federal agencies compile and maintain their code.json files for code.gov compliance. It automatically scans specified GitHub organizations, finds repositories containing code.json files, and combines them into a single indexed file.
6
8
7
9
### Project Vision
10
+
8
11
To streamline the process of code.gov compliance for federal agencies by automating the collection and aggregation of code.json files across multiple GitHub organizations.
9
12
10
13
### Project Mission
14
+
11
15
To provide agencies with a reliable, efficient tool for maintaining their code.gov inventory while reducing manual effort and potential for errors in the process.
12
16
13
17
## Core Team
14
18
15
19
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.
16
20
17
-
<!--
18
-
## Documentation Index
21
+
<!--
22
+
## Documentation Index
19
23
20
24
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.
21
25
22
-
**{list of .md at top directory and descriptions}**
26
+
**{list of .md at top directory and descriptions}**
23
27
-->
24
28
25
-
<!--
29
+
<!--
26
30
## Repository Structure
27
31
28
32
TODO: 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.
29
33
30
-
**{list directories and descriptions}**
34
+
**{list directories and descriptions}**
31
35
32
36
-->
33
37
34
-
<!--
35
-
# Development and Software Delivery Lifecycle
38
+
<!--
39
+
# Development and Software Delivery Lifecycle
36
40
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).
37
41
-->
38
42
@@ -42,26 +46,30 @@ The following guide is for members of the project team who have access to the re
42
46
43
47
- Python 3.x
44
48
- GitHub Personal Access Token (optional, but highly recommended for higher rate limits)
45
-
> **_Create a PAT:_** GitHub -> Settings -> Developer Settings -> Personal Access Tokens
49
+
> **_Create a PAT:_** GitHub -> Settings -> Developer Settings -> Personal Access Tokens
46
50
47
51
### Installation
48
52
49
53
1. Clone the repository:
54
+
50
55
```bash
51
56
git clone ...
52
57
cd codejson-index-generator
53
58
```
54
59
55
60
2. Install required dependencies:
61
+
56
62
```bash
57
-
pip install PyGithub
63
+
pip install -r requirements.txt
58
64
```
59
65
60
66
1. Set up your GitHub Personal Access Token:
67
+
61
68
```bash
62
69
export GITHUB_KEY="your-token-here"
63
70
```
64
-
> **_NOTE:_**_Use of GitHub PAT is highly recommened due to rate limiting._
71
+
72
+
> **_NOTE:_**_Use of GitHub PAT is highly recommened due to rate limiting._
65
73
66
74
### Usage
67
75
@@ -71,17 +79,20 @@ The script can be run from the command line with the following options:
@@ -123,11 +134,11 @@ The codejson-index-generator team is taking a community-first and open source ap
123
134
124
135
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.
125
136
126
-
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.
137
+
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.
127
138
128
139
### Community Guidelines
129
140
130
-
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.
141
+
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.
131
142
132
143
<!--
133
144
## Governance
@@ -151,13 +162,13 @@ questions, just [shoot us an email](mailto:[email protected]).
151
162
152
163
### Security and Responsible Disclosure Policy
153
164
154
-
*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.
165
+
_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.
155
166
156
167
For more information about our Security, Vulnerability, and Responsible Disclosure Policies, see [SECURITY.md](SECURITY.md).
157
168
158
169
### Software Bill of Materials (SBOM)
159
170
160
-
A Software Bill of Materials (SBOM) is a formal record containing the details and supply chain relationships of various components used in building software.
171
+
A Software Bill of Materials (SBOM) is a formal record containing the details and supply chain relationships of various components used in building software.
161
172
162
173
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-index-generator/network/dependencies.
0 commit comments