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: .github/SECURITY.md
+4-8Lines changed: 4 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,11 +5,7 @@ Security is a priority. We maintain a proactive stance to identify and fix vulne
5
5
<br/>
6
6
7
7
## 🛠️ Supported & Maintained Versions
8
-
9
-
| Version | Status |
10
-
|---------|----------------------|
11
-
| 0.x.x | ✅ Supported & Active |
12
-
| 1.x.x | ✅ Supported & Active |
8
+
Any released version of **go-subtree** that is not marked as deprecated is actively supported and maintained.
13
9
14
10
<br/>
15
11
@@ -70,7 +66,7 @@ We follow the [OpenSSF](https://openssf.org) best practices to ensure this repos
70
66
71
67
To proactively protect this repository, we use several automated GitHub workflows:
72
68
73
-
-**[CodeQL Analysis](./workflows/codeql-analysis.yml)**: Scans the codebase for security vulnerabilities and coding errors using GitHub's CodeQL engine on every push and pull request to the `master` branch.
74
-
-**[OpenSSF Scorecard](./workflows/scorecard.yml)**: Periodically evaluates the repository against OpenSSF Scorecard checks, providing insights and recommendations for improving supply chain security and best practices.
69
+
-**[CodeQL Analysis](./github/workflows/codeql-analysis.yml)**: Scans the codebase for security vulnerabilities and coding errors using GitHub's CodeQL engine on every push and pull request to the `main/master` branch.
70
+
-**[OpenSSF Scorecard](./github/workflows/scorecard.yml)**: Periodically evaluates the repository against OpenSSF Scorecard checks, providing insights and recommendations for improving supply chain security and best practices.
75
71
76
-
These workflows help us identify, remediate, and prevent security issues as early as possible in the development lifecycle. For more details, see the workflow files in the [`.github/workflows/`](https://github.com/bsv-blockchain/go-subtree/tree/master/.github/workflows) directory.
72
+
These workflows help us identify, remediate, and prevent security issues as early as possible in the development lifecycle. For more details, see the workflow files in the [`.github/workflows/`](.github/workflows) directory.
Copy file name to clipboardExpand all lines: .github/tech-conventions/labeling-conventions.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
> Labels serve as shared vocabulary for categorizing issues, pull requests, and discussions. Proper labeling improves triage, prioritization, automation, and clarity across the engineering lifecycle.
4
4
5
-
Current labels are located in `.github/labels.yml` and automatically synced into GitHub upon updating the `master` branch.
5
+
Current labels are located in `.github/labels.yml` and automatically synced into GitHub upon updating the `main/master` branch.
0 commit comments