components/bitdefender_gravityzone/actions/move-endpoint-to-group/move-endpoint-to-group.mjs (1)

24-39: Consider adding error handling to the API call.

The current implementation doesn't include specific error handling. Consider adding try/catch logic to provide more helpful error messages to users when the API call fails.

async run({ $ }) {
+  try {
    const response = await this.bitdefender.moveEndpointToGroup({
      $,
      data: {
        params: {
          endpointIds: [
            this.endpointId,
          ],
          groupId: this.groupId,
        },
      },
    });

    $.export("$summary", `Successfully moved endpoint ${this.endpointId} to group ${this.groupId}`);
    return response;
+  } catch (error) {
+    $.export("$summary", `Failed to move endpoint: ${error.message}`);
+    throw error;
+  }
}

components/bitdefender_gravityzone/sources/new-incident-instant/test-event.mjs (2)

1-34: Well-structured test event but has a trailing comma issue.

The test event provides a comprehensive representation of a Bitdefender incident, which is excellent for testing. However, there's a formatting issue:

-    "main_action": "no action",
-  }
+    "main_action": "no action"
+  }

The trailing comma at the end of the last property in a JSON object might cause parsing issues in some environments.

---

26-31: Consider adding comments for ATT&CK technique IDs.

The ATT&CK IDs (like "T1036", "T1059", etc.) represent specific MITRE ATT&CK techniques. Consider adding comments to explain what each technique ID represents for better developer understanding.

   "att_ck_id": [
-      "T1036",
-      "T1059",
-      "T1002",
-      "T1012"
+      "T1036", // Masquerading
+      "T1059", // Command and Scripting Interpreter
+      "T1002", // Data Compression
+      "T1012"  // Query Registry
   ],

components/bitdefender_gravityzone/actions/get-policy-details/get-policy-details.mjs (1)

6-6: Fix documentation link formatting.

There's a missing closing bracket in the documentation link.

- description: "Retrieve details about a specific policy. [See the documentation](https://www.bitdefender.com/business/support/en/77209-135304-getpolicydetails.html)",
+ description: "Retrieve details about a specific policy. [See the documentation](https://www.bitdefender.com/business/support/en/77209-135304-getpolicydetails.html)",

components/bitdefender_gravityzone/sources/new-endpoint-added-instant/new-endpoint-added-instant.mjs (1)

15-17: Fix indentation inconsistency.

The indentation for "endpoint-moved-in" has extra spaces/tabs compared to the rest of the code.

    getEventTypes() {
      return {
-        	"endpoint-moved-in": true,
+        "endpoint-moved-in": true,
      };
    },

components/bitdefender_gravityzone/actions/get-scan-task-status/get-scan-task-status.mjs (1)

6-6: Fix documentation link formatting.

There's a missing closing bracket in the documentation link, which will cause incorrect rendering.

- description: "Get the status of a scan task. [See the documentation(https://www.bitdefender.com/business/support/en/77209-440638-gettaskstatus.html)",
+ description: "Get the status of a scan task. [See the documentation](https://www.bitdefender.com/business/support/en/77209-440638-gettaskstatus.html)",

components/bitdefender_gravityzone/sources/common/base.mjs (1)

52-66: Avoid shadowing the event parameter inside the run loop

The parameter event is re-declared in the for … of loop, which is legal but confusing.
Renaming the outer argument clarifies intent and removes shadowing.

-  async run(event) {
+  async run(reqEvent) {
   …
-    const { body } = event;
+    const { body } = reqEvent;
   …
-    for (const event of events) {
-      const meta = this.generateMeta(event);
-      this.$emit(event, meta);
+    for (const e of events) {
+      const meta = this.generateMeta(e);
+      this.$emit(e, meta);
     }

components/bitdefender_gravityzone/bitdefender_gravityzone.app.mjs (2)

103-107: Static JSON-RPC id risks collisions

The constant "120000" is sent with every call. Some servers use this field to match responses; duplicates can confuse retry logic and tracing. Consider a per-call random or incremental value.

-          id: "120000",
+          id: Date.now(), // or uuid.v4()

---

139-162: Pagination helpers drop next-page information

listPolicies, listEndpoints, etc. expose an options() helper that converts result.items into a flat array but never returns hasMore / nextPage flags.
Pipedream’s dynamic dropdowns rely on these flags for infinite scroll.

Consider returning { options, nextPage } where nextPage = page + 1 when the server indicates more pages.

components/bitdefender_gravityzone/actions/scan-endpoint/scan-endpoint.mjs (2)

67-68: Fix typo in scan depth option label.

The label for the permissive scan depth option contains a typo "Permissivearray" instead of "Permissive".

-          label: "Permissivearray",
+          label: "Permissive",
           value: 3,

---

109-109: Improve the summary message to be more user-friendly.

The current summary uses numeric scan type and endpoint ID, which isn't very readable. Consider using the scan type label instead of the numeric value.

-    $.export("$summary", `Successfully initiated ${this.scanType} scan on endpoint ${this.endpointId}`);
+    const scanTypeLabels = {
+      1: "Quick",
+      2: "Full", 
+      3: "Memory",
+      4: "Custom"
+    };
+    $.export("$summary", `Successfully initiated ${scanTypeLabels[this.scanType]} scan on endpoint ${this.endpointId}`);

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting