fix: update github links to reflect org transfer

Dockerfile

@@ -30,8 +30,8 @@ ENV APP_VERSION=$VERSION \
 # Set Docker labels
 LABEL org.opencontainers.image.title="ATT&CK Workbench Frontend Service" \
     org.opencontainers.image.description="This Docker image contains the frontend service of the ATT&CK Workbench, an application for exploring, creating, annotating, and sharing extensions of the MITRE ATT&CK® knowledge base. The service handles the storage, querying, and editing of ATT&CK objects. It is an Angular SPA served by an Nginx reverse proxy." \
-    org.opencontainers.image.source="https://github.com/center-for-threat-informed-defense/attack-workbench-frontend" \
-    org.opencontainers.image.documentation="https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/README.md" \
+    org.opencontainers.image.source="https://github.com/mitre-attack/attack-workbench-frontend" \
+    org.opencontainers.image.documentation="https://github.com/mitre-attack/attack-workbench-frontend/README.md" \
     org.opencontainers.image.url="https://ghcr.io/center-for-threat-informed-defense/attack-workbench-frontend" \
     org.opencontainers.image.vendor="The MITRE Corporation" \
     org.opencontainers.image.licenses="Apache-2.0" \

README.md

@@ -45,10 +45,10 @@ The ATT\&CK Workbench application is composed of several interconnected services
 
 ### Core Components
 
-* **[ATT\&CK Workbench Frontend](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend)**
+* **[ATT\&CK Workbench Frontend](https://github.com/mitre-attack/attack-workbench-frontend)**
   The web-based user interface for ATT\&CK Workbench, and the primary way users interact with the knowledge base.
 
-* **[ATT\&CK Workbench REST API](https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api)**
+* **[ATT\&CK Workbench REST API](https://github.com/mitre-attack/attack-workbench-rest-api)**
   Provides a CRUD interface for storing, querying, and editing ATT\&CK objects, as well as managing collections, collection indexes, and subscriptions.
 
 * **[ATT\&CK Workbench Database](https://hub.docker.com/_/mongo)**

docs/contributing.md

@@ -4,7 +4,7 @@ Thanks for contributing to `attack-workbench-frontend`!
 
 You are welcome to comment on issues, open new issues, and open pull requests.
 
-Pull requests should target the **develop** branch of the repository. If your pull request is reliant on changes to the [REST API](https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api), please make sure to document this in your pull request and link to the corresponding REST API pull request.
+Pull requests should target the **develop** branch of the repository. If your pull request is reliant on changes to the [REST API](https://github.com/mitre-attack/attack-workbench-rest-api), please make sure to document this in your pull request and link to the corresponding REST API pull request.
 
 Also, if you contribute any source code, we need you to agree to the following Developer's Certificate of Origin below.
 

docs/integrations.md

@@ -95,7 +95,7 @@ To allow Navigator to access your Workbench data, you must enable basic API key
     JSON_CONFIG_PATH=/some/path/to/rest-api-service-config.json
     ```
 
-    Make sure this path points to your actual configuration file. For more details on configuring the REST API, see the [Usage Documentation: Configuration](https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api/blob/main/USAGE.md#configuration).
+    Make sure this path points to your actual configuration file. For more details on configuring the REST API, see the [Usage Documentation: Configuration](https://github.com/mitre-attack/attack-workbench-rest-api/blob/main/USAGE.md#configuration).
 
 2. In your REST API config file, add a `basicApikey` section to the `serviceAuthn` block, specifying a service account for Navigator. Example:
 
@@ -116,7 +116,7 @@ To allow Navigator to access your Workbench data, you must enable basic API key
     }
     ```
 
-    For more example configurations, see the [sample REST API configuration files](https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api/tree/main/resources/sample-configurations). For more details on Service Authentication, see the [REST API Service Authentication documentation](https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api/blob/main/docs/legacy/authentication.md#service-authentication).
+    For more example configurations, see the [sample REST API configuration files](https://github.com/mitre-attack/attack-workbench-rest-api/tree/main/resources/sample-configurations). For more details on Service Authentication, see the [REST API Service Authentication documentation](https://github.com/mitre-attack/attack-workbench-rest-api/blob/main/docs/legacy/authentication.md#service-authentication).
 
 ### 4. Serve the application
 

docs/local-dev.md

@@ -7,8 +7,8 @@ This document outlines how to set up ATT&CK Workbench for local development. For
 Before running the application locally, ensure you have the following set up:
 
 1. Clone the required repositories
-    - [attack-workbench-frontend](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend) repository
-    - [attack-workbench-rest-api](https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api) repository alongside the frontend
+    - [attack-workbench-frontend](https://github.com/mitre-attack/attack-workbench-frontend) repository
+    - [attack-workbench-rest-api](https://github.com/mitre-attack/attack-workbench-rest-api) repository alongside the frontend
 
 2. Install the [recommended version](../README.md#requirements) of [Node.js](https://nodejs.org/)
 
@@ -29,7 +29,7 @@ npm install
 
 #### 2. Configure the system
 
-Configure the application using environment variables, a configuration file, or a combination. Please refer to the documentation on how to [Configure the System](https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api?tab=readme-ov-file#step-3-configure-the-system) for more details.
+Configure the application using environment variables, a configuration file, or a combination. Please refer to the documentation on how to [Configure the System](https://github.com/mitre-attack/attack-workbench-rest-api?tab=readme-ov-file#step-3-configure-the-system) for more details.
 
 For example, you can use a custom configuration to adapt to your specific environment:
 

package.json

@@ -4,7 +4,7 @@
   "description": "An application allowing users to explore, create, annotate, and share extensions of the MITRE ATT&CK® knowledge base. This repository contains an Angular-based web application providing the user interface for the ATT&CK Workbench application.",
   "repository": {
     "type": "git",
-    "url": "https://github.com/center-for-threat-informed-defense/attack-workbench-frontend.git"
+    "url": "https://github.com/mitre-attack/attack-workbench-frontend.git"
   },
   "keywords": [
     "cti",

src/app/classes/collection-index.ts

@@ -1,10 +1,10 @@
 import { Observable, of } from 'rxjs';
 import { RestApiConnectorService } from '../services/connectors/rest-api/rest-api-connector.service';
+import { logger } from '../utils/logger';
 import { Serializable, ValidationData } from './serializable';
 import { VersionNumber } from './version-number';
-import { logger } from '../utils/logger';
 
-// https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/blob/develop/docs/collections.md#collection-version-properties
+// https://github.com/mitre-attack/attack-workbench-frontend/blob/develop/docs/collections.md#collection-version-properties
 export class CollectionVersion extends Serializable {
   public version: VersionNumber;
   public modified: Date;
@@ -114,7 +114,7 @@ export class CollectionVersion extends Serializable {
     return of(new ValidationData());
   }
 }
-// https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/blob/develop/docs/collections.md#collection-reference-properties
+// https://github.com/mitre-attack/attack-workbench-frontend/blob/develop/docs/collections.md#collection-reference-properties
 export class CollectionReference extends Serializable {
   public id: string;
   public name: string;
@@ -224,7 +224,7 @@ export class CollectionReference extends Serializable {
     return of(new ValidationData());
   }
 }
-// https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/blob/develop/docs/collections.md#collection-index-properties
+// https://github.com/mitre-attack/attack-workbench-frontend/blob/develop/docs/collections.md#collection-index-properties
 export class CollectionIndex extends Serializable {
   public collection_index: {
     id: string;

src/environments/environment.prod.ts

@@ -12,7 +12,7 @@ export const environment = {
   integrations: {
     rest_api: {
       // configuration for the ATT&CK Workbench REST API
-      // https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api
+      // https://github.com/mitre-attack/attack-workbench-rest-api
       enabled: true, // MUST be true for application operation
       url: 'api',
     },

src/environments/environment.ts

@@ -16,7 +16,7 @@ export const environment = {
   integrations: {
     rest_api: {
       // configuration for the ATT&CK Workbench REST API
-      // https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api
+      // https://github.com/mitre-attack/attack-workbench-rest-api
       enabled: true, // MUST be true for application operation
       url: 'http://localhost:3000/api',
     },